Prime Mover 1.3.9 is now available in both FREE downloads and in Freemius PRO repository (for paid versions). This is part of the regular 2-weeks maintenance release focusing on some specific bugs and migration related changes.

Change log

= 1.3.9 =

  • Fixed: Issues with package download due to SSL mixed content issues.
  • Fixed: Incorrect ABSPATH computation in export.
  • Fixed: Incompatibility issues with sites using custom wp-content directory.
  • Fixed: Incompatibility issues with sites using custom uploads directory.
  • Fixed: Incompatibility issues with WordPress installed on its own different directory.

Release highlight #1 Custom wp-content better compatibility

Some sites are customizing wp-content directory. This means that this directory is either:

  • Not using wp-content as the folder name. Example it is named as sites-content instead.
  • Not placed within standard path as it is used to be.
  • UPLOADS directory is also customized and it is not using the usual /wp-content/uploads/ but it is pointed somewhere else.

Prime Mover 1.3.9 has better compatibility regarding this custom adjustments.

Release highlight #2 Fixed bug with mixed content issues

In previous releases, there are customer reports of being unable to download the WPRIME package directly in package manager. We debug this and this is due to mixed content issues. For example, if the site URL in dB is still using HTTP protocol however the entire site is using SSL. Chrome blocks the download.

This is now fixed with version 1.3.9.

Release highlight #3 Fixed incorrect ABSPATH declaration

In previous releases, Prime Mover uses get_home_path() to easily compute ABSPATH. However this is turn out to be not entirely reliable when used in a migration scenario. For example, if WordPress is installed in it’s own directory, get_home_path() is different than the original ABSPATH. This can be lead to some import errors specially on the search and replace aspect.

Note that this issue only affects if you have WordPress installed in a different directory that results to different site_url and home_url.

What’s next?

In the next release Prime Mover 1.4.0 – we will focus on removing the write permission dependency on the WordPress root directory. If your host does not allow the WordPress root directory to be writable (e.g. some Manage WordPress hosting do this for security reasons) – then Prime Mover cannot be installed/activated. We are planning to fix this limitation hopefully this is will done in the next release.

This change allows sites that are affected with this issue to finally migrate or backup their sites using Prime Mover.

Found issues? Or suggestions?

We love to hear from you. Please contact us here and report any suggestions or issues you’ve found with the plugin 🙂

Emerson Maningo Announcements