Closed (fixed)
Project:
Drupal core
Version:
4.7.2
Component:
other
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
19 May 2006 at 21:43 UTC
Updated:
8 Jul 2026 at 18:58 UTC
Jump to comment: Most recent
Comments
Comment #1
bradleyg commentedI'm also experiencing this problem. Haven't investigated yet. I'll let you know if I find anything.
Comment #2
Anonymous (not verified) commentedThanks - Still gettting these 2 months later... just ignoring it. :(
I believe it is related to when I moved the menu table from our dev environment to the live environment. I recently went the other direction with just the menu table, and started getting this message on our dev machine.
Not sure what to do about it, but I am fairly certain its related.
Thanks,
-Greg
Comment #3
varr commentedHas there been any progress on this issue?
I just ran into the same problem. I've been trying to get the search indexing to work, and I ran the cron.php which gives me the mentioned errors.
Have you guys found a solution yet?
Thanks
Comment #4
varr commentedSo far it appears that getting these errors has no adverse effect on the actual searching, the site still gets indexed, so other than getting the annoying errors when I run cron.php, it's not an issue.
I also changed the Component back to 'other'.
Comment #5
nigels commentedI am also experiencing these errors but they appear on the Home » administer » settings »
search page after the cron job has run.
And my site is search index is stuck with only 9% indexed.
These are the messages...
warning: array_keys(): The first argument should be an array in /includes/menu.inc on line 328.
warning: Wrong parameter count for min() in /includes/menu.inc on line 328.
Comment #6
killes@www.drop.org commentedthis is almost certainly a contrib module which is misbehaving. Please disable all contrib modules and try to reproduce. Then enable one by one until you found the culprit.
Comment #7
JHeffner commentedThe same issue popped up for me when I started to use the epublish module; more specifically with abstracts which are added into the content types configuration by the module.
Comment #8
magico commentedFollowing killes... probably a contrib module.
Comment #9
(not verified) commentedComment #10
okeedoak commentedJust for the record I moved my Drupal 5.7 site from a dev environment on one server to a live environment on another server and experienced this error. My solution was to disable and re-enable the devel module. No more error.