Moving OceanWP/Elementor site to localhost has bugs

  • I have created a client site for the first time using OceanWP and Elementor. I really like the combination overall, and want to consider it a standard combo for some applications moving forward. (For what it’s worth, I started on the client’s host and password protected just so I could show them a few example pages. Now I want to work fully offline.)

    For around 2 years now I have been using Duplicator to move sites back and forth between host/localhost without hardly an issue, and when I had minor bugs, I could figure them out. However, I cannot reason my way through it this time. Details:
    > Website is built with OceanWP child
    > Using Xampp (which I have for 2+ years)
    > Follow Duplicator protocol to the letter (package + installer)
    > All files confirmed to have moved into target folder in xampp/htdocs (including wp-config, all media in wp-content/uploads including /elementor folder, etc.)
    > Launching localhost site brings up every page, all links working, but some formatting missing (background colors, media file links broken but files available in folder)
    > The logo in the header appears. No other image works. (broken image icon shows for each)
    > All plugins on localhost site appear and are activated (or not) as per the original site selection (including Elementor)
    > I’ve made sure the paths/permalink is set the way I always have set it in the past.

    Because this is a first after a few hundred runs across a dozen or so sites, I wonder if there isn’t some interaction. Or is there a better tool or process recommended for the back-and-forth move to local? I can do manual, but find it tedious if I don’t have to do it.

Viewing 5 replies - 1 through 5 (of 5 total)

  • The good thing is it should be pretty easy to figure out what is wrong with the image paths by simply inspecting them and seeing what is wrong and then take corrective actions in your migration plugin (if it allows it).

    I’ve never used duplicator but I’ve seen many all-in-one type migration plugins that sometimes miss the mark because it is unaware of special tables used by some plugins and you end up with missing data or embedded file paths that are not fixed. This is one of the reasons Elementor provides an area called Tools in the Elementor settings (back end) to find and replace urls.

    Additionally whenever I build out a site I try my best to use relative paths when I can or modify a fields setting manually after selecting an item from the media library, I’ll remove the domain name so the path is /wp-content… so that no matter what domain I later move to, the path will be proper.

    I’ll often use the wp-sync db plugin which can do site-to-site push/pull migrations or you can do direct database exports with it and define the search and replace domain information at that same time. I’ve used this plugin successfully with Elementor many times.

    Best of luck getting it all handled.

    @johnwp413 –

    Can’t speak for OceanWP as I use GeneratePress exclusively, but I have successfully moved many Elementor, BB with GP, Gen + DWB sites, both ways, using All In One WP Migration. Note that all of these sites have been under their 512MB limit of the free version of the plugin available on the WP plugin repo:

    https://www.ads-software.com/plugins/all-in-one-wp-migration/

    Perhaps give it a go ??

    Cheers!
    Lyle

    Thread Starter johnwp413

    (@johnwp413)

    @snifflevalve

    After I struggled with Duplicator, I tried All in One. The results were almost identical. That’s why I decided to come to the Elementor WP support page. Rightly or wrongly, I’m assuming it’s associated with the theme/builder tool more than the service used to package and move. Thanks for the suggestion.

    @johnwp413 –

    All I can say then is that it could be with the theme because I have successfully used AIOWPM with Elementor (with and without Pro), Beaver Builder (Lite, Standard, and Pro), GeneratePress (with and without Premium), Genesis + Dynamik Website Builder plus many other plugins and these sites have been moved from / to XAMPP on Win 10 to / from various web hosts. All without fail. Pretty sure it is not an Elementor issue.

    • This reply was modified 7 years, 10 months ago by snifflevalve.
    Thread Starter johnwp413

    (@johnwp413)

    @snifflevalve

    Good point. I selected OceanWP because I wanted to experiment with Elementor and there is an organic tie between the two – it may not be the same team, but they seem to collaborate and recommend back and forth. As if optimized for each other. And it’s a little late to change themes at this point. At least to do so quickly.

    Too bad I’ve hit this snag so far. Just cannot find the right place to discover someone who may have addressed this exact theme + tool (Duplicator) + Xampp issue before.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Moving OceanWP/Elementor site to localhost has bugs’ is closed to new replies.