I’ll dig into that with some further testing to see what’s going on. If anything comes up, I’ll reach out via the contact form you noted since it’s not directly related to the OP’s issue.
However… there is something I have noticed that IS directly related to the OP’s issue. Or, more accurately, your recommended solution in the answer.
You cannot define the RESMUSHIT_LOGS_PATH
constant in the wp-config.php file without generating a PHP warning. This constant is defined in resmushit.settings.php, so if you apply a definition in wp-config.php, you’ll get a warning notice when it the plugin tries to define it later.
If you want these to be user definable (and you should), then you should either add a filter hook somewhere to allow it to be changed via a filter function (which would be the best alternative), OR, you should write in a check to see if the constant was defined already, such as:
( ! defined( 'RESMUSHIT_LOGS_PATH') ) ? define( 'RESMUSHIT_LOGS_PATH', 'resmushit.log' ) : '';
As I noted, adding some filter hooks to modify certain settings/options would be helpful, but if you’re going to recommend that someone change a PHP constant, at least make it possible to do that without generating error notices.