I am getting two errors back in our log files each time cron.php runs:

1: array_keys(): The first argument should be an array in /home/realself/public_html/includes/menu.inc on line 328.
2: Wrong parameter count for min() in /home/realself/public_html/includes/menu.inc on line 328.

Started 3 days ago after a significant data import, where we also enabled the ping functionality.

Any ideas on what might causing this?

Comments

bradleyg’s picture

I'm also experiencing this problem. Haven't investigated yet. I'll let you know if I find anything.

Anonymous’s picture

Thanks - 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

varr’s picture

Version: 4.7.0 » 4.7.2
Component: other » search.module

Has 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

varr’s picture

Component: search.module » other

So 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'.

nigels’s picture

Priority: Normal » Critical

I 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.

killes@www.drop.org’s picture

Priority: Critical » Normal

this 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.

JHeffner’s picture

The 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.

magico’s picture

Status: Active » Fixed

Following killes... probably a contrib module.

Anonymous’s picture

Status: Fixed » Closed (fixed)
okeedoak’s picture

Just 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.