Hi, 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.php file permission to 777. Instead start with 644 or use your hosting default permissions for wp-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-config file. For example some local applications like Bedrock does not use wp-config.php but 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.log and 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.log errors).
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!
