feat: add corrections customize settings

[Takshil-Kunadia]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

• Add a new Panel and global customizer setting “Corrections Location” (with options “Top” and “Bottom”).
• Fix a edge case in Correction Modal.

Closes # .

How to test the changes in this Pull Request:

1. Open the WordPress Customizer and Load a single post in the theme.
2. Open Template Settings > Correction Settings > Corrections & Clarifications, and check the Radio buttons Top & Bottom to see the impact.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[Takshil-Kunadia]

@leogermani
Currently, if corrections are enabled and present, they are automatically appended to the post content. However, we are not providing users with an option to enable or disable corrections per post, as was originally intended by:

newspack-plugin/includes/corrections/class-corrections.php

Line 32 in abd1bc2

const CORRECTIONS_ACTIVE_META = 'newspack_corrections_active';

Would you like me to add a UI option to enable/disable corrections for individual posts?

Additionally, if we proceed with this implementation, corrections will be appended to all posts by default. This might not be ideal for users who may want to use blocks we are going to create via https://app.asana.com/0/1209292256643614/1209292256643625.

Would it make sense to introduce a separate setting in the modal for "Enable/Disable auto-inserting corrections" so users can choose whether corrections should be automatically appended? We could reuse(and rename it) CORRECTIONS_ACTIVE_META for this, but I wanted to check with you first—should we manage "enable/disable corrections" and "auto-insert corrections" separately, or should they share the same meta field?

[leogermani]

should we manage "enable/disable corrections" and "auto-insert corrections" separately, or should they share the same meta field?

As @laurelfulford suggested here, let's only filter into the_content if the active theme is not a block theme

[naxoc]

This looks good 👍 I tested "Open Template Settings > Correction Settings > Corrections & Clarifications" and it works great. It's not under Template Settings, but directly under "Corrections Settings", but I also think that makes more sense.

[Takshil-Kunadia]

Thanks! @leogermani @naxoc for taking a look 🙇 . Merging this PR 🚀

[github-actions]

Hey @Takshil-Kunadia, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

[matticbot]

🎉 This PR is included in version 6.0.0-alpha.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀