Generic conflict notice flags Jetpack without checking Site Accelerator

[pirate-bot]

Summary

Optimole can display its “Multiple image optimization plugins active” notice when Jetpack is active even if Jetpack’s image Site Accelerator is not enabled. The notice is expected only when an active Jetpack image feature can conflict with Optimole; instead, plugin activation alone triggers the warning on the inspected path. This can mislead users into diagnosing a conflict that is not present and may contribute to unnecessary plugin deactivation.

Customer context

Product / area: Optimole WordPress plugin, admin conflict notice
Version: 4.2.11
Environment: WordPress site with Jetpack active; further environment details were not provided
Integration / third party: Jetpack
Reported error / symptom: WordPress reports that Optimole conflicts with Jetpack
Impact: The reporter deactivated Optimole after long-term use; direct causality and Jetpack Site Accelerator state are unknown

Reproduction notes

Code-derived reproduction:

1. Install Optimole 4.2.11 and activate Jetpack.
2. Leave Jetpack’s image Site Accelerator disabled.
3. Visit a WordPress admin screen where Optimole notices are rendered.
4. Observe whether “Multiple image optimization plugins active” lists Jetpack.

The path is confirmed by inspection but was not executed in a WordPress runtime. The reporter did not provide the Jetpack version, module state, exact notice text, or screen location.

Diagnosis

Conclusion

The generic admin notice has a confirmed false-positive branch. Jetpack is included in the generic conflicting-plugin list, and that list is filtered only by whether the Jetpack plugin is active. No check of Jetpack Photon/Site Accelerator state occurs on this path. A separate conflict class demonstrates the narrower intended condition by checking Jetpack’s photon module.

Where this likely occurs

• Admin conflict-notice surface: inc/conflicts/conflicting_plugins.php — Optml_Conflicting_Plugins::defined_plugins() lines 43–61 adds jetpack/jetpack.php; Optml_Conflicting_Plugins::get_active_plugins() lines 71–76 retains entries based only on is_plugin_active().
• Notice rendering: inc/admin.php — Optml_Admin::add_notice_conflicts() lines 899–950 presents retained entries as active image-optimization plugins that may conflict with Optimole.
• Comparison path: inc/conflicts/jetpack_photon.php — Optml_Jetpack_Photon::is_conflict_valid() lines 36–45 checks both Jetpack activation and Jetpack::is_module_active( 'photon' ).
• Regression history: commit a404964e added Jetpack to the generic list while removing the feature-aware lazy-loading conflict class. The change first appears in v4.1.0; v4.0.4 is the preceding release, and the reported v4.2.11 contains it.

Engineering notes

The confirmed scope is the generic WordPress admin notice. Optimole’s dashboard conflict manager retains a separate Photon-aware path, so users may receive conflict messaging through two mechanisms with different eligibility rules. Jetpack source is not present in the inspected workspace; no claim is made about current Jetpack module behavior beyond Optimole’s own conditional call. A search of existing issues in Codeinwp/optimole-wp found no matching open or closed issue.

Test coverage status

tests/test-plugin-conflicts.php — Test_Plugin_Conflicts lines 14–49 covers generic conflict collection and dismissal using mocked Smush entries. It does not cover Jetpack with Photon enabled or disabled. No relevant Jetpack integration or end-to-end coverage was found during inspection.

What to verify or explore next

• May be worth reproducing on v4.2.11 with Jetpack active and Site Accelerator for images disabled, then recording whether the generic notice appears.
• May be worth repeating with Site Accelerator enabled to distinguish the generic notice from the dedicated Photon conflict message.
• If available, checking the targeted PHP conflict suite and an admin-notice integration scenario across v4.0.4, v4.1.0, and v4.2.11 would confirm the release boundary.

Unknowns / follow-up

The uninstall submission does not identify which of the two Optimole conflict messages appeared or whether Jetpack Site Accelerator was enabled on that site.

Confidence

Confidence: 93/100

Repository inspection confirms a reachable false-positive notice path in v4.2.11: generic conflict detection treats Jetpack activation alone as proof of an image-optimization conflict, unlike the separate Photon-aware check. The other two uninstall comments lack enough detail or matching code evidence to confirm product defects.

---

Source: automated uninstall feedback — optimole-wp, 2026-08-31
Generated by bug-report-triage (ID: bug-report-triage_6a965c1bdc8373.61433803)