Home>Support>Vantage Premium failing after db restore

Vantage Premium failing after db restore

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

I have a wordpress site that I deleted by mistake. I have restored the files, but the database was out of date (site has been migrated since the last backup). I downloaded the db and replaced the old URLs for the new one and this seems to have worked.
However, I use Vantage Premium on the site and this isn’t working properly. When I go to edit a page, it loads in text format. If I click on Page Builder it asks ” Would you like to copy this editor’s existing content to Page Builder?”
If I say yes, it puts all the content into one box, whereas previously I had several.
Also, when I go into themes and theme settings, it displays a page with all the text against the left side of the page just showing hyperlinks.
I hadn’t made any changes to the contents since the migration, so although the db was out of date, the actual files were up to date, so all that I’ve done is update the url’s in the db.

URL: http://www.velociraptorcycle.org.uk

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 9 years, 8 months ago Greg Priday
    Hi, I Work Here

    Hi Kevin

    SiteOrigin Page Builder (which is the plugin that handles everything behind the “Page Builder” tab) uses what’s called the Post Meta database. This table stores extra meta information for a post or page.

    If this table isn’t transferred properly, then your Page Builder content wont come along. Only the plain text version that’s stored in the posts table.

    Moving and restoring database tables can be quite complex, but here is a complete guide on how to do it. There’s a section on how to do the post meta tables too.

    https://premium.wpmudev.org/blog/moving-wordpress-site/

  2. 9 years, 8 months ago kevinmarkwhite

    Hi,
    Thank you for your reply.

    After my initial post I got it working…about 90% working. The site was loading ok, but the page builder was only working on some pages. I’ve today tried your suggestion, exporting the table from the original db, making url changes and reimporting it into the new db.

    I works in terms of the page builder working on all pages…but I lost my images!

    I’ve tried a few things, but can only get page builder OR images to work! I’ve done a search and replace on the exported table etc.

    There aren’t that many images on the site, so I guess I could just update each page, as that would be much easier than trying to re-do the page builder formats.

    Do you have any ideas why this might be the case?

    Thanks
    Kevin

  3. 9 years, 8 months ago Greg Priday
    Hi, I Work Here

    Hi Kevin

    The widgets Page Builder uses will either have images stored as a URL or an attachment ID. The SiteOrigin Image Widget, for example, uses an attachment ID. The SiteOrigin Editor and Visual Editor widgets will store the image as a full URL.

    For widgets that store the full URL, you can just do a search and replace. For widgets that store the attachment ID, you need to ensure that the attachment ID is the same as it was before.

    If you follow all the steps in that guide though, you should be very close to a complete recreation. You might just need to reinsert a few of the images.

  4. 9 years, 8 months ago kevinmarkwhite

    Hi Greg,

    Thanks for your help. I’ve got it working now.

    I edited the “siteurl” and “home” fields with the new URL locally.

    I created a fresh install of WP on the server. I then dropped all the tables from the db and imported the whole of the old db (it was in phpMyAdmin SQL format, not MySQL as the new db, so wouldn’t let me replace tables etc).

    I then went into WP and used the “Better Search Replace” plugin to change the URL’s (leaving the GUID box untucked). I then set the permalink config to the correct format.

    (I think part of my problems were the permalink’s were set wrong in WP and I was also using Textedit to search and replace. Textedit changed everything, including the GUIDs and didn’t deal with serialisation, which at that point I didn’t know about).

    So it is now working perfectly. Initially the circle widget links weren’t working, but I manually changed those to the full url path and all ok now.

    Thank you for your help, it pointed me in the right direction. I now have several backups!

    • 9 years, 8 months ago kevinmarkwhite

      Forgot to add – along with uploading the db, I also uploaded the wp-content folder from my original files backup, overwriting the one created by the clean WP install.

  5. 9 years, 7 months ago Support Assistants

    Hi Kevin

    We’re really glad to hear you’ve recovered. Thanks for the detailed update.

    All the best with your site.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More