Hey beriber,
I had a similar issue a few days ago using the plugin version 0.17.2 and received an email including the error details, did you get an email?
If not I was able to debug and confirm this by logging php errors. I did this by placing the following code into wp-config.php
// log php errors
@ini_set(‘log_errors’,’On’); // enable or disable php error logging (use ‘On’ or ‘Off’)
@ini_set(‘display_errors’,’Off’); // enable or disable public display of errors (use ‘On’ or ‘Off’)
@ini_set(‘error_log’,’/path/to/logs/php-errors.log’); // path to server-writable log file
^ The only thing you need to change in the above is the final line pointing to where the path will be for your php-errors.log file, this needs to be a server writable directroy.
This should give you a log of any php errors you experience on your site. Go to this log file and look for a line similar to the below:
PHP Fatal error: Access level to WebPConvert\Convert\Converters\BaseTraits\WarningLoggerTrait::logLn() must be public (as in class WebPConvert\Convert\Converters\BaseTraits\OptionsTrait) in /…/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Convert/Converters/AbstractConverter.php on line 17
If you have this exact message (where “WarningLoggerTrait::logLn() must be public” in “AbstractConverter.php on line 17”) then you are likely experiencing the same problem.
If it’s different then you’ll need to do more research into how to fix it but I fixed my issue by changing “protected” to “public” in the following files on the following lines:
/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Convert/Converters/BaseTraits/WarningLoggerTrait.php on line 17
/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Convert/Converters/BaseTraits/LoggerTrait.php on line 39
/wp-content/plugins/webp-express/vendor/rosell-dk/webp-convert/src/Convert/Converters/BaseTraits/LoggerTrait.php on line 65
I changed three lines across two files because I kept getting more errors in the log file until it eventually started working again.
HOWEVER I don’t know enough to say whether this is the right way to fix this problem or whether this creates a security hole so if anyone with more knowledge can confirm that would be great.
Hopefully this will fix your problem (or at least point you in the right direction).
Don’t forget to remove the code from wp-config.php once you are done testing to stop logging php errors.