Title: essemge's Replies | WordPress.org

---

# essemge

  [  ](https://wordpress.org/support/users/essemge/)

 *   [Profile](https://wordpress.org/support/users/essemge/)
 *   [Topics Started](https://wordpress.org/support/users/essemge/topics/)
 *   [Replies Created](https://wordpress.org/support/users/essemge/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/essemge/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/essemge/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/essemge/engagements/)
 *   [Favorites](https://wordpress.org/support/users/essemge/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Forminator 1.46.2 not detecting update to 1.55.1 (WP-CLI confirmed)](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/)
 *  Thread Starter [essemge](https://wordpress.org/support/users/essemge/)
 * (@essemge)
 * [1 week, 5 days ago](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/#post-18963180)
 * 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
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Forminator 1.46.2 not detecting update to 1.55.1 (WP-CLI confirmed)](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/)
 *  Thread Starter [essemge](https://wordpress.org/support/users/essemge/)
 * (@essemge)
 * [1 week, 6 days ago](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/#post-18962970)
 * Hi Patrick,
 * I checked Tools → Site Health as suggested. It reports one critical issue:
    - Background updates are not working as expected.
    - 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, which manages WordPress core updates, so some
   of these settings may be hosting-related.
 * I also noticed WPCode is installed, although I did not install or configure it
   myself, so I do not want to disable it on the live site without knowing what 
   its snippets control.
 * Could these Site Health findings explain why the Forminator plugin update is 
   not being detected, or should I proceed with the staging-site conflict test you
   recommended?
 * Best regards,
   Sophie
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Forminator 1.46.2 not detecting update to 1.55.1 (WP-CLI confirmed)](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/)
 *  Thread Starter [essemge](https://wordpress.org/support/users/essemge/)
 * (@essemge)
 * [1 week, 6 days ago](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/#post-18962969)
 * 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?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Forminator 1.46.2 not detecting update to 1.55.1 (WP-CLI confirmed)](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/)
 *  Thread Starter [essemge](https://wordpress.org/support/users/essemge/)
 * (@essemge)
 * [1 week, 6 days ago](https://wordpress.org/support/topic/forminator-1-46-2-not-detecting-update-to-1-55-1-wp-cli-confirmed/#post-18962713)
 * **Additional information following Flywheel’s investigation:**
 * Flywheel has now completed a server-side investigation.
 * They confirmed:
    - WordPress is **not** detecting an available Forminator update.
    - They reproduced the same result using **WP-CLI**.
    - They reviewed the security advisory and confirmed my installed version (1.46.2)
      is within the affected range.
    - They investigated an initial malware alert and confirmed it was a **false 
      positive**. They found **no evidence of malware** on the site.
    - They advised me to contact the Forminator team because the update is not being
      offered despite a patched version existing.
 * I hope this helps with your investigation.

Viewing 4 replies - 1 through 4 (of 4 total)