Hi Herman,

Thank you for getting in touch with us. My name is John, and I'm happy to assist you today.

Please ensure that the changes were published instead of saved as a draft by pressing the Publish button at the bottom right corner of the editor. If that's not the case, it might be a caching issue. If you're using a site optimization plugin, you might need to clear/purge the caches manually. This is true for other solutions where caches might be involved, such as server-side optimization solutions or using a content delivery network (CDN).

This is very strange and shouldn't happen. I can only think of one additional cause: translation plugins. If you use a plugin or service to localize your site, it's possible that the content is not coming from LayerSlider. Instead, it comes from the localization plugin, where you might need to update the translation for that string.

Hi Herman,

It's almost certainly caused by a localization solution or caching issue. I lean toward the former option since these symptoms are very typical in those cases. If you use a plugin like WPML, Polylang, or another translation solution, please visit their String Translation or similarly named section. LayerSlider automatically registers content in your projects when you use these plugins, and then you need to manage their translations there. While WPML supports a "needs translation" state, therefore it's not a prominent issue there, but Polylang doesn't have this state and requires you to always keep translations up-to-date. This, sadly, comes with the issue you've just described, even if you haven't translated any slider content before. It's how Polylang works, and similar plugins can have this behavior as well.