Today we released Prime Mover 1.4.7. Change log:
Change log
- Fixed: Unrecognized WPRIME file extension affecting the package download.
- Compatibility: Tested for WordPress 5.9 release.
Compatibility fix: WPRIME extension not recognized
Some servers does not recognize WPRIME file extension. As a result – they cannot be downloaded properly because the file extension isn’t recognized. There is no force download and the download is garbled(streamed as plain text).
This is an annoying issue because it forces user to use other means like SFTP or cPanel which might not be readily available. Actually the issue is more pronounced when using Google Chrome than using Mozilla Firefox.
This issue is reproduced on Apache servers so the fix is the addition of .htaccess on /wp-content/uploads/prime-mover-tmp-downloads/
<IfModule mod_mime.c>
AddType application/x-tar .wprime
</IfModule>It checks if mod mime Apache module is enabled – you don’t need to worrry since this is most likely enabled for all Apache setups including shared hosts.
Once mod mime is set, it will then associate wprime file extension with the application/x-tar mime type.
Compatibility Testing: WordPress 5.9
Prime Mover 1.4.7 is also tested for compatibility with WordPress 5.9. This major version supports full site editing. So during testing – a full site edited site has been exported and restored without any issues with Prime Mover. Note that this won’t affect any existing functionalities that are already supported by WordPress before (including the multisite feature). Is is because – usually WordPress does not want to break backward compatibility.