Common Issues

The scan says “A scan is already running”#

Symptom: Clicking Run scan does nothing, or the button is disabled, and no progress appears.

Cause: A scan is in progress in another tab or in the background, or an earlier scan died without finishing.

Fix:

1. Wait a moment and reload the page. If a scan is really running, the page shows its progress.
2. If nothing changes, click Cancel if the button is visible.
3. A scan with no progress for 15 minutes is treated as stale. After that, Run scan replaces it (it is recorded as Stopped in History) and starts fresh.

“Editor simulation for ‘post’ failed, so observed data is used instead”#

Symptom: The summary page lists this under files could not be scanned, and the Meta boxes tab says the list for that post type comes from real editor visits.

Cause: A plugin’s editor callback produced a fatal error, called exit, or redirected while the scanner simulated the editor. The message names the error, file and line when it was a fatal error.

Fix:

1. Read the error to find the plugin responsible. That plugin is a strong candidate for problems in the real editor too.
2. Open that post type’s editor once as an administrator, so the scanner records the real meta boxes and editor assets, then scan again.
3. Update or replace the plugin, or run the scan on a staging copy without it.

A background scan never finishes#

Symptom: You closed the page during a scan; hours later History still shows it as Running.

Cause: WP-Cron is not firing (for example DISABLE_WP_CRON is set with no system cron, or the site gets no traffic), so the queued chunk never runs.

Fix:

1. Open Tools → Editor Readiness. If the scan is not stale, the page resumes driving it over AJAX and it finishes while you watch.
2. Push the background job along by hand: wp cron event run ers_process_scan_chunk, or wp action-scheduler run if Action Scheduler is installed.
3. For future scans, keep the page open or set up a real system cron that calls wp-cron.php.

The Meta boxes tab says “No editor visit is recorded yet”#

Symptom: A post type shows no meta boxes and the note asks you to open the editor.

Cause: The scan ran without the page open (or from WP-CLI), so the editor could not be simulated, and no administrator has opened that post type’s editor since the plugin was installed.

Fix:

1. Open Posts → Add New (or the equivalent for that post type) as an administrator and let the editor load fully.
2. Run a new scan from Tools → Editor Readiness with the page open.

Findings show “Lowered: found as an editor script by a static guess”#

Symptom: Confidence is Medium instead of High, and a plugin you expected to be Likely broken is Check.

Cause: No runtime editor data was available when the file was classified, so the scanner guessed it was an editor script from block.json, PHP enqueue references or .asset.php siblings.

Fix: Run a scan from the admin with the page open so the runtime check records which files really load in the editor, then review the plugin again.

“Some rules in rules.json are invalid and were skipped”#

Symptom: A warning on the summary page lists one or more rule IDs.

Cause: The rules file inside the plugin is damaged, usually by a partial upload or an edit.

Fix: Re-install the plugin from a fresh zip from your technoleet.dev account. Do not edit rules/rules.json; rule updates ship with plugin updates.

Many files are reported as skipped#

Symptom: The scan summary says Skipped: N (over 2 MB, or large minified files that are not editor scripts).

Cause: This is normal. Large minified bundles that do not load in the editor are not worth reading, and files over 2 MB are never read.

Fix: None needed. Editor assets are always read regardless of the minified-size limit, so iframe findings are not affected.

The license screen says licensing is not configured#

Symptom: Tools → Editor Readiness License shows a warning instead of the key field.

Cause: The ERS_STOREENGINE_PRODUCT_ID constant or the ers_storeengine_product_id filter has set the product ID to 0, or the bundled StoreEngine SDK did not load.

Fix: Remove the constant or filter, and re-install the plugin from a fresh zip if the library/storeengine folder is missing.

Updates are not offered#

Symptom: A newer version exists on technoleet.dev but Dashboard → Updates does not list it.

Fix:

1. Open Tools → Editor Readiness License and confirm the status is Active and Automatic Update is Enabled. Renew or re-activate if not.
2. Click the check-now link next to Last Checked to refresh the license.
3. Go to Dashboard → Updates and click Check again.