Fixes #8659: remove outdated Ezoic Integration conflict notice - #8660
Open
rickydeez wants to merge 1 commit into
Open
Fixes #8659: remove outdated Ezoic Integration conflict notice#8660rickydeez wants to merge 1 commit into
rickydeez wants to merge 1 commit into
Conversation
Ezoic's WordPress plugin is now JavaScript integration only and no longer blocks WP Rocket page caching the way the legacy HTML integration did.
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the legacy Ezoic Integration “conflicting plugin” admin notice and its wiring, since the current Ezoic plugin no longer blocks WP Rocket caching (JS integration only).
Changes:
- Removed the Ezoic third-party subscriber that added the conflict + custom explanation.
- Unregistered the Ezoic service from the ThirdParty ServiceProvider and from the plugin’s common subscriber initialization.
- Removed the now-obsolete Ezoic integration tests covering the conflict filters.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/Integration/inc/ThirdParty/Plugins/Optimization/Ezoic/addExplanations.php | Removed integration test for the Ezoic conflict explanation filter output. |
| tests/Integration/inc/ThirdParty/Plugins/Optimization/Ezoic/addConflict.php | Removed integration test for the Ezoic conflict plugin list filter output. |
| inc/ThirdParty/ServiceProvider.php | Unregistered the ezoic service (no longer provided or registered in the container). |
| inc/ThirdParty/Plugins/Optimization/Ezoic.php | Deleted the Ezoic conflict subscriber implementation (no longer adds conflict/explanation). |
| inc/Plugin.php | Removed ezoic from the common subscriber initialization list. |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Removes the admin conflict notice that tells publishers to deactivate the Ezoic Integration plugin.
That notice was added for Ezoic's legacy WordPress HTML/proxy integration (#2200 / #4533), which interfered with page caching. The current Ezoic plugin is JavaScript integration only and does not block WP Rocket caching, so the notice is incorrect for current installs.
Closes #8659
Type of change
Checklist
Additional context
Ezoic docs already note this warning applies only to the legacy method:
https://support.ezoic.com/kb/article/third-party-tools-javascript-integration