I ended up creating the slider in Cornerstones native slider elements, but you might want to tell people that in V7 of Slider Revolution, you must migrate your slider in v6 first. Apparently that is the core issue…?
Hello @Kev,
Thanks for writing to us.
I have tested this on my local setup with Pro theme version 6.8.1, WordPress 6.9.4, and Slider Revolution 7.0.4, and it works correctly. To resolve the issue, deactivate the Slider Revolution plugin and reinstall it directly from Pro/X > Extensions > Slider Revolution. Always back up your site’s database and files before deleting any plugin.
Thanks
I have the same problem. It seems to be related to the Complianz plugin.
My first step was to undo the changes and ignore the Slider Revolution update for the time being. Of course, this isn’t a long-term solution.
I do not have the Complianz plugin. But the update sure did break my site.
This is what it is supposed to look like:
This is with the Slider Revolution update:
Same thing here in my case all modules appear as a not migrated
@prakash_s I think I have seen too many comments in the forum about this plugin to show that this is not just an isolated issue. It could possibly… and I’m just speculating here… that there may be classic elements involved?
@Juanjo can you verify with your site? I do see on Slider Revolution’s site that the modules need to be migrated first, which is something Slider Revolution has promoted, but because Themeco packaged it, I did not get that notice.
Hey @Kev,
Yes, there are many comments but there are many users with working sliders as well. The key here is testing in staging before updating the live site. That is the best practice for doing any website updates.
To th Slider Revolution issue, you need to switch to the SR 7 engine before updating to the latest version. We do not have notification for that as Slider Revolution is not our product. We have no control over it nor can monitor system changes. If you wish to receive bundled plugin news, you need to purchase the plugin and subscribe to the plugin author’s newsletter.
We cannot downgrade Slider Revolution. It would be best that you contact your web host to revert to the previous working version of your site. From there, you can set up a staging copy and test converting your sliders to SR 7 system.
About the Classic Slider Revolution element issue. Please note that we strongly encourage to switch to v2 or non-Classic elements. That includes Slider Revolution. Just copy the Slider Revolution shortcode to a Raw Element.
Yeah, while it is true that this is not your software, you do offer it a part of the package with your software. I appreciate that this doesn’t mean you can support everything about it but… surely, “it broke my site entirely” should warrant a bit more recourse than what is being offered here.
What exactly would one do to “switch to the SR 7 engine before updating to the latest version”? Can you perhaps elaborate and be a little more helpful here?
1 Like
Yes, previously doing the conversion to SR7 and upgrading later the ‘no migrated’ seems to be solved.
As you said the classic Revolution Slider element don’t work with this new Revolution Slider version: the list of sliders not longer appears as before.
I’ve solved the issue embedding the sliders as a shortcodes from the embed option in sliders:
Thanks to all for the support
Yes, I feel that if there was a major issue change with provided software, there should be relayed communication about it. As I dug deep with Slider Revolution, I saw that they warned about the newest version, but I hadn’t had the need to change my slider on that one site for some time and do not have a paid version and therefore did not get the memo.
So I can confirm that the old classic rev slider integration does not work. Raw code with the shortcode is the move to use for sure. However, I can also confirm that the “not migrated” error is weirdly only happening some of the time.
I happen to have a copy of 6.7.51 I have been downgrading to as Ive been experimenting. On one client site, I had to downgrade and upgrade 2x before all slides stopped showing “not migrated”. Arbitrarily, they just all stopped displaying that error after the second time I tried and then the raw code implementation worked fine.
This is very strange and I feel like it deserves some further investigation.
I have seen this pattern now on 2 client sites so far. Anyone else have info on this or anything to add to the story so far?
I can confirm that i´ve downgraded 2 sites to 6.7.51 to save my sanity and time for investigating it further.
Use this code if you don’t want to upgrade to v7 for the moment
add_filter ('site_transient_update_plugins',
function ($value)
{
if (isset ($value->response['revslider/revslider.php']))
{
unset($value->response['revslider/revslider.php']);
}
return $value;
});
And i can confirm that complex queries with hook revslider_get_posts won´t work well too!
1 Like
Our latest theme update will fix the issue with Slider Revolution 7 and our Classic Slider Revolution Element.
2 Likes
Thanks for recognizing the issue and thanks for the fix! I think I am going to try to avoid that plugin from here forward.
1 Like
I hoped the issue will get resolved with the latest theme update - I am using X theme version 10.8.4 - but unfortunately the slider revolution plugin still crashes my whole site. Is there a recommended method for dealing with this error?
I’m just stopping using the third-party sliders until I have to. The built-in sliders are good enough for most of the work I do.
Hello @wrkotte,
I would suggest you please create a sepreate a new thread and share the admin login credentials, so we can check it on our end and guide you properly. Please share the exact page URL as well.
Thanks
For anyone experiencing a similar issue. It seems you need to prepare your slides for migration to the new SR7 version first: https://www.sliderrevolution.com/help/whats-changed-from-slider-revolution-6-to-7/
After that, the error message will no longer appear. Unfortunately, however, not all sliders are automatically migrated to the new version during the update. To avoid that save each slide in the old version 6.7.5x. The admins here seem to be aware of the problem. A helpful user has posted a possible workaround here: Slider Revolution Issue. "not migrated"