Posted by lancelot on May 9, 2008 at 7:17pm
| Project: | Comment RSS |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
warning: Invalid argument supplied for foreach() in /http/suncampus/site/_htdocs/includes/menu.inc on line 258.
warning: array_merge() [function.array-merge]: Argument #1 is not an array in /http/suncampus/site/_htdocs/includes/menu.inc on line 323.
warning: Missing argument 1 for drupal_get_form() in /http/suncampus/site/_htdocs/includes/form.inc on line 69.
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '' was given in /http/suncampus/site/_htdocs/includes/form.inc on line 358.
That appeared after upgrade from Drupal5 to Drupal6.
As one can find by Goggle the first error is quite spread among v6 modules.
Hope you someone can fix this. Thanx!
Comments
#1
Line 39 of comentrss.module should read:
'page arguments' => array('commentrss_admin_settings'),#2
I'm having the same problem, and updating line 39 of the commentrss.module doesn't change the error messages.
#3
Or maybe it did. I disabled all caching and went back to the setting page and voila!
#4
Just a confirmation. I saw the same warning. The fix in #1 corrected it after I cleared the cache.
#5
Yep, it works.
#6
I can confirm doing this fixes the issue, once the cache is cleared.
#7
Here is a patch to fix this issue
#8
I attempted to apply this patch to my installation but the same error was returned. I cleared my browser cache. I have upgraded to 6.4. Is there a difference between 6.4 and the 6.x the patch was originally written to work with?
#9
It's not your browser cache you have to clear, but the cache built into Drupal.
Navigate to admin/settings/performance
(Or just click "Performance" from the Admin menu screen) - scroll down and click the "Clear cached data" button.
#10
That fixed it! Thanks very much.
#11
Also realized myself, and shipped in 6.x-1.1. Please upgrade.
#12
Automatically closed -- issue fixed for two weeks with no activity.