[Shipper] Shipper thinks destination is not a multisite but it is wrong

I’m trying to migrate a subdomain multisite to a staging location, but Shipper is for some reason reporting the destination as not being multisite and not using subdomains – which isn’t true.

  • Adam Czajczyk
    • Support Gorilla

    Hello Tracy

    I hope you’re well today!

    Both these sites are registered in The Hub as mutlisites, indeed. The “target” site has also listed five of our plugins being installed but when I logged in into it now I can’t see WPMU DEV Dashboard and Shipper there – if you made any changes to that “target” site before trying to do migration please make sure that Shipper is installed and activated there again and that WPMU DEV Dashboard is installed, enabled and logged in into your WPMU DEV account (the same account as the “source” site).

    Shipper also checks whether the site is Multisite or not by checking for two configuration constants in wp-config.php file. If it cannot read them or they are missing – it will not confirm that site’s multisite. Since I don’t have direct access to site files, please make sure that there are these two lines present and not commented out in the “wp-config.php” file:

    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', true );

    Additionally, the target site seems to be redirecting to https:// (so to a secure SSL connection) but doesn’t have a valid certificate which might cause connection issues (e.g. browser gives a warning before letting access the site) so either don’t force redirect to https:// and set the site to be served over regular http (non-SSL) or make sure that it’s protected with a valid SSL certificate (it might be e.g. free Let’s Encrypt cert).

    If this all together still doesn’t fix the problem, let me know please.

    Kind regards,

    Adam

  • Adam Czajczyk
    • Support Gorilla

    Hello Tracy

    Thank you for letting me know!

    I started the migration and we’ll see but I was unable to do an export to the site.

    If you are able to start migration as “import” on destination site but not as “export” on source site, that would rather suggest some connection issues there. However, if the migration did start fine, let’s give it a chance and see if it completes – let me know, please, and if it doesn’t, I’ll call out our developers for help.

    Best regards,

    Adam

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.