Codexonics
Forum Replies Created
-
Forum: Plugins
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Prime mover not activatedHi, thank you for using Prime Mover plugin. Based on the above issue – it looks like the required constants might not be added on the correct configuration file. I don’t think Wordfence plugin or Litespeed cache has something to do with this. But I think you should not set your
wp-config.phpfile permission to 777. Instead start with 644 or use your hosting default permissions forwp-config.php.To troubleshoot this issue – can you please try the steps below:
- Check with your hosting company docs or support on how to properly add/edit constants in
wp-config.php. Some host might not allow you to edit file but allow you to add your custom constants elsewhere (e.g. some managed WordPress hosting). In this case – feel free to check your hosting support on whether you have correctly added those constants in the correct place. - Some useful tutorials on how to add WordPress security keys in your configuration file (
wp-config.php)
How to add or change your WordPress security keys?
How to generate security keys for WordPress?
- If you are not using a hosting company but using a local development software – check your software docs on where to correctly add custom constants for your
wp-configfile. For example some local applications likeBedrockdoes not usewp-config.phpbut instead they have their own custom configuration file on adding the constants. - Now if you are sure you have added the constants in the correct place – double check for obvious errors in your
wp-config.php. Maybe all security key constants are not completely added. - Try enabling WordPress debug mode by adding these constants to your wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );- Now If you have enabled WordPress debug mode – try reactivating Prime Mover plugin. Please take a screenshot of the entire error message after activating it and post a link here to view this screenshot.
- Also double check if there are error logs to
/wp-config/debug.logand share it here also. Maybe there are some other helpful errors on this. - In addition if the plugin won’t still activate – please share some info on your system/ site by sharing the Site Health information tools. Login to your WordPress site and go to Tools -> Site Health -> click “Info” tab. And then click “Copy site info to clipboard” and paste it here as a reply (in addition to the screenshot and
debug.logerrors).
These constants are WordPress security keys which are used by WordPress core to secure your passwords and credentials. Prime Mover plugin uses this as well to secure your package information and to generate hashes for the packages (during export and restore). It’s why this is being required on activation. Adding these security constants should be straightforward just like you add any constants to your configuration file.
Please let me know if you still need any technical assistance. Otherwise if the above issues is now fixed in your end – please mark this ticket as resolved. Thank you again!
Forum: Plugins
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Export to AWS.Hello, thanks for the interest in using Prime Mover plugin. 100GB is a very big site – however it is possible you can still use Prime Mover FREE version to move the site to your AWS Server. You can read our big site migration strategies that utilizes some FREE version features.
For example – if your site has around 100GB of media upload files (this is where largest files lurks) + plugins/themes – then you can simply migrate your site database only to your AWS server using Prime Mover FREE. And then manually copy the rest of your files to AWS via
SFTPorSCPwhichever you feel comfortable. This way – the files are copied on a server level which does not depend on HTTP, PHP or database timeouts which could be error prone. As long as your done copying all of the 100GB files to AWS server – then the site should work normally after you have restored site database via Prime Mover also. Please checkout the tutorial above for details.There are other solutions in the migration strategies that involves PRO features – but I could not discuss it here since this is WordPress community forum which prohibits support for paid features. If you are interested or have a question with our PRO solutions – please get in touch with our official contact page.
Thank you again, closing it here so we can continue the discussion on our contact page if you are interested in upgrading to PRO versions. Thanks again!
Hello David,
Thank you for using Prime Mover plugin! Happy to hear about your successful import. Now regarding the critical error – this looks like an issue with WooCommerce plugin. Can you please report this to WooCommerce plugin support forum? This is best in your case because you will be getting a permanent solution instead of having a commented code which could be overwritten if you update the WooCommerce plugin.
I think this issue would have been caused by other plugin / theme conflicts such as these threads:
https://ww.wp.xz.cn/support/topic/recovery-mode-doesnt-work/#post-14800585
We tried reproducing your issue by migrating a complex WooCommerce test site (with 25+ plugins on it) from multisite to single-site but we never encounter this fatal error in our tests. This is using latest Prime Mover 1.9.9 + latest WooCommerce plugin. So this issue must be isolated with your own site – most likely with some incompatible plugins after it has been moved to single-site (from multisite configuration).
Sorry but we could not provide you tech assistance on this one as this is best handled by WooCommerce plugin support team. We will be closing this ticket here and as suggested please open a separate ticket on WooCommerce support forum. Thanks again and have a great day!
I think this entire issue you are referring belongs to another plugin “BackWPup – WordPress Backup & Restore Plugin” which we cannot provide technical support. This is after we examined your posted screenshots – it does not belong to Prime Mover plugin. But it belongs to a different plugin – “BackWPup”, which we cannot provide support on this.
To get support on your issue – please open a ticket directly to their dedicated forum so developers will be aware of your issue:
https://ww.wp.xz.cn/support/plugin/backwpup/
I will ask the moderator to move your ticket to the dedicated forum if possible. Thank you for the update.
Hello, thanks for update. Yes the above steps should work for you. We have tested it here using WampServer in and it works. In addition – we have tested Prime Mover plugin as well with different local server setups like XAMPP/MAMP/Laragon and Local By Flywheel. All of which works.
Just follow the above steps that we provide and please let us know if you still need any technical assistance. Otherwise if all is now good in your end. Please mark this ticket as resolve. Thanks again!
Hello, thanks for using Prime Mover plugin! Sorry to hear you have issues restoring the package. It’s possible that this issue could be caused by some incorrect site configuration or if you are using outdated versions of Prime Mover plugin or the package.
Can you please try the following workaround to see if it works?
- In your source site – check if you are using the latest version of Prime Mover plugin. If not, please upgrade to latest version 1.9.9.
- Delete all old copies or duplicate copies of Prime Mover plugin if it exists.
- Repeat the export process by using the latest version of Prime Mover plugin. This will ensure that you will have updated exports.
- You should see export success message.
- Download the package to your Desktop by following this procedure. This will ensure that your package is not corrupted while being downloaded from the source site.
- In your source site – Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Debugging Tools -> Download log and click “Download log file“. This will download the complete migration log of the export. Create a blank folder in your Desktop and named it as “debugfiles“. Place the log file to this folder – we will need this later on.
- In your source site also – Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. This will download your source site site info details including your Prime Mover settings data. This is your site information log. Place this log file also to this debugfiles folder.
At this stage – you should now have an exported package. We will now restore this to your target site in your localhost. To prepare your localhost environment for best results, please follow the steps:
- [Recommended] – To prevent conflicts, try using another localhost server with a different site name / local URL name. If you are OK with this – please try using Local by Flywheel which we tested to work.
- Please reset/create new localhost WordPress fresh install (using latest WordPress version 6.6.1). Ideally matching your source site PHP version as possible to prevent conflicts. For example – if your source site is PHP 8.1 – make sure your target site is PHP 8.1 as well.
- Clear the uploads directory, plugins directory and unused themes just like it was in fresh install. This will avoid these things to interfere with the restore.
- Make sure your fresh WordPress install works well both front end and back end. The localhost site should load properly without any errors.
- Now install and activate latest version of Prime Mover plugin (version 1.9.9 as of this time).
- Once activated – Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. Place this log file also to this debugfiles folder.
- Finally restore your package by copying it to export directory and restore it via package manager.
- After restore is completed – refresh the permalinks and your site should now be migrated.
- In your target site – Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Debugging Tools -> Download log and click “Download log file“. This will download the complete migration log of the import. Place this log file also to this debugfiles folder.
The above steps should allow you to migrate your site to your local specially if you use another local host server (e.g. like Local by Flywheel). Now if you are still having the same issue and the above steps still does not work – please do the following:
- Copy also your
WPRIMEpackage to debugfiles folder. - Zipped your debugfiles folder.
- Upload and share it via Google Drive or Dropbox. Please do not share links here or in public as these files are meant to be private only.
- Please send us the link to download this in our site contact form.
Thank you again and if our technical assistance helps in resolving this issue , please marked this ticket as resolved. Cheers.
Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Thank YouYou’re welcome! We are glad to know that it worked perfectly. Thanks again for rating us 5 stars. Cheers!
Hello David,
Thank you for trying out Prime Mover! Yes we have received your ticket in our internal system and already replied to you. I see that you have a valid license. I’m closing this ticket here so we can continue with our official support channel (via our website). Supporting PRO version of a plugin is not allowed in this forum. Thanks again! Cheers.
Hello, thanks for the feedback! Regarding your additional questions:
- Is there a way to exclude/filter certain plugin/theme folders from the package and include the rest?
Answer: Excluding some activated plugins from the package is a PRO feature. In addition – excluding media files from the uploads directories from the package is also PRO feature. These are the related documentations:
How to Exclude Plugins in Prime Mover Pro?
How to exclude upload media files in Prime Mover Pro?
- Also is there a way to only back-up/restore the DB and uploads of the target multisite including the main site (just in case something goes wrong during migrating a single site)?
Answer: Prime Mover also supports database only backup and database + media files only backup. This is available in FREE version. However to backup the main site – you need to upgrade to PRO version. But if your multisite is sensitive and complex – Prime Mover cannot back up the entire network at once. This can only backup individual subsites or main site). You must rely on additional backups (such as full database dumps and manual backups of your files) so you have redundant copies of your site in case you want to revert. And test this first with a development server to be sure (using the same PHP version, WordPress version, server environment settings as your live site)
- Will …/uploads/prime-mover-export-files/2, …/uploads/prime-mover-export-files/2 etc be excluded by default during -if any- full back-up? After all they hold every sub-site’s package and can unnecessarily bloat the full back-up package.
Answer: Yes of course they are excluded by default. You can also exclude other large directories if you need to. (this is supported in PRO version, see the link above to exclude media file directories).
=========
If you have additional questions with the above PRO features – please consult our official documentation or contact us via our site. As discussing PRO features is not allowed in this forum. Please mark this ticket as resolved if you no longer have any questions or assistance. Thanks a lot!
Hi, thank you for using the Prime Mover plugin! Below are simple rules on how plugins/themes are handled during migration. Take note these only apply when you migrate using complete export (that includes plugins /themes on it)
- Prime Mover will copy the plugin from the source package to the target site. E.g. If the source site has Plugin A and the target site has Plugin A as well. Then Prime Mover will delete Plugin A at target site and replace it with Plugin A from the source site package.
- Prime Mover will copy theme from the source package to target site. E.g. If source site has Theme Z and target site has Theme Z as well. Then Prime Mover will delete Theme Z in target site first and then replace it with Theme Z from source site package.
- The other plugins/themes in the plugins/themes directory that are not part of the migration package are untouched (not deleted, overwritten or edited in any way). For example if package only has Plugin A, B and C. And target site has existing Plugin A, B, C, D and E. Prime Mover will not delete or overwrite plugin D and E.
The above rules are applied regardless if you are migrating from single-site to single site, single-site to multisite, multisite to multisite, multisite to single-site. The above rules ensure that the package are migrated correctly to target site. Since plugins / themes are included in the package (if it’s complete package you are restoring) – they are dependencies of the source site to work correctly.
So to answer your questions:
- What happens during migration? Are theme X, theme Z, plugin A, plugin B overwritten in multisite?
Answer: What happens during migration (following the above rules) – is that if plugins exists in target multisite, it will be replaced or overwritten with the plugins /themes from the package.
- Or will Prime Mover skip preexisting plugins/themes leaving them untouched?
Answer: Target site plugins/themes are untouched only if you are migrating a package that does not include plugins/themes on it (e.g. DB only package or DB + Media package type). In this case – Prime Mover will do a compatibility check before import and warn if you want to proceed migrating just in case the plugin/theme versions are different from the source and target site. This is important if your source site is not tested to work with the target site plugin /theme versions.
But if you are migrating a complete exported package – Prime Mover will eventually replace plugins / themes in the destination site.
- Would we need to manually transfer each new theme/plugin (a delicate as well as tedious task), just export the database from the single site and then go through the whole process again every time we need to import a new single site as sub-site?
Answer: It depends on your case and convenience. For example – if all of your plugin/theme versions are the same for both source single site and target multisite. Then it would be best to just migrate the database/media files if all needed plugins /themes exists in target multisite and running the same versions. Target multisite plugins/themes are untouched in this case.
But if versions are different or if some plugins/themes in single site are not found in the multisite – then migrating using complete package is nice since it will surely copy all plugins /themes needed from the source site to target site. This way there is no tedious work of copying each plugins/themes manually.
If you have complex sites – you must test them first entirely in a local or development server before rolling out the migrating work to production or live site. By testing locally / developing, you know exactly if the migration will be compatible with your target multisite.
Thank you again for your question and if you have further questions – please check out this related question from another user in our FAQ.
Thank you for using Prime Mover! We are happy to know that you find the plugin easy to use and to rate it 5 stars! Cheers 🙂
Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Superb toolThank you for using Prime Mover plugin! We are happy to hear that find the plugin reliable and amazing. Thanks again for rating the plugin 5-stars. Cheers!
Forum: Reviews
In reply to: [Prime Mover - Migrate WordPress Website & Backups] Works wellThank you for using Prime Mover plugin and for rating us 5-stars. We are happy to hear that you found the plugin useful in your multisite environment. Cheers 🙂
Thank you for using Prime Mover plugin and for rating the plugin 5-stars. Cheers! 🙂
Thank you for the feedback and we are glad to assist!
- Check with your hosting company docs or support on how to properly add/edit constants in