Did you guys find out a solution for this? Same thing is happening for me today check PHP 7.1. Theme (HealthMedical WPL from WPLook) and 7 plugins, most of which are pretty common (i.e. TinyMCE, Duplicator, Classic Editor)
Any help is greatly appreciated.
MD
Hi,
I did not remember correctly what I did, I hope that will help more CPU and RAM :). I use this plugin just as precaution.
Chears.
Hey MD. We’re actively working on a fix for these types of failures along with adding in 7.3. I don’t have a precise ETA, but it’s weeks away and not months.
In the meantime, and as always, our recommendation is to not run this ~linting plugin inside a production environment, but rather run locally or in another non-production environment (dev / staging copy of your site) prior to pushing to production.
This should help you avoid any server related issues from killed processes (or non-killed ones) and of course, it’s better to tax a non-production environment with the workload of scanning code vs. using your production server for that. Additionally PHP COMP is designed to be a workflow tool to vet PHP compatibility before pushing to production, so it’s best used before you push live.
In any case, I hope that was helpful. We’ll be updating documentation and the support forums when the new version is released with the fixes mentioned above and the addition of 7.3.
I’m sorry to hear that you’re still experiencing the errors, but we’re working now on a fix for these cases. Thanks for letting us know!
Thanks josmatic and davidvee. No trouble at all. I did run it locally on my staging server and it seemed to complete quicker but with the same results. I do test everything in staging before applying to live but, like josmatci, use the plugin as a precaution even in my staging environment. I’ll definitely keep an eye out for the plugin update. Thanks for the quick response guys. Keep up the great work! MD
