• Resolved Milan

    (@milanxy)


    I have a 4GB file with the entire content of the website. Now I will try to import to localhost. PHP and database versions are the same. I edited PHP.ini – increased to 5GB file, longer time etc.

    What all needs to be set so that the import ends well?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Milan

    (@milanxy)

    Import only database work, but not all tables imported. The problem is the files. I copied the plugins and images manually. The site looks functional, but only time will tell.

    Plugin Author Yani

    (@yaniiliev)

    It sounds like you’ve taken some solid steps for the import. With a 4GB file, a few additional adjustments can help ensure a smooth import process:

    1. Since you’ve already adjusted your php.ini, double-check the following settings:
    • memory_limit
    • max_execution_time
    • post_max_size
    • If not all tables were imported, this is likely because they are not using the $wpdb->prefix defined in wp-config.php. The plugin only exports prefixed tables.
    • Manually copying plugins and images, as you’ve done, can be a good approach, especially with larger sites. Just ensure that all paths are correctly set and that permissions are set appropriately on your localhost.
    • Check PHP and server error logs for any issues that occurred during the import. This can provide insight if any further adjustments are needed.
    • This reply was modified 1 month, 1 week ago by Yani.
    Thread Starter Milan

    (@milanxy)

    The most important is the “max_execution_time” parameter (minimum 1800).

    Of course, I have the prefix. No import of empty tables and probably damaged tables. I don’t know. It should not be damaged. Before setting up a working configuration, I had a lot of strange errors in phpMyAdmin during import. It was better with this plugin. What didn’t work through phpMyAdmin, it worked fine with the plugin.

    For a real server import, I recommend backing up everything separately. The database was also imported for at least 24 minutes (every test). It is good to divide the database into several parts. Even the previously marked tables as faulty, after the division they passed in order.

    I didn’t look at the log errors. Every error means searching on Google and longer work time.

    Anyway, I solved my problem.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.