Revolution Slider Media paths break on migration of the site

Support
#1

I have created my first set of sliders on my DEV server, and have used BackupGuard to migrate the site to my live server. Once there, the sliders were all blank - no images.

In investigating, I see that the problem is that BackupGuard is failing to find and translate the base URL of the media paths when migrating. Thus they still point to the DEV server.

One way I have worked around this in other places, is to remove the base.url and make the paths relative, starting at /wp-content/uploads/…

But I cannot find a way to access the paths directly in the slider UI. Is there a way to edit the media paths? If not - could this be sent to the slider developers as a wishlist item?

#2

Hello @ConsortChorale,

Thanks for posting in!

Please understand that this is not related to the theme. Somehow this issue occurred after you have migrated the site. Just to manage your expectation, we can guide you how you maybe able to resolve your issue. You can install Search and Replace plugin. Search for the URL of the your dev server like http://dev-server.url/wp-content/uploads/ and replce it with http://live-server.url/wp-content/uploads/.

Hope this helps.

#3

We have tracked down the problem. Revolution slider is doing an unconventional save of the media paths. They are being saved to the DB in their escaped form, e.g. http://base.url/wp-contents/uploads/…

It would be better on your part to store them normally, without the back slashes. I’ve also alerted BackupGuard about the issue.

As for your comment that this is not related to the theme - I know it is in Revolution Slider, but while you “bundle it” with the theme, apparently that bundling does not grant me the ability to contact that team directly. That’s why I posted on this site. Please pass on my suggestion for them to properly save the paths in the DB. And thanks for the tip on the Search & Replace plugin - that should hopefully suffice for an ability to edit the paths.

Thanks.

#4

Hey @ConsortChorale,

Escaping URLs or special characters before saving is not unconventional. That is pretty common and database migration systems usually support them or the user should take them into account.

We’re happy that your issue is not resolved.

#5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.