essemge

Hi Amin,

Thank you for your reply.

I have now completed the Site Health checks that Patrick suggested.

The critical issue reported is:

“Background updates are not working as expected.”

More specifically, Site Health reports:

• “A plugin has prevented updates by disabling wp_version_check().”
• WP_AUTO_UPDATE_CORE is set to false.
• A number of WordPress core files are reported as not writable.

The site is hosted by Flywheel, who manage WordPress core updates, so I appreciate that some of these findings may be expected in a managed hosting environment.

Flywheel have also completed a server-side investigation and confirmed:

• they reproduced the issue using WP-CLI (no Forminator update is detected);
• there is no evidence of malware (the earlier scan results were confirmed to be false positives);
• my current Forminator version (1.46.2) is within the affected security advisory range.

Before I create a staging site and carry out a full conflict test, could you please clarify one point?

Do the Site Health findings—particularly “A plugin has prevented updates by disabling wp_version_check()“—suggest a known cause that could explain why Forminator updates are not being detected, or would you still recommend proceeding with the staging conflict test as the next diagnostic step?

I’d like to understand whether these findings are likely to be related before making changes, even on a staging site.

Thank you very much for your help.

Kind regards,

Sophie

Thanks Patrick.

I checked Site Health as suggested and it reports the following critical issue:

• A plugin has prevented updates by disabling wp_version_check().

It also reports that background updates are not working as expected.

Since Flywheel has already confirmed that neither WordPress nor WP-CLI detects the Forminator update, could this be related? Is there a known plugin or configuration that could interfere with Forminator update detection in this way?