Unfortunately, the site clone failed. It made it to 95% complete in the "overall progress" before failing. Would it be acceptable to instead send a site backup that you could spin up within a local/dev site yourself?
Thank you for the updates. In this case, we can try this alternative:
To best troubleshoot the issue, please make a snapshot of your site using the Duplicator plugin: https://wordpress.org/plugins/duplicator/. This will allow me to try and duplicate the error so that I can run further tests without interrupting your live site.
Once the snapshot is complete, either upload the snapshot ZIP file and the installer.php file to a file sharing service such as Dropbox (and share the link in your reply) or right click the Duplicator links in your wp-admin and paste in your reply.
Please note: It is important to reduce the size of the package so please exclude some paths like /cache or /uploads and also exclude archives and media files.I will also need the username and password of an account that was created BEFORE creating the duplicator package.I will enable the next reply to be private so only you and I have access to it!
Thank you for the updates. Unfortunately I wasn't able to deploy the provided package, can you please, try the migration process again as I deleted some apps to free some resources in our test server?
Also, if it is possible to setup a staging website where the issue is reproduced in case a new failed migration it would be of help as well.
The login credentials are the same as what I provided before.
I've reproduced the issue there, but please keep in mind that currently I have the WPML plugins deactivated so that you can log in. Once you're logged in, you can reproduce this issue by reactivating the plugins and then attempting to log in via an incognito window. If you become logged out while these plugins are active, you become locked out so you will want to be careful of that.
That is very interesting. Is your test server running on NGINX?
I reached out to WP Engine support and they say that their NGINX config is a default one unless the site owner defines any custom settings (which we have not)
According to this bit of the documentation, since we have language name defined as a parameter we shouldn't need any special configuration applied.
Thank you for the updates. Yes, it is Nginx, as you can confirm from the network tab when using the Chrome Web Developer Tools. Instead of setting a clone of your website, do you see the same issue if you set a new test site from scratch in your server keeping only the WPML plugins enabled? It will confirm if we have a server specific issue or some issue specific to your website only.
I completely wiped the Staging site, set it up as a Multisite, and reactivated the WPML plugins (although I left out the ACF and Gravity Forms ones since those plugins weren't active) and the problem still persists.
I have recreated your user with the same credentials on the site so that you can take a look. I also made it so that you're a Super Admin to give you a bit more freedom in looking around and trying out things. I have confirmed that Network Activating the WPML plugins makes no difference in the login issues.
Same as before, I have left the WPML plugins inactive so that you'll be able to log in.
Thank you for the updates. As said testing the issue in a cloned website won't help us to isolate it. It is prefereable to set an entire new clean test website, set it as a multisite install and install only WPML and its related plugins, this is the only to make sure we have some sort of specific issue to your website or something related to a possible server related issue. Is that possible? Please, let me know and we will move forward to the issue resolution.
> testing the issue in a cloned website won't help us to isolate it
This is effectively a new website. I deleted all the database tables. While I didn't modify wp-config.php (outside of setting up Multisite again) this is a fresh site. Sure, the plugin files and stuff are still there, but none of the original data (WPML or otherwise) still exists.
Since we had no custom NGINX rules configured for the site, that means that it previously having been a clone of Production should not matter.
I can create a whole new Development install on WP Engine if needed, but it is very likely the problem will still exist.
Thank you for the updates. For me it seems to be a specific issue with WPEngine, however as I need to confirm it I am consulting our second level support. I will update you here as soon as I have some more details regarding it.
I'm sorry for the long wait. Marcos is not available at the moment so I'll take care of your ticket.
Could you please try to install a new site on your staging multisite and see if the issue still happens. Since we can't reproduce the issue we suspect it might be a problem with WP Engine and multisites directly.
