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 use Divi theme framework. Your plugin is not bundles. I have my license key for LayerSlider activated. And of course my API key from Elegant Themes is activated. I Just started receiving this error when trying to update LayerSlider for Wordpress from version 6.1.0. to version 6.1.6.
When I try to update to 6.0.5 I keep getting this error :
“An error occurred while updating LayerSlider WP: Before you can receive product updates, you must first authenticate your Elegant Themes subscription. To do this, you need to enter both your Elegant Themes Username and your Elegant Themes API Key into the Updates Tab in your theme and plugin settings. To locate your API Key, log in to your Elegant Themes account and navigate to the Account > API Key page. Learn more here. If you still get this message, please make sure that your Username and API Key have been entered correctly”
I noticed in the forum on Envato that someone else had this issue 3 months ago and the support reply was not sufficient as it was the typical "if the plugin was bundled with your theme" Obviously, Divi does not bundle Layer Slider in its core theme.
PS. I use LayerSlider/Divi combination on another website and do not have the same issue. The other website updated fine.
Hey bmw411973,
We have looked into it and the issue is caused by the Elegant theme. The theme overwrites and changes LayerSlider's default methods that could easily result in problems like this.
Unfortunately there is not much we can do from our end as the issue is generated by the theme's behavior.
You will need to contact the author of the theme with this case I'm afraid. They should be able to provide more insight on this matter and hopefully a solution on how you can prevent the theme's custom methods from applying on our plugin.