fix: restore Media Kit components in Ads wizard#3881
Conversation
|
We need to have a "Plugins" tab because why would the page has heading that says "Settings" and then we scroll down and there's another heading, this time that says "Plugins". |
laurelfulford
left a comment
There was a problem hiding this comment.
Thanks for tackling this, @dkoo! Everything saves as expected, and TIL Ad Refresh Control was a separate plugin?
The only thing I noticed was that the Suppression section isn't 1:1 with how it looks in the mockup (with the header, and without the border), but I think that could be tackled in a second, less urgent iteration.
I'm marking as approved from a functional perspective, but I'm happy to take another look if you end up breaking 'Plugins' into its own tab in this PR like @thomasguillot recommended.
|
Thanks, @laurelfulford! Yeah, re: the "Suppression" settings, I'm proposing here that we wrap the section in a card like the other settings sections so that the page looks more visually consistent. Ok with you, @thomasguillot? Note that we've also decided to eliminate the "Plugins" heading halfway down the page. The whole page now looks like this. with all settings sections existing at the same hierarchy in the Settings page: I'll flag this as needing a design review from @thomasguillot since the end result is a bit different than the original designs. |
## [6.2.2](v6.2.1...v6.2.2) (2025-04-03) ### Bug Fixes * restore Media Kit components in Ads wizard ([#3881](#3881)) ([86fa89a](86fa89a))
|
🎉 This PR is included in version 6.2.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |


All Submissions:
Changes proposed in this Pull Request:
Hotfix to add some IA reorganization that was missed.
Note: I did not move the Super Cool Ad Inserter plugin settings to the "Plugins" settings in this PR, as is outlined in the design mockup. These settings are more tightly integrated into the Newspack Ads plugin and moving them would require a more extensive refactor that doesn't fit the urgency of this issue. cc @thomasguillot if we'd like to flag this for a future refactor.
How to test the changes in this Pull Request:
Other information: