A typo has occured in one of the slides (Fausili instead of Faulisi) and has been corrected by my client, but it never got represented in the actual slider. Client supposed it was due to not having a license (LS came with theme), but I doubted that. Now after getting a license, problem persists, but I got support ;-). Thanks in advance for looking into this. If you need credentials, let me know.
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).
Thanks for your quick response. No site optimizer active. Published (of course). Now Duplicated the slider set and imported it in a new field with the original slider name (not the slug), so no cache van cause the problem (as far as I understand), but the problem persists. Awaiting your clarifying response.
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.
The slider still does not work properly. It does not update content correctly. If we duplicate a slider and change the text (and background picture) the titles hang on the original slider.
As you can see, if we save and update the layer slider the info represented differs from what we see on our Layer Slider input screen ("Luka Faulisi", which is correct) vs "Christiaan Kuyvenhoven", which came from the old slider.
But also if we start from clean slide, it does not wat you expect. If we type "Faulisi" and then change it to "Luka Faulisi" it stays "Faulisi" forever. Even if we type a new field with only "Luka", it puts "Faulisi" there as well and does not show "Luka" (on the website). Mindblowing and pretty inconvenient. Looking forward to hearing from you. Regards,
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.
you were o so right. Thanks for your advice, still believe it should not work like that and the first 20-something slides it never happened. I'll keep an eye on it. Case closed
A typo has occured in one of the slides (Fausili instead of Faulisi) and has been corrected by my client, but it never got represented in the actual slider. Client supposed it was due to not having a license (LS came with theme), but I doubted that. Now after getting a license, problem persists, but I got support ;-). Thanks in advance for looking into this. If you need credentials, let me know.
Attached files: Schermafbeelding 2023-01-11 om 13.36.16.png
Schermafbeelding 2023-01-11 om 13.35.56.png
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).
Best Regards,
John | Kreatura Dev Team
Thanks for your quick response. No site optimizer active. Published (of course). Now Duplicated the slider set and imported it in a new field with the original slider name (not the slug), so no cache van cause the problem (as far as I understand), but the problem persists. Awaiting your clarifying response.
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.
Best Regards,
John | Kreatura Dev Team
The slider still does not work properly. It does not update content correctly. If we duplicate a slider and change the text (and background picture) the titles hang on the original slider.
As you can see, if we save and update the layer slider the info represented differs from what we see on our Layer Slider input screen ("Luka Faulisi", which is correct) vs "Christiaan Kuyvenhoven", which came from the old slider.
But also if we start from clean slide, it does not wat you expect. If we type "Faulisi" and then change it to "Luka Faulisi" it stays "Faulisi" forever. Even if we type a new field with only "Luka", it puts "Faulisi" there as well and does not show "Luka" (on the website). Mindblowing and pretty inconvenient. Looking forward to hearing from you. Regards,
Herman
Attached files: Schermafbeelding 2023-03-13 om 12.21.54.png
Schermafbeelding 2023-03-13 om 12.21.44.png
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.
Best Regards,
John | Kreatura Dev Team
John,
you were o so right. Thanks for your advice, still believe it should not work like that and the first 20-something slides it never happened. I'll keep an eye on it. Case closed
Best Regards,
Herman