New to the community? Start here

[Shipper Pro] shipper not working

I need to syncronize my local site (http://digitalsigncl.juan) which is not online, obviously, to the https://digitalsign.wpmudev.host/ dev host.

this is an screenshot showing the problem.
https://share.getcloudapp.com/wbuJ2zLQ

Thanks

Sat, 21 Sep 2019 19:49:55
More Shipper Pro discussions
Shipper Pro
  • Kasia Swiderska
    • Support nomad

    Hello juanitodelrock ,

    I’m sorry about this issue you are facing.

    Just to confirm – you are trying to export local site to the WPMU DEV hosting and not import from local to WPMU DEV Hosting?
    I can see that both sites are connected to the HUB and Shipper is in the same version.
    Have you tried the 3rd suggestion – to deactivate the Shipper on destination site and activate again?

    kind regards,
    Kasia

  • Mukul Chawla
    • Product Manager

    Hey juanitodelrock

    Based on the attached screenshot, it looks like you are trying to import http://digitalsigncl.juan from
    https://digitalsign.wpmudev.host/. That’s exactly the reason why Shipper isn’t able to process the package size. The import method only works with live sites. So, could please go to http://digitalsigncl.juan (your local site) and try to export that to https://digitalsign.wpmudev.host/. The Export method should work fine. And do note that, you need to keep the Shipper’s migration window open while your local site is being exported when migrating a local site.

    Do let us know if you face any issues with Export migration method.

    Regards,
    Mukul Chawla

  • Kasia Swiderska
    • Support nomad

    Hello juanitodelrock ,

    Can you enable debug log on the destination site and then try to run again pre-flight check to see if there are any errors showing?

    To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:

    define('WP_DEBUG', true);

    In order to enable the error logging to a file on the server you need to add yet one more similar line:

    define( 'WP_DEBUG_LOG', true );

    In this case the errors will be saved to a debug.log log file inside the /wp-content/directory.

    Depending on whether you want your errors to be only logged or also displayed on the screen you should also have this line there, immediately after the line mentioned above:

    define( 'WP_DEBUG_DISPLAY', false );

    The wp-config.php is located in your WordPress root directory. It’s the same file where the database configuration settings are. You will have to access it by FTP or SFTP in order to edit it.

    If you open wp-config.php and that define statement is not there, you can add it right before this line:

    /* That's all, stop editing! Happy blogging. */

    if there is debug.log please upload it to the service like Dropbox and give us a link.

    kind regards,
    Kasia