Here’s a roundup of the fixes we’ve shipped since our June 2–15 roundup.
- Separator blocks now use their correct default width on sites running WordPress 7.0, where they had started displaying at the wrong width. (newspack-theme@2.23.3)
- Wide- and full-width blocks now expand properly when placed inside content sections, instead of being held to the narrower content width. (newspack-theme@2.23.2)
- The new Advanced settings tab no longer appears in the Audience settings on sites that don’t use group subscriptions or access control, where it had shown up by mistake. (newspack@6.43.2)
- Readers clicking through from a newsletter now reliably skip the paywall. On sites using Mailchimp’s audience-level tracking — the default for most publishers — some valid newsletter links were still being stopped; they now bypass the paywall as intended. (newspack@6.43.1)
- Campaigns targeted to reader segments now reach the right readers. A segment condition that had been switched off (such as “articles read in session”) was still being applied, which kept some prompts from showing to readers who qualified. (newspack-popups@3.12.2)
- Parse.ly analytics now hold up better alongside Yoast SEO. Newspack switches to Parse.ly’s recommended setup, clearing a conflict that could interfere with analytics, and existing sites are updated automatically. (v6.42.3)
- Fixes newsletters reaching the wrong contacts on Mailchimp. When the send list or segment changed, the previous list’s recipients could carry over; the recipient count now matches the list selected. (newspack-newsletters@3.34.1)
- Icon-only buttons now show as proper squares in the block theme, instead of taking on an uneven shape. (newspack-block-them e@1.28.4)
- The Allow duplicate content toggle is available again on Homepage Posts and Carousel blocks set to Static mode. Without it, a post pinned in a static block could disappear from a dynamic block higher up the same page, with no way to bring it back. (newspack-blocks@4.26.5)
