Fix inconsistent legacy WordPress footers - #10
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the WordPress companion plugin’s rendered-HTML compatibility layer to normalize additional legacy Brizy footer variants to the current operator/copyright/tagline text, and bumps the plugin version to 0.1.4.
Changes:
- Expand legacy footer matching to handle multiple operator/copyright/tagline variants and whitespace/entity differences.
- Add/adjust PHPUnit coverage for legacy variants and idempotence of the current footer.
- Update plugin docs/changelog text and bump plugin header version to 0.1.4.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| wordpress-plugins/calorieapp-identity-bridge/includes/class-calorieapp-identity-bridge-legal-footer-compatibility.php | Broadens regex-based legacy footer normalization (operator/copyright/tagline). |
| wordpress-plugins/calorieapp-identity-bridge/tests/test-legal-footer-compatibility.php | Adds test cases for multiple legacy variants and idempotence. |
| wordpress-plugins/calorieapp-identity-bridge/calorieapp-identity-bridge.php | Bumps plugin version to 0.1.4. |
| wordpress-plugins/calorieapp-identity-bridge/README.md | Updates version history narrative to include 0.1.4 footer normalization scope. |
| wordpress-plugins/calorieapp-identity-bridge/TESTING.md | Updates documented covered scenarios to include idempotence and variant normalization. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Summary
Operator: ICTHendrikse · KVK 73774693Scope and safety
This remains a rendered-public-HTML compatibility layer. It does not alter stored WordPress pages, products, Tokenomics data, payment logic, or authentication data.
Verification
Production WordPress deployment is intentionally not performed by this PR.