I have no caching plugin installed, whatsoever. Though the hosting provider is probably using a caching feature (Flywheel). Could that be interfering?

I’ve tried 2 sites and both show the same page transition issue on any type of device using Safari:
– goo.gl/82wbXl (currently disabled the page transition and only the preloader still active, which works without issues)
– goo.gl/UfWnlT (click on the logo top left and then try to go back)

As the page transition for the first site is disabled, the preloader works fine. So it’s probably the transition code having issues with other code? Though like I said, the second site does not run ANY plugins at all (not 1!), so if it is interfering, it’s likely with something in the theme itself. That second site is a clean test site where I have only installed the Enfold theme.

Perhaps it is good to know I’m using a Magic Mouse from Apple and swipe the mouse with my finger to navigate through next or previous pages instead of pressing those buttons in the browser or using keyboard buttons.

I haven’t fixed the caching issue yet because with the recent few theme updates it kept getting removed and forgot to add it in again.

There is only one more issue that remains, and I see it on multiple website with multiple devices (iPad, iPhone, Mac) in Safari. When I hit the “back” button of the browser, most of the time the preloader does not load the page and it needs a page refresh to load the page properly.

Hi Elliott.

No, that’s a different situation. This edit broke the slider as in not showing caption AND image for any slide ever. That other topic talks about an issue that sometimes does not show a caption.

The issue here occurred after editing the shortcode.js file and was fixed again after going back to the standard code. The other issue has been going on for several months.

Great, thanks!

I’ve updated the site, flushed cache on server, did some local tests and it seems the issue isn’t solved yet. I cannot say 100% for sure it’s not my local cache still interfering, but so far I still see the caption not always appearing. :(

Perhaps you can test it a few times to see if it still occurs on your side. If it does and you’d like another check in the CMS, the login credentials are still valid.

Maybe I’ll also try recreating the fullscreen slider and see if that helps after this update.

WOW, I just skimmed through the list of changes and am really impressed! Lots of great new features and especially several that I have long been waiting for and was beginning to consider looking for plugins.

I’ll make the update tomorrow and check the fullscreen slider caption. I will let you know if it’s solved.

Ok Ismael, I’ll definitely let you know. So far no issues, but waiting for an opportunity to arise where I can clearly see if this works.

And once again, perfect for me!

Thank you, Elliott!

Hello again Elliott,

Thanks for the suggestion. Unfortunately I cannot change the .htaccess file on my hosting provider. Also, I’d prefer to just disable caching for one specific file (custom.css) as that is the one that changes the most when modifying CSS for the Enfold theme. I rarely touch other files.

I found this, but not sure where I would add this to the theme and how to specify it should refer to custom.css instead of style.css (unless I just change “style.css” to “custom.css”):
<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); echo '?' . filemtime( get_stylesheet_directory() . '/style.css'); ?>" type="text/css" media="screen, projection" />
This basically automatically adds a version number to the file so it is regarded as a new file and requests a fresh download.

My site is never completely finished. New things get added, changed and optimised daily. I often overrule existing style (specified by Enfold), but if the visitors don’t see my version, they will see a broken result.

For example:
I added a new fullscreen slider to the homepage. I set the caption to “center without frame”. This already has existing styles specified by Enfold, but I need to change several aspects of it, such as the positioning (top instead of middle, etc.). If the visitors still have the previous custom.css version in their cache in which that style isn’t overruled yet, they will see the caption in the middle of my picture instead of at the intended top position, and so on.

If tomorrow I change my fullscreen slider and want to change the font-family, this too will be done in custom.css, but only those who do a force refresh (= no one except me) will see the change.

Personally, I don’t even think the custom.css file should be cached in the first place, or not longer than a single session (like only lasting an hour). That is THE file we (Enfold users) will probably be modifying the most and the small file size would most likely not even impact load speed at all. If that’s the file we modify the most, I assume everyone would prefer these changes to be immediate.

Using the custom CSS text area in Enfold options (inside WP admin) is not a solution for me. Not all styles are accepted (for example changing font types), possibly because there are still other styles rendered below it. And I have about 10 languages, meaning I need to copy-paste every single change to every language. I also find it too risky to add anything there, because there is no turning back after saving changes (undo, backup different versions, …).

Thanks for your feedback Elliott!

I’ll try flushing the cache next time, but I assumed it would be purely local caching because some people see it and some don’t. If new visitors see it correctly, while returning visitors don’t, doesn’t that mean it’s the local caching? If it would be server side caching, I suppose new visitors would see the same thing, no?

Sorry if I get this all wrong, it’s a bit confusing.