Limited availability during the holidays
Another busy year is coming to its end, and an exciting year lies ahead. In order to get ready for a fresh new start, our team will spend a few days' rest during the winter holidays. Over the holiday break, we will have reduced staffing from December 20th, 2024, to January 5th, 2025, so please be patient if you do not receive a response as quickly as you normally would.
We send our warmest wishes for happiness, health, and success throughout the coming year. Thank you for your continued support, and may you have a peaceful and blessed Happy Holidays!
I have a slider I am using in a presentation that I am presenting next week and I upgraded to 6.1.5 since it was supposed to contain some fixes to issues I had filed previously but when since upgrading I can no longer edit my old presentations. When I go to any of the slider edit pages, none of the buttons work other than "Back to the list"
I can't edit anything in new presentations either. Please help!
Or an option to go back to 6.1.0?
Hello,
It seems that the new update of LayerSlider ( 6.1.5 ) contains an error that causes issues for certain users in some rare cases.
In case you experience problems with it we recommend you to install 6.1.0 back, which is the latest version before this update.
We have removed 6.1.5 from the auto-update servers for now.
You can download 6.1.0 from CodeCanyon on the following url: https://codecanyon.net/downloads
Downgrading to it should solve all your issues.
We'll release a quick fix soon.
We are very sorry for your inconveniences!
Best Regards,
George
Best Regards,
George | Kreatura Dev Team
We have just released the new version that contains the fix for the error introduced in 6.1.5.
It is available through the auto-update solution. You can check for live updates in the WP Dashboard -> Updates section.
We have also uploaded it to CodeCanyon for manual download, but it might take a day or two for Envato to accept it.
It still isn't working for me
Never mind, I had tried clearing my site cache but that hadn't worked, but clearing my browser cache got it to work with version 6.1.6