Hi,

After updating today to 6.x-1.1 of node_clone I get this:

"call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'clone_access' was given in /var/www/html/drupal/includes/menu.inc on line 452.

After disabling the module, apparently the message went away.

I thing the bug might be in
sites/all/modules/node_clone/clone.module
line 63:
drupal_alter("clone_access", $access, $node);

I changed it to:
drupal_alter("clone_access_cloning", $access, $node);

And the message went away.

regards,

Giannis

Comments

scalp’s picture

In my case, after upgrading to 1.1 I got a WSOD. Rolling back to version 1.0 fixed it.

andrewhthomas’s picture

I saw this error after my upgrade, but I flushed my site cache and have not seen it since.

pwolanin’s picture

Yes, the name of the access callback was changed so you need a menu rebuild - did you run update.php after the update?

pwolanin’s picture

Status: Active » Fixed
asb’s picture

Status: Fixed » Active

Similar/same issue here. The watchdog log is flooded (yes, literally flooded) with messages like this:

Warning: call_user_func_array() [<a href='function.call-user-func-array'>function.call-user-func-array</a>]: First argument is expected to be a valid callback, 'clone_access' was given in _menu_check_access() (line 452 of /var/www/drupal/includes/menu.inc).

And yes, I ran update.php after the update (through drush updatedb).

Re-opening.

pwolanin’s picture

ok, well drush updatedb should have worked, but try the performance page. Or submit the modules page. All you need is a menu rebuild.

asb’s picture

Status: Active » Fixed

Yes, submitting the modules page seems to have done the trick. Thanks!

scalp’s picture

After running update.php is when I get the WSOD. Checking the Drupal's recent log entries shows:
call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'clone_access_cloning' was given in /var/www/html/includes/menu.inc on line 452.
I should mention that I also tried to do a menu rebuild by visiting /admin/build/modules, but still get the WSOD.

Status: Fixed » Closed (fixed)

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