Local Community

Importing Issues on a Mac

Issue Summary

_Hello, I’m totally new to Local.I’ve downloaded a public site from the server with “All-in-one WP Migration” Plug-In. After importing the site in Local, I got the attached picture with some issues I do not understand. Do you have an idea what the reason for this might and how I can solve this?

My second question is, if it is necessary to set up locally the same database with the same name as on the live server to re-import the site successfully to the live server after finishing? What is the easiest process to export the site from local and import it (migrate it) to the server of the hosting provider?

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?

I have a similar issue with a second site. Both have outdated themes. On the server is PHP 7.2 and apache running (Hosteurope.de)

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?

Yes

Replication

Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!

  1. Setup a new local site
  2. Installed “All-in-one WP Migrate” Plugin locally and on the server
  3. Export Site as File with “All-in-one WP Migrate” Plugin from server
  4. Import Site as File with “All-in-one WP Migrate” Plugin from server

System Details

  • Which version of Local is being used?

5.8.1+493

  • What Operating System (OS) and OS version is being used?
    • For example: macOS Catalina or Windows 10 Professional

Mac OS Catalina 10.15.7

Thanks for helping.

Best reagards,
Frank

Hey @FrankM, Welcome to the Local Community Forums!

To your first question about why the site looks broken in Local – from the screenshot, it looks like those are just PHP warnings. It would be best to fix those by either fixing code, or updating plugins. If you aren’t in a position to do that, then you might consider disabling error reporting until you are in a better position to fix those underlying issues.

Here’s a help doc that goes into more detail about how to make adjustments to the kinds of warnings that are displayed in Local:

https://localwp.com/help-docs/warnings-and-errors-in-local/

It doesn’t have to be the same, but having them be the same will mean one less thing you have to consider when deploying the site.

If the remote site supports Local Connect (right now WP Engine or Flywheel) then that would be the easiest way to deploy a site.

If the remote site is hosted some place else, then you’ll likely need to either export the site by right-clicking on it and selecting “export”, then manually import the site on the remote server.

You might take a closer look at this blog post that outlines some ideas for deploying a site:

Thanks a lot Ben!

Meanwhile I could find out, that the PHP warnings mainly came from only one outdated plug-in (and a few outdated scripts from the theme).

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