Only visible when logged in

Try disabling W3 Total Cache briefly and see if that resolves your issue. It looks like you have some combination of combining, minifying, and deferring javascript active which seems to be causing an issue. You may need to play around with these options to find which combination of settings works without causing issues with the ditty scripts.

Thank you. W* Total Cache deactivated did not solve the issue.

You say “some combination of combining, minifying, and deferring javascript active”? Where exactly can I play around with that?

Those settings would be within W3 Total Cache. Can you leave it disabled for a little while today? I’d like to check out your site without it running.

OK, I had switched W3 on again but now deactivated it one more time. I have also updated it to the latest version. I will leave it like this.

Thank you. It looks like even with W3 disabled, the site is still using it’s cache (see html source: https://imgur.com/a/pFrMN9q). I know W3 total cache adds a constant within the wp-config.php file that is only removed if the plugin is fully deleted. That may be the case with the cache as well. Here’s a thread referencing this: https://www.ads-software.com/support/topic/page-cache-disabled-but-wp_cache-still-defined/

I’m not sure of the best way to get rid of the cache while not deleting W3 total cache… Possibly manually removing the WP_CACHE constant and also manually deleting the cache folder via FTP in the wp-content directory. It’s a bit of a pain (I’m not a big fan of W3 total cache… it’s overly complicated).

I did find the settings for minifying and it’s located Performance > Minify and make sure JS minify settings is disabled.

If minifying isn’t enabled and this isn’t the issue, which it may not… When I view the source in the developer tools it actually doesn’t look like scripts are combined. But, I do see “defer” on every javascript file, which could be the issue. In order to check this out, I found this article: https://blossomthemes.com/defer-parsing-javascript-wordpress/ and scroll down to “Defer Parsing of JavaScript with W3 Total Cache Plugin”. This provides the steps to defer scripts, so you’ll need to use this to do the opposite and not defer scripts.

Let me know if this helps.

I have now deleted W3 cache. For the moment, Ditty is still not visible unless I am logged in.

• This reply was modified 1 year, 6 months ago by ulf01.

Thanks for the update. I am no longer seeing the javascript errors that I was seeing before. I do see that scripts are still being deferred, so there must be something else doing that on your site.

Regardless of that, I am not seeing html for the news ticker in the source html of your home page. Can you let me know how you are adding the ticker to your site?

Also, just to confirm, it looks like you are using the Legacy news ticker correct?

Many thanks for all your efforts. The (legacy) ticker is added with a shortcode: [ditty_news_ticker id=”452″]

This morning I started the page and the ticker didn’t work. Nothing has been changed! Then I logged into WP and loaded the page and it didn’t work. Then I re-loaded the page and the ticker worked. I logged out of WP and it worked. I started a Safari Private Window, loaded the page and the ticker worked. I started Firefox and the ticker worked.

So, it seems like this is kind of unreliable in some way…

• This reply was modified 1 year, 6 months ago by ulf01.

You’re welcome and thanks for the info!

I realized I was searching for the html of the new Ditty post type, which is why I didn’t see it in the html source. I see the legacy ticker now on the home page.

It’s possible you still had cached browsers, possibly? I’m not sure, but this behavior definitely isn’t normal. Please check it out throughout this next week and let me know if you still see inconsistencies like this.

Have a great weekend!