(Thanks to cwgordon7 for helping me identify this as a bug & pinpointing the likely cause)

The problem: in my module (bones-6-x-1.0-unstable3) I have the path 'admin/build/bones'.

Upon unchecking the 'Bones' checkbox and submitting the form at 'admin/build/modules' to disable the module, I get the error

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'bones_access' was given in /path/to/drupal-6.10/includes/menu.inc on line 452.

From cwgordon7 in #drupal:
cwgordon7: usonian: Oh, *very* interesting....
[9:15pm] cwgordon7: usonian: I think I know what's going on here, and I think it's a core bug.
[9:15pm] cwgordon7: usonian: After the initial disable, does everything start working again?
[9:15pm] usonian: Yeah, it
[9:16pm] cwgordon7: usonian: Ok here's the problem (my guess at it anyways)
[9:16pm] usonian: cwgordon7: er yes, the site doesn't break; the error in question is just a warning and it only happens once, immediately after submitting the modules form
[9:16pm] cwgordon7: You're using the path admin/build/bones
[9:16pm] gnuist: db_query doesn't have a maximum number of arguments after the SQL syntax, right? these arguments are used for variable replacement, or whatever it is called. . .
[9:16pm] cwgordon7: usonian: So when you disable the module on the module page... weird stuff happens because it has to check the menu item admin/build/bones for access
[9:16pm] cwgordon7: because the menu is open there
...
[9:24pm] cwgordon7: usonian: ^ you could also mention it's just a matter of calling drupal_flush_all_caches() in system_modules_uninstall_submit()

Comments

damien tournoud’s picture

damien tournoud commented
Title: system_modules_uninstall_submit() should call drupal_flush_all_caches() » Access functions of disabled modules can be called when submitting admin/build/modules
Status: Active » Postponed (maintainer needs more info)

I'm not unsure what's causing this. cwgordon7 is talking about system_modules_uninstall_submit(), which is actually admin/build/modules/uninstall, not the module page itself.

Can you reproduce this issue in isolation (ie. just with your module and Drupal core)?

usonian’s picture

usonian commented
Version: 7.x-dev » 6.10

Interesting. I initially encountered this issue in Drupal 6.10, but originally logged it for D7 on cwgordon7's recommendation.

On a clean install of Drupal 6.10 with *only* Bones installed, the error does not occur.

dpearcefl’s picture

dpearcefl commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing this issue because of a lack of activity.