jeffrod

I ended up buying Pro and it worked exactly as I wanted. With all the time I was spending trying to find a good solution, it just made more sense to spend the $20 and give it a try. It seems to have paid off. Pro works just how I want and was very easy to get going.

I had been using regular tabs and Incognito tabs to test it out. There is no server cache that I am aware of. I’m glad to hear that the day functionality exists in the Pro plugin, but I’m not ready to commit to that if I cant even get the Basic version to behave/dismiss properly. What is the intended design for the lightbox when it is dismissed? Is it supposed to continue to pop up on every page? I tried this on Chrome, Safari, and Firefox and got the same behavior in each one: dismiss the lightbox, but it continues to show up on every subsequent page load.

I tried adjusting the lightbox behavior to see if that helps. I was able to get the lightbox to refrain from loading on every page after a dismissal or successful submission if I enabled the Reappear after [1] day using cookie setting.

Unfortunately, this still does not provide acceptable user experience for two reasons. First, I cant change the [1] day value. If someone dismisses the lightbox, I dont want to harass them every single day. Something like once a month would be more appropriate. Why isnt this value able to be edited? Second, the lightbox still appears the next day for users that submitted the form. If a user submitted the form and made it on to the mailing list, they should never be prompted to sign up again. I was able to test this behavior by adjusting my computer’s system time to simulate what the behavior would be after several days.

• This reply was modified 8 years, 2 months ago by jeffrod. Reason: bad [em] formatting

I just figured this out. My users were tagged as “Editors” which still are apparently considered by WordPress to be Administrators.

current_user_can('administrator') == true

I changed my users to Author and then the plugin worked as advertised.

Did either of you get this resolved? I also simply doesnt work for me. I deactivated all other plugins and switched to 2015 theme and the WordPress admin still shows everything – all Posts and all custom post types.

Actually, I guess is_home is supposed to be true.

Anyway, after digging around the source code of DW and WP I was able to figure out the right settings for DW. I must admit, I wasn’t expecting everything to be triggered to ON/YES by default. But I guess that is inline with the default WordPress widget behavior.

Still, once a widget is set to dynamic, it seems to make more sense to me to whitelist all the places the widget should appear rather than blacklist them. I know theres the “Set all options to NO” field so it can be done either way. I just got a little confused is all and now I’m rambling.

Thanks again for your help and attention. I have what I need.

I’m not afraid of a little debugging and PHP code! ??

It looks like WhoAmI = 'front-page' because $wp_query->is_home = true. That is definitely wrong so I guess I have to dig a little deeper but it doesn’t seem like this is a DW issue like you suspected. Thanks for the direction. If it looks like it comes around full circle and becomes a DW issue, I’ll post back here. Otherwise, thanks for the help.

Thanks for the quick response. Even if it was reported on a page, it seems odd that they would be rendered on the archive since DW should be checking if it is on the section page or below – and the archive is not in any of those sections. At least In my mind, the values being reported shouldn’t matter at all in this case… but obviously if I knew better, I wouldn’t be asking this question!

I’m somewhat new to WP theme development but I dont mind hacking the Canvas base theme if I have to. Can you point me in the right direction to make the theme report the proper value?

Great! I’m glad it was an easy and quick fix!

Thanks Stephan. I worked around the issue for now by modifying your source code and adding an additional event that was triggered at the end of the slide transitions. I handled that event and used my custom handler to force IE 8 to take a regular Fade transition.

I can try to push that to your repo if you have that capability.

I suspect that this won’t get a ton of attention so maybe a solution would be to provide a built-in alternate transition for IE8 browsers? Or maybe you can just provide a hook into the JavaScript so I can manually take control of the transition and selectively serve a hardcoded transition to IE8?