PHP Notice output breaking nginx proxy about wplib-box HOT 6 CLOSED

@greghaygood Thanks for the report.

So this might be the case that you used your code instead of ours? Our code should have included turning on debugging in the wp-config-local.php. Can you check that?

This was included in that file:

define( 'WP_DEBUG', true );
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);

If that is not the issue then I would definitely like to address it.

BTW, is this the theme?

• http://www.layerswp.com/

from wplib-box.

This is a vanilla install of wplib-box, and the first thing I did to it was to install the Layers plugin. So my wp-config-local.php matches what you have here.

And yes, that's the theme. I made no changes since it failed immediately, so you should be able to replicate easily.

from wplib-box.

@greghaygood Okay, will try to reproduce.

from wplib-box.

@greghaygood So I cloned wplib/wplib-box and downloaded and placed the Layers theme and was not able to get it to crash.

I then searched for the string 'to silence this notice and keep existing sidebar content' and found in one place in WordPress core's register_sidebar() function. I think searched for everywhere that function is called and in most cases it is called with a partially hardcoded string for 'id'.

The only place I could find that was not hardcoding the id is a LayersWP function register_dynamic_sidebars() that iterates over $a_layers_widget->get_dynamic_sidebars() (class Layers_Widgets) Based on the data you have in your wp_options table it is possible but even that seems unlikely.

So I uncommented the if { ... } to force the error message to trigger and then it did, but the Query Manager plugin caught the error messages and displayed them in a debugging console accessible via a red flashing button on the Admin Bar.

So I am at a loss. I would love to find out why and how this failed, but I think I might need your test DB and any code that goes beyond just the box as cloned and the theme as downloaded. Let me know if you want to package that and send to me; you know how to get it to me.

BTW, one potential is if you have an add_action( 'register_sidebar', ... ) in your code, if the filter in not returning the correct value. But even then, the Query Monitor caught the error when I forced it to happen so not sure how to fix... Help?

from wplib-box.

Thanks for digging in. I just PM'd you a copy of the Site+DB so hopefully that will better help illuminate the issue.

from wplib-box.

Odd - I just wiped the DB (didn't change anything with the code) and let WP re-install, and now the errors are showing in the browser. ¯_(ツ)_/¯

I'll close this until I find something replicable. Thanks!

from wplib-box.