Joe Litobarski

Ok, I’ve identified the problem. Apparently, it’s an issue if the theme uses the box-shadow property for its widgets. I restyled the banner so it didn’t use a box shadow and that solved it.

Just tested – I can confirm this solution works! Great stuff, thanks everyone!

Unfortunately, when I remove ‘footer_widgets’ => array( ‘sidebar-1’ ) then it automatically defaults to scroll without the option in the reading settings of changing to click. However, it’s possible to override that by adding ‘type’ => ‘click’ – so that’s what I’ve done, and it works perfectly!

Thanks so much! I’ve now updated to 3.3 and everything is working for me. I can’t use automatic scrolling, but I was anyway using click to scroll – so for me this definitely works.

Awesome! Thanks for your help!

I bet if you remove ‘footer_widgets’ => array( ‘sidebar-1’ ) it will work.

Yup, that worked for me (although then it obviously messes up the footer widget – still, that seems to be the problem!).

Wait, yes – you’re absolutely right!

I’ve now updated to 3.3 with Infinite Scroll deactivated and the issue is gone. Sorry about that, I’m not sure why that didn’t work the first time I tried it.

And it works with Infinite Scroll activated in Twenty Fifteen – just not Twenty Twelve/Thirteen/Fourteen.

Some new information: I can confirm that the problem does NOT appear when I use Twenty Fifteen.

So, whatever the issue is, it seems to be limited to Twenty Twelve, Twenty Thirteen and Twenty Fourteen or child themes of those themes.

Oh, and I forgot to say – this is all without Infinite Scroll activated. So, for me at least, it doesn’t seem to be an issue with my having modified any code or with Infinite Scroll.

I’m also experiencing the problem in a Twenty Thirteen child, and can reproduce the issue with Twenty Thirteen out of the box (i.e. without a child theme or any plugin or code modifications).

So far, I’ve been able to reproduce the issue with Twenty Twelve, Twenty Thirteen and Twenty Fourteen – all on fresh installs with no plugins or child themes.

My host says they run XCACHE and Varnish on their servers. Hope that helps!

I’m using PHP version 5.6.

I’m hosted with one.com – and can’t find anything about layered caching on their site. I’ll write to their support to double-check.

P.S. This is on a clean installation of WordPress 4.0.1 with Jetpack 3.3 and no other plugins. Tested themes were Twenty Twelve, Twenty Thirteen and Twenty Fourteen.

P.S. This is on a clean installation of WordPress 4.0.1. and Jetpack 3.3 – no other plugins. Tested with themes Twenty Twelve, Twenty Thirteen and Twenty Fourteen.

Just tried deactivating Infinite Scroll. No luck, unfortunately – the same problem appears whenever toggling Widget Visibility options in the Secondary Widget Area.

@bernardop_rj Can you check if the problem is just in the Secondary Widget Area? If you move your widgets over to the Primary / Main Widget Area, does it work?

Ok, I’ve got something (hopefully) useful to report!

I tried installing on another server with a clean WordPress install and managed to reproduce the problem. However, I’ve discovered that the problem only occurs in the Secondary Widget Area of whichever theme I’m using. Widget visibility is working as expected in the Main Widget Area, just not in any other widget areas.

So far, I’ve tested in Twenty Twelve and Twenty Thirteen with the same results.