Support » Plugin: PHP Compatibility Checker » Stuck? How to stop?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jason Stallings

    (@octalmage)

    I replied to your later topic, but I’ll go ahead and respond here too! If the progress doesn’t move in 2 minutes it most likely means that the scan has stopped because the site’s cron didn’t trigger. The plugin WP Crontrol is great for debugging cron issues. You can also enable WP_DEBUG and check the log to see if the scan is still running.

    I hope this helps! Please let us know if you need anything else.

    Hi @osseonews,

    I actually had to do this today because mine got stuck while scanning the Divi theme. You can cancel the current scan by following these steps:

    1. Run this query to delete the records that PHP Compatibility Checker creates for the current scan:

    DELETE FROM wp_posts WHERE post_type = 'wpephpcompat_jobs';

    2. Run these queries to delete the options that PHP Compatibility Checker sets for the current scan:

    DELETE FROM wp_options WHERE option_name = 'wpephpcompat.scan_results';

    DELETE FROM wp_options WHERE option_name = 'wpephpcompat.lock';

    DELETE FROM wp_options WHERE option_name = 'wpephpcompat.status';

    DELETE FROM wp_options WHERE option_name = 'wpephpcompat.numdirs';

    3. Install Advanced Cron Manager, enabled it, and remove the cron job titled wpephpcompat_start_test_cron.

    • This reply was modified 3 years, 1 month ago by  Jimmy K.. Reason: Fixed code formatting
    • This reply was modified 3 years, 1 month ago by  Jimmy K..
    Jonathan

    (@bionicsquid)

    Are these steps necessary if I’ve deactivated the plugin to get it to stop? Mine too keeps hanging on Divi. Is there an alternative to these queries and WP Crontrol not only to stop the scan but to deal with the hanging issue?

    Plugin Author Jason Stallings

    (@octalmage)

    If a scan is hung then it’s already stopped, re-running the scan will restart it and clear all of the above options.

    If the scan is hung then that means the cron didn’t fire. There’s a section in the FAQ for how to deal with this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Stuck? How to stop?’ is closed to new replies.