@lizgent: Received your bug report. Thanks very much. I replied but your email got bounced back to us. Yours is definitely the error we’d like to see and resolve. What we’d really need is:
1) WordPress login details
2) FTP login details
If you can send those, I’ll forward them to the developer and he’ll look at your site either this evening or first thing tomorrow. You may want to send from an alternate email. Thanks! (Erick)
Same problem here 50Gb error file two days ago. You don’t want to know what my hosting service said. 🙂 .Now I downgraded to .21 version and the odd thing is that today another 50Gb file was created. I will try kerwood’s solution and let you know.
My temp solution still generates errors, but at least its not looping.
[Tue Sep 24 23:31:20 2013] [error] [client 66.249.66.207] PHP Warning: reset() expects parameter 1 to be array, integer given in /var/sites/wp-includes/plugin.php on line 401
[Tue Sep 24 23:31:20 2013] [error] [client 66.249.66.207] PHP Warning: current() expects parameter 1 to be array, integer given in /var/sites/wp-includes/plugin.php on line 404
Geez I thought I was the only one with this issue…
Exactly the same error message. It stopped for a while after I deactivated all the plugins yesterday (I didn’t which was the issue yet),and now it started all over again!
Please fix!
well the major issue is the loop. Several GB of text data are generated in a few hours. Kerwood, I will open again my error logs and see if the error loop has stopped.
Thanks for the quick tip though because all this mess would cost me a fortune 🙁
After Kerwood’s fix the error still occurs. less loops, still looping
how do I stop this? Now that I’ve deactivated nextGen, the error log still keep rolling!
Remenber to restart apache!
sudo service apache2 restart
I have also had this error on my site and my provider took my site down. I disabled all plugins and brought them back up one by one. Nextgen is not yet producing this problem again, but I have not re-enabled WordPress SEO or WP Geo maps which I guess maybe the conflict with this update. Although NExtgen has another error which is not letting me see the insert image screens
Anyone else have these plugins along with nextgen and get this loop error issue? I am reluctant to enable Geo and/or SEO until this has been replicated.
I have the WordPress SEO latest version! I don’t want to disable it though because my url construction is based on this plugin
I am experiencing the same problem, huge error log files caused by a pair of errors repeating endlessly after upgrading NextGEN Gallery from 1.9.3 to 2.0.27:
PHP Warning: current() expects parameter 1 to be array, integer given in /var/www/vhosts/domain.com/httpdocs/wp-includes/plugin.php on line 404
PHP Warning: next() expects parameter 1 to be array, integer given in /var/www/vhosts/domain.com/httpdocs/wp-includes/plugin.php on line 408
Here are some server settings:
Operating System : Linux (64 Bit)
Server : Apache
Memory usage : 37.25 MByte
MYSQL Version : 5.1.69
SQL Mode : Not set
PHP Version : 5.3.3
PHP Safe Mode : Off
PHP Allow URL fopen : On
PHP Memory Limit : 128
PHP Max Upload Size : 10M
PHP Max Post Size : 8M
PCRE Backtracking Limit : 500000
PHP Max Script Execute Time : 60s
PHP Exif support : Yes ( V1.4 )
PHP IPTC support : Yes
PHP XML support : Yes
Hello!
Would one of you experiencing this problem mind posting the following please:
– Which theme you have activated
– A list of all plugins activated
– The version of WordPress installed
Thanks,
Mike
Theme is TwentyTwelve
WordPress version 3.6.1
Plugins:
NextGen Gallery
Google Analytics for WordPress
TinyMCE Advanced
WordPress SEO
Akismet
WP Smush.it
Same Problem!
This url (most visited by GoogleBot 66.249.75.200) fill up your error logs if you have installed NextGEN Gallery by Photocrati and WordPress SEO:
http://yourdomain.de/sitemap_index.xml
Fix it:
Go to SEO, XML-Sitemaps, uncheck the first checkbox (in german: “Funktionen für XML-Sitemaps aktivieren.”)
Now, i have no more error logs. 😉
Hey all, I just wanted to let you know that we’ve tracked down the issue here. The errors are being triggered by new code introduced in one of the latest versions of the WordPress SEO plugin.
This code was introduced to address an existing NextGEN-WordPress SEO conflict affecting xml sitemaps, but caused this new issue as a by-product.
We have a fix for the initial WordPress SEO-NextGEN Gallery sitemap issue, and the same fix should prevent the new code in WordPress SEO from being triggered and thus resolve this error log / db issue as well.
We’re now doing a final round of internal testing and are hoping to push this fix out today. Thanks. (Erick)
