Codexonics
Forum Replies Created
-
Forum: Plugins
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Taking foreverHello Jenn,
It depends on your site size. But if this is going on for 4 hours, most likely is it not normal. I see that you have subscribed to Free Trials so have access to email support.What I would suggest is to refresh the page and use version 1.0.3-beta for both source and target site (which I’ve sent to you via Free Trial support email). Please check your inbox.
If you still need help. Let’s use the premium support channel so we can discuss this issue further, I’m closing this ticket here. Thanks !Yes, if you can access Prime Mover – Accounts in Network admin you should be able to edit your existing email and verify it.
The go to Account tab, under Account details, you will see the old email and then change it.
The plugin is new and have not been tested yet on AWS. But it has been tested with several hosts already. But as long as the server is PHP 5.6 + and passes all system requirements, it will work.
Once Prime Mover is activated, it will automatically do a series of system requirement checks to see if the server can handle the migration. If you don’t see any error after activation, it assumes it passes the requirements and you can migrate.
Otherwise it will list a number of dependencies missing from your server which needs to be settled you can use the plugin.
The official site documentation, shows several examples of migration including migrating from single-site to multisite. It also includes some troubleshooting guide.
When using this in multisite, it can only be installed network-wide. So you need to be a network-administrator to install this plugin.
Let me know if you still have some questions. Thanks for your interest in using the plugin 🙂
Hi Steve, thanks for the warning. I’m sorry its a mistake to ask for user site access. But the user here didn’t provide access to the site though (only log details) and I never have the access the site.
Rest assured that I will never repeat asking this information. I will review our procedures and add your input as well.
Again, thanks for the note. This makes us more vigilant in doing things the right way in WordPress support.
@lukefiretoss / @je2walsh I pushed version 1.0.2 today based on the fixes added on related to this issue. It adds more flexibility in MySQL/PDO connections especially in customized servers.
I can confirm this is specific error is now gone using version 1.0.2 on a test server I’ve used. Please confirm that this is also fixed in your end, then we can mark this ticket as resolved.
Make sure you are using version 1.0.2 Thanks!
Thank you @je2walsh . I got your log file and is now analyzing it. Yes it’s true that if MySQL localhost server is not set up to listen for external connections, this error will be returned.
I’ll hopefully create a patch later for you to test in your server. I’ll update.
Hi Luke,
I read about this error and I found these possible solutions having this exact error:If you are using using Maria DB:
https://mariadb.com/kb/en/troubleshooting-connection-issues/Looks like this is a possible issue with MySQL configuration in your own server.
If you can also provide details on your server configuration/ host or the migration log, it would be helpful. Thanks.
Thanks @lukefiretoss , If you can provide debug details and access to your test site it would be great (follow the link above to add this info). I need more details on why this can be happening.
@je2walsh I tested this with localhost as database hostname in my test server and it works. The plugin should be able to handle any database hostname even
localhost. The issue found in my local debug is related to some port number thing in database connection credentials. It’s why there is a connection issue error. I made some adjustments in 1.0.1 to make this more flexible.Let me know if you still need more help. Thanks.
@lukefiretoss / @je2walsh I manage to reproduce a specific issue on my end that will prevent it from exporting a database. I fixed this in version 1.0.1. Can you try the following:
- Update to version Prime Mover 1.0.1
- Clear your browser cache
- Re-test the export
- The expected is that the database should be exported
In case, you still see the problem. The issue might be isolated in your own server. In this case, I need to see some debugging data or possibly access your site for further troubleshooting. Please refer this guide on submitting debug data to our support.
If version 1.0.1 fixed the issue, that’s great. Please let me know if it works and we can mark this ticket as resolved. Thank you again.
- This reply was modified 6 years, 11 months ago by Codexonics. Reason: Fixed typo
@je2walsh / @lukefiretoss Thanks for reporting this issue. I’m now reproducing this specific problem. I will let you know if I need more information. I’ll add the fix as soon as the issue is reproduced on my end.