• hello –

    recently i have seen an alarming increase in my php log files, all saying the same thing:

    [04-Jun-2014 04:02:13] PHP Warning: next() expects parameter 1 to be array, boolean given in /blah/blah/wp-includes/plugin.php on line 472

    [04-Jun-2014 04:02:13] PHP Warning: current() expects parameter 1 to be array, boolean given in /blah/blah/wp-includes/plugin.php on line 468

    i realize i could put one of these lines at the beginning of my index.php file:

    error_reporting(0);
    error_reporting(E_ERROR);

    but i would rather deal with the problem. short of rewriting the plugin.php, does anybody have any ideas what might be causing this? a rogue plugin perhaps?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator t-p

    (@t-p)

    a rogue plugin perhaps?

    To find out, try deactivating ALL plugins temporarily to see if this resolves the problem. If this works, re-activate them individually (one-by-one) to find the problematic plugin(s). If you can’t get into your admin dashboard, try deactivating via FTP or SFTP or whatever file management application your host provides. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old.

    Thread Starter edwardsmarkf

    (@edwardsmarkf)

    hello tara – thank you for answering my question.

    i considered that, but i have two problems there:

    1) i never know when the problem will occur, since it does not seem to be consistent time-wise.

    2) this is a multiuser wordpress site with many sites associated with it.

    so, i have added this line into /wp-includes/plugin.php:

    error_log(print_r(debug_backtrace(),1));// 2014-06-06 looking for lines 468 and 472

    now all i can do is wait, and gzip the log file frequently !

    Moderator t-p

    (@t-p)

    I read often on these forums that its not a good idea to tweak core WP files.

    For one, any changes will be overwritten when you nex update the WP. Further, such tweakings may cause other side effects (e.g, security, plugis issues, theme issues…)

    Thread Starter edwardsmarkf

    (@edwardsmarkf)

    true – this is just a VERY temporary measure until i can get the offending plug-in to expose itself. i think whatever it is, it only happens at night.

    url to your site?

    hi all – my idea of including this line didnt do much, except for REALLY fill up my logfiles:

    error_log(print_r(debug_backtrace(),1));

    instead, i found this post:

    https://www.ads-software.com/support/topic/pluginphp-and-wp_filter-causing-an-infinite-loop

    it recommends changing the line from:

    while ( next($wp_filter[$tag]) !== false );

    to:

    while ( is_array($wp_filter[$tag]) && next($wp_filter[$tag]) !== false );

    not much of an answer, but at least my log files wont be filling up!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘repeating warnings showing up in log’ is closed to new replies.