The following errors are being received on the /catalog page. I am using Drupal 5.5 with PostgreSQL.

    * warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'uc_product_add_to_cart_form_228' was given in /usr/local/apache2/htdocs/drupal/includes/form.inc on line 218.
    * warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'uc_product_add_to_cart_form_205' was given in /usr/local/apache2/htdocs/drupal/includes/form.inc on line 218.
    * warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'uc_product_add_to_cart_form_204' was given in /usr/local/apache2/htdocs/drupal/includes/form.inc on line 218.
    * warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'uc_product_add_to_cart_form_39' was given in /usr/local/apache2/htdocs/drupal/includes/form.inc on line 218.

Comments

Island Usurper’s picture

Island Usurper commented

Did you put non-product nodes in the catalog? That's not really supported, though I'm not sure what to do to prevent these errors from happening.

WISEOZ’s picture

WISEOZ commented
Status: Active » Fixed

I've only ever used Product nodes to add items to the Catalog. I wouldn't know how to otherwise. However, I did notice that this error was happening for any product nodes I had created prior to beta5 and beta6. I deleted them all (fortunately I'm in a position where I can easily do that still) and the errors were all gone.

I mark this issue as fixed although I still view it as a problem if existing product nodes are not being considered by new versions.

Island Usurper’s picture

Island Usurper commented

Now that I think about it some more, non-products in the catalog wouldn't cause this kind of problem. They still won't work very well, but they wouldn't cause PHP errors, I don' think.

The upgrade path for products has probably not been done very well in Postgres (surprise, surprise). I'm limiting it to that because I know of at least two test sites using MySQL that don't have this problem. They products have been around since the early alpha versions, or longer.

WISEOZ’s picture

WISEOZ commented

Well, I go-live April 1st ... I can only hope it gets better by then. I'm trying to do all I can to provide the PostrgreSQL test perspective as quickly as these new releases come out but I'm going to have to freeze a working solution in a couple weeks.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.