Forum Replies Created

Viewing 15 replies - 1 through 15 (of 386 total)
  • Plugin Author Codexonics

    (@codexonics)

    Thank you for using the Prime Mover plugin! I’m glad to hear that you found this to be the only solution that works in a multisite environment. Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Thanks, Marioline, for sharing your experience and rating the plugin five stars! Yes, we are happy that the plugin’s usability aspects are working as intended. This is designed to be used as easily as possible. Cheers!

    Plugin Author Codexonics

    (@codexonics)

    OK, as an update, we have reproduced this when creating a site via the wp-signup.php page (not on Network admin -> Sites). I’m sorry, but this is not an issue with your server, plugins/themes. But this is currently a bug in Prime Mover: it can’t properly initialize the WP filesystem when used in the signup page.

    We tested the hot fix as a workaround, and it works in this case so you can use it temporarily. We will add a permanent fix to the next release. Thank you again for reporting this issue!

    Plugin Author Codexonics

    (@codexonics)

    Yeah, this is weird. We did some updated tests as follows (based on your latest post).

    1.) In a multisite network activate the following plugins: Jetpack, Litespeed Cache, and Multisite Enhancements

    2.) In wp-config, add the following constant:

    define( 'DISALLOW_FILE_EDIT', true);

    3.) In the network, go to Sites -> Add site -> then create a test subsite.

    Expected: The issue is reproduced.
    Actual result: The site is successfully created, with both front-end and back-end accessible.

    My test environment is PHP 8.2.29 in Linux (PHP-fpm) + WordPress 6.9. Please provide more information about your site from the site health tools (e.g., a complete list of your plugins/themes/PHP info/server info). That would be great, so we can update our test site to make this reproducible.

    If you have managed to activate the Prime Mover plugin using the hotfix version, you can also send us your site information, which is more complete than the one in Site Health Tools. Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. This will download details of your site, including your Prime Mover settings. This is your site information log. Zip it and then share the download link to our tech team in this contact form.

    This is likely an incompatibility issue with your server (perhaps a permission misconfiguration) or with one or more plugins. Still, until you can share all the details, we won’t have a better picture of this issue.

    You can also create a test multisite (ideally a fresh one without any plugins and using default themes) on your server to play with and see if the issue is still reproducible with that test site. If it is reproducible, it might be hosting-related, so we need to know where your site is hosted so our tech team can run some tests.

    Thanks again!

    Plugin Author Codexonics

    (@codexonics)

    Hello Rolf,

    Thank you for using the Prime Mover plugin! I’m sorry to hear you’re having issues with the plugin on your site. We’ve checked the error stack, and your site does not consistently set the $wp_filesystem global object.

    We’ve tried to reproduce this on our test servers (both local and remote, across different hosting companies, including popular ones), but couldn’t see the problem.

    However, we have found a simple workaround: we check whether $wp_filesystem is set before using it. If not set, we initialize the WP Filesystem object so it’s usable. We hope this works with your setup; otherwise, there is no quick workaround for now except to deactivate the plugin while we work on a different solution.

    You can download the hotfix here: https://codexonics.com/prime-mover/hotfix/prime-mover-free.2.1.1-hotfix.zip

    Please try it on your site and see if it works. You need to delete the current version and replace it with the hotfix version. We will add a permanent fix in the next release, 2.1.2, but for now, please use the hotfix version. Thanks, and please mark the ticket as resolved if it works for you

    Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Thank you for sharing your wonderful experience with our plugin and support. Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Hello Romfill,

    Thanks a lot for using the Prime Mover plugin and sharing your experience! We take note of your comments, and they’re very valuable. We believe we’ve already added this note, but we will review it again for usability reasons.

    Thanks again for rating the plugin five stars! Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Hello,

       Thank you for using the Prime Mover plugin! Sorry to hear that Inactive plugins are not excluded from the export. We do this to save space in the package, speed up the export/restore, and enhance target site security (as per WordPress core recommendations).

        WordPress core best practice also recommends removing inactive plugins for security reasons. You can see these recommendations in the Site Health status page. Therefore, these are the reasons we follow these security recommendations in our migration procedures: if the plugin is not active, it should not be included in the package.

        You have three options regarding handling inactive plugins on your site (when doing a migration or export):

    • If you want to keep these plugins on your site, as they serve a purpose, make sure you activate them before creating any export. Prime Mover automatically includes this in the export package unless it is excluded in the export.
    • If these plugins are not used on your site, you should consider removing them (as WordPress security recommends).
    • If you plan to use these inactive plugins sooner in your target site (after migration), then it’s best to reinstall them fresh from their sources (e.g., WordPress plugins repository) or directly from the vendors. This will ensure you are always using the latest version.

    In future versions of Prime Mover, we might review this one and add an option for users to include inactive plugins (as an export setting). However, for now, you can only choose from the above three options.

    Plugin Author Codexonics

    (@codexonics)

    Hi Virginie,

    Thank you again for providing us with the package and the site information log. We have restored the package using the exact environment as your server (using the site information log):

    • PHP version: 8.2
    • WordPress version: 6.8.3
    • Language: French

    We also activate the same network-activated plugins as in your multisite to make the test environment as close as possible to your multisite.  However, the package was still restored successfully. Please check our tech support reply to your email for the test result screenshots so that you will be guided on the next steps.

    We are closing the ticket here since we already have your ticket filed in our internal system. We will continue our discussion there if you still need technical support. Thank you again!

    Plugin Author Codexonics

    (@codexonics)

    Thank you so much for using the plugin and for rating us five stars. We are glad to know that you find it efficient and straightforward to use. Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Hello Virginie,
    Thank you for using the Prime Mover plugin! We are sorry to hear that you are having issues restoring your site using the H5P plugin. We tried to reproduce your reported issue by doing the steps as follows:

    • Create a fresh WordPress install with H5P implementation (e.g., multiple-choice content type using the H5P plugin).
    • Implement the H5P content type using a shortcode and see the multiple-choice quiz work on the front end in a single site.
    • Create a multisite export of this subsite to blog ID 7.
    • Migrate the package to the multisite environment in the subsite blog ID: 7

    Actual test result: The H5P plugin’s multiple-choice content type works as expected (in the subsite). We are not able to reproduce the problem.

    This means we are dealing with an edge-case scenario in the H5P implementation. Please follow the steps below to allow us to diagnose your package:

    • Upload your WPRIME package to Google Drive that you have migrated to blog ID 7 (which is having the issue).
    • In the target multisite where you want to restore the package, log in as network administrator. Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. Upload this to Google Drive as well to share with us.
    • Please send us the link to download the package and the site information log by contacting us here. Don’t share the links to Google Drive in this forum – only share them with us via the form link above.

    We will try to reproduce the issue with your package, and if it occurs on our end as well, we will investigate why it got stuck in that process and how to fix it.

    Thanks again, and we will be happy to assist further if you send us the package and your site information log by following the steps above.

    Cheers.

    • This reply was modified 5 months ago by Codexonics. Reason: minor typo
    Plugin Author Codexonics

    (@codexonics)

    Hello Ken,

    Thank you for using the Prime Mover plugin! Sorry to hear that you’re having issues restoring the package. If you don’t see the package, it may be that you have uploaded it to the wrong path or that it is corrupted (during your download from the source site).

    To find out the problem, we would like to clarify the following:

    1.) Please share the name of your WPRIME package.
    2.) Is your target site for migration a multisite?
    3.) Does this path exist in your target site server?

    /home/my_cpanel_username/public_html/wp-content/uploads/prime-mover-export-files/2/

    You should only upload the package to the specific Prime Mover export directory at the provided path (not in the WordPress root).

    Cheers.

    • This reply was modified 5 months, 3 weeks ago by Codexonics. Reason: hidepath
    Plugin Author Codexonics

    (@codexonics)

    Hello,

    Thank you for using the Prime Mover plugin and sharing your wonderful migration experience!

    Cheers!

    Plugin Author Codexonics

    (@codexonics)

    Thank you for using the Prime Mover plugin! We are pleased to hear that the plugin works in your case and that the migration went smoothly.

    Thank you again for rating the plugin five stars! Cheers.

    Plugin Author Codexonics

    (@codexonics)

    Hello Andy,

    Thank you for using the Prime Mover plugin! Sorry to hear you have issues with your “guid” field. However, according to guidelines on migrating WordPress, this “guid” field should never be changed.

    This is why the “guid” field stays the same across different WordPress migrations, as WordPress core and its feed readers use it to identify the source site when processing these feeds uniquely.

    The site should continue to work as usual if these are unchanged. If you need to use the updated URLs after the migration, you should use the new site URL or its permalinks, and not the guid. The “guid”, as per WordPress guidelines, has its special, unique purpose.

    If you need to change these “guid” fields, you need to do a manual search and replace after migration using plugins like Better Search and Replace. And then you need to check the “Replace GUIDs” checkbox and check the affected tables (e.g., the posts table). This can be a risky procedure if done wrong, so make sure you back up your site database before doing so.

    Or if you are comfortable with running SQL queries, you can do it directly inside the database by following this tutorial.

    Thanks again, and have a great day!

Viewing 15 replies - 1 through 15 (of 386 total)