New Bug Filling Up Log Files Taking Down Site – 20gig And Counting

I hope you solve the problem soon, our server is becoming really unstable blocking > 50 websites until the logs get deleted.

Hey guys, I work from WP Engine and we are having some customers with this issue … if you will email me the patch at [ email deleted, please do not post those here ] I can test it. Cheers,

Hey all, this fix has been released in 2.0.30. Please note the fix will not remove your error log. You can do that by connecting to your site via FTP and just deleting the error log. But it does resolve the issue and stop additional errors.

If anyone here does update, can you please confirm that the latest update resolves this issue for you? Obviously also let us know if it does not.

Thanks (Erick).

@mpvanwinkle77: I just emailed you separately. (Erick)

Thank you very much.. Iv just updated and will keep an eye on my log file. I will let you know if anything changes.

Updated but all my custom templates for imagebrowser don’t function as they should. Downgraded again

@eyeqt: where are you storing your custom templates at? You can still store them in the theme folder, as will previous versions of NextGEN, and they shouldn’t be overwritten. If your templates are there and not loading, please let us know – preferably in a separate thread or bug report.

You can also store them in the plugin folder. If you are doing that, they will be overwritten, so you’d need to restore them each time. Once you restore, they should be fine.

FYI – I think we are eventually going to create an option to store/read custom templates in a separate folder in wp-content as we’ve done with custom CSS to ensure it’s update proof and theme-change proof as well.

ok I will contact your support team because I have a premium account. Sorry if it was irrelevant but had to say this. As for the files there are in the themes’s folder not the plugin’s.

Everything works perfectly fine after the awesome support from NextGen Team!

It appears the issue may still be occurring. We updated the plugin to v2.0.30 on a site we manage on the 25th shortly after it was released. Everything ran fine yesterday, but we are seeing a similar error in the error_log again today (log file over 300 MB).

1000’s of lines which look like this:
[27-Sep-2013 17:06:50 UTC] PHP Warning: current() expects parameter 1 to be array, integer given in /home/username/public_html/wp-includes/plugin.php on line 404
[27-Sep-2013 17:06:50 UTC] PHP Warning: next() expects parameter 1 to be array, integer given in /home/username/public_html/wp-includes/plugin.php on line 408
[27-Sep-2013 17:06:50 UTC] PHP Warning: current() expects parameter 1 to be array, integer given in /home/username/public_html/wp-includes/plugin.php on line 404
[27-Sep-2013 17:06:50 UTC] PHP Warning: next() expects parameter 1 to be array, integer given in /home/username/public_html/wp-includes/plugin.php on line 408

Is anyone else experiencing this?

@mark – This issue was believed to be resolved but obviously you are not seeing that to be the case. Please submit a Bug Report (https://www.nextgen-gallery.com/report-bug/) with your site’s specifics and referencing this particular issue. We will most likely need to get a set of log in credentials as well as FTP credentials to your WordPress installation folder as well.

Thanks!

– Cais.

Actually, yes, I reported the same information via the support link on your website. Let me know if that was not the correct location. Thanks.

This issue seems to be resolved with WordPress SEO in regards to the sitemap_index.xml file, but if you’re running Yoast’s Local SEO plugin, then there is a problem when try and load the location.kml file. The log file will fill up with the following:

PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408

Verified this with Nextgen 2.0.30 and Yoast Local SEO 1.1.5,

Any ideas for a fix?

@mark, @mccomb: We do think that the Yoast Local SEO plugin has introduced something similar to the main WordPress SEO plugin that’s producing this. Unlike with WordPress SEO, this one seems a bit intermittent and is only triggered periodically. As @mccomb noted, it may have to do with the location.kml file.

For now, to avoid this, we’d recommend deactivating either Local SEO or NG until we can push out a fix. A developer is looking at this today. Thanks. (Erick)

@mark, @mccomb: we’ve pushed a fix in 2.0.31 that should resolve the issue with the local SEO plugin + NG producing errors. Feel free to reactivate and let us know if you see any more issues. Note you’ll still need to manually delete the existing error log if you haven’t already.