Codexonics
Forum Replies Created
-
Hi Yavuzyayla, that’s great to hear 🙂 Thanks for the update.
Hello Yavuzyayla,
Thanks for the log! We’ve checked the log and you are getting out of memory runtime errors. This is usually caused by a large imported user data that exceeds your current WP memory limit:
Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes)Can you please raise your memory limit in the target site
wp-config.php? Let’s try increasing this to somewhere 256M to 512M to see if your server can handle it.define("WP_MEMORY_LIMIT", "256M"); define("WP_MAX_MEMORY_LIMIT", "512M");Once the memory limit is raised – please try the restore again to see if it outputs the same error. If you still get memory errors – try raising the memory limit to somewhere 1GB:
define("WP_MEMORY_LIMIT", "512M"); define("WP_MAX_MEMORY_LIMIT", "1024M");Once the site is restored – you can re-adjust the memory limit to something sensible during it’s operation.
If the issue does not fix with any memory limit adjustments – please share the link to download
WPRIMEpackage (e.g. in Gdrive or DropBox) via our contact form – we will diagnose this package and see why it requires this much memory requirements. Thanks again and let me know how it goes.Cheers,
Emerson- This reply was modified 4 years, 1 month ago by Codexonics.
Hi Parihar,
Thanks for the question. No, it does not include inactivated plugins in any package. This is to save bandwidth during file transfer and reduce the size of the package. This is listed in the Prime Mover FAQ.To get to know more about Prime Mover – please check out also our complete set of documentation. Cheers and have a great day!
Hi Parihar,
Thank you for reviewing and rating us 5 stars! Happy to know that you have found the free version useful and sufficient. You’re very welcome and good luck in your projects 🙂 Cheers.Hello Parihar,
Thank you for using Prime Mover! For your question – we have a detailed answer on this one in our FAQ. Cheers 🙂Hi Ludovic, thank you for using Prime Mover! Automating backups is not currently supported. Currently it only supports on-demand backups. This feature has been on our road map and this will be available in the future versions of Prime Mover. There is no definite timeline yet. Automating backups is a complex feature as we want to make this as hosting friendly as possible and easy to use as well.
Right now – you can just use do the backups on-demand (manually). Cheers.
Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] FantasticThank you for using Prime Mover and for rating us 5 stars! Cheers 🙂
Hi Sparkis,
You’re welcome 🙂 Prime Mover 1.5.0 is now released. For your update. Thanks.Good news, we have reproduced and fixed this one 🙂 The fix is now included in the latest Prime Mover 1.5.0-beta2 version. A stable version will be released in ww.wp.xz.cn within this week.
If you like to use the fixed version – make sure to re-create the package using Prime Mover 1.5.0-beta2 and restore it also with Prime Mover 1.5.0-beta2.
Thanks again and for your update. Closing here 🙂
Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Best migrator by farThank you for sharing your experience in using Prime Mover plugin and for giving us 5 stars 🙂 Yes donate button seems like a good idea. We will check on it. Thanks again. Cheers!
Hi Sparkis, thank you for creating the ticket. We would like to reproduce and fix this one. For now, the workaround is manual search and replace after restore 🙂 We will mark this one as resolves once a permanent fix is added on the plugin. For your update. Cheers.
Hi Hans,
You’re welcome! Thanks for taking the time to review and rating us 5 stars! Cheers 🙂Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Worked perfectlyHello Thoughton, thanks for giving the plugin a 5-star review. Happy to know you find it easy to use and it worked perfectly in your end 🙂 Cheers.
Forum: Plugins
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Failed at first hurdleHi thoughton,
Thanks for using Prime Mover and sorry to hear you have issues. First, looking at the errors – it does not look to be migration related. I think has something to do with user authorization, cache related, or server permissions. But there is no specific details in the error that relates to a Prime Mover process.
Can you please do the following quick troubleshooting first so we can isolate the issues and get more details:- Clear your browser cache.
- Login to your network admin.
- Make sure you are using the latest version of Prime Mover plugin (currently version 1.4.9)
- If you are exporting a subsite – check the subsite front end – does it display correctly? If there are errors or white screen – you need to resolve this before exporting the site.
- Please check the subsite admin dashboard – can you access it? Make sure it does not have white screen or fatal errors.
- Confirm if the subsite to be exported is in multisite – go to subsite admin -> Tools -> Sitehealth -> click “Info” tab -> Scroll below and look for “WordPress” section -> Click on it and look for “Is this a multisite?” – it should be “Yes”.
- Finally follow these steps to reproduce the issue and submit migration/debug logs to our support. Follow these steps under Prime Mover Free version.
Basically the steps will require you to enable WordPress debug (if not enabled) and then reproduce the error.
- If the error is still reproducible – please get the migration logs/debug.log generated and check the browser for console errors also (if there is).
- You can send to us all the logs via our contact page.
Thanks again! Cheers.
As far as we know it by looking at the WC code – it’s only dependent on
_customer_user. This is what they use to query orders belonging to that specific user. We cannot reproduce this scenario in our end if the customer order association is correct but it won’t appear in order history.It would be hard to debug this without getting real data. If you like us to debug this one, you can install this debug plugin in the affected site or a clone of a site (in your test site). Enable
WP_DEBUGandWP_DEBUG_LOGto true. Logged-in as affected customer (or you can use the user switching plugin).And then go to My Account -> Orders and view the order history. The debug plugin automatically generates
debug.logoutput to wp-content directory. Please send it to us here. Once generated – please deactivate the plugin.We will take a look at the data and analyze why the order history won’t show the orders even if the dB side is fine.