fix(parse.ly): update meta_type default#4724
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates Newspack’s automated configuration defaults for the Parse.ly plugin to use Parse.ly’s recommended meta_type setting (repeated_metas), intended to avoid the Yoast conflict referenced in NPPM-2833.
Changes:
- Change the default Parse.ly setting
meta_typefromjson_ldtorepeated_metaswhen Newspack initializes Parse.ly settings for the first time.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Just noting the lint failure was fixed here in trunk: #4718 |
adekbadek
left a comment
There was a problem hiding this comment.
Verified end-to-end in an isolated env: the new default serves repeated_metas, and a stored meta_type=json_ld flips correctly on the real admin_init path.
One blocker and a few suggestions and nits.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Thanks for the review @adekbadek! This is ready for another look. |
adekbadek
left a comment
There was a problem hiding this comment.
Migration blocker resolved: an absent meta_type key and an empty option both migrate now via the ?? 'json_ld' default, with unit tests locking each branch (including the inactive-plugin stays-pending and idempotency cases). The admin_init re-run for late wp-parsely activations and the unconditional override of a deliberate json_ld choice are both documented and sound.
adekbadek
left a comment
There was a problem hiding this comment.
Migration blocker resolved: an absent meta_type key and an empty option both migrate now via the ?? 'json_ld' default, with unit tests locking each branch (including the inactive-plugin stays-pending and idempotency cases). The admin_init re-run for late wp-parsely activations and the unconditional override of a deliberate json_ld choice are both documented and sound.
|
Hey @chickenn00dle, good job getting this PR merged! 🎉 Now, the 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! ❤️ |
## [6.42.3](v6.42.2...v6.42.3) (2026-06-17) ### Bug Fixes * **parse.ly:** update meta_type default ([#4724](#4724)) ([d5f4ea9](d5f4ea9))
|
🎉 This PR is included in version 6.42.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# [6.43.0-alpha.2](v6.43.0-alpha.1...v6.43.0-alpha.2) (2026-06-17) ### Bug Fixes * **audience:** decode HTML entities in campaign prompt titles ([#4711](#4711)) ([d22bd0f](d22bd0f)) * correct submit button text on change-payment-method page ([#4654](#4654)) ([15b230d](15b230d)) * **parse.ly:** update meta_type default ([#4724](#4724)) ([d5f4ea9](d5f4ea9)) * prevent content-gate editor.scss styles from getting chunked into the common.css file ([#4716](#4716)) ([4d4c557](4d4c557)) * **reader-activation:** exclude peeking newsletter from a11y tree ([#4744](#4744)) ([aba7794](aba7794)) * remove colour label changes to avoid bleeding into other blocks ([#4703](#4703)) ([befce8c](befce8c)) * **wc-memberships:** skip expiry filter for non-subscription memberships ([8769161](8769161)) * **web-preview:** right-align toolbar close button ([589248d](589248d)) ### Features * **admin:** companion to newspack-newsletters admin UX milestone ([#4735](#4735)) ([6d0566a](6d0566a)) * **block-theme:** add search overlay block ([#4729](#4729)) ([328f1ea](328f1ea)) * **integrations:** add inactive plugin state ([#4721](#4721)) ([f87a50f](f87a50f)) * **integrations:** add oauth and hidden field types ([#4639](#4639)) ([daafa6b](daafa6b)) * **integrations:** details modal and Run now for integration logs ([#4757](#4757)) ([db5ba79](db5ba79))
|
🎉 This PR is included in version 6.43.0-alpha.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
## [6.42.3](Automattic/newspack-plugin@v6.42.2...v6.42.3) (2026-06-17) ### Bug Fixes * **parse.ly:** update meta_type default ([#4724](Automattic/newspack-plugin#4724)) ([65335bf](Automattic/newspack-plugin@65335bf))
All Submissions:
Changes proposed in this Pull Request:
Closes https://linear.app/a8c/issue/NPPM-2833/possible-conflict-between-yoast-and-our-required-parsely-code-that-may
This PR updates the default meta_type parse.ly config to
repeated_metaswhich is recommended by parse.ly . This also implements a migrator so existing sites with Parse.ly get the updated setting.We need to do this to avoid the conflict pointed out in the linear task above when Yoast is active.
Removing parsely
These tests will require removing parsely and parsely settings several times. You can do so with the following:
release, add the following snippet to a site where parsely is removed:repeated_metasrepeated_metasOther information: