Here’s a roundup of the fixes we’ve shipped since Hotfix roundup: August 10–14, 2026. WordPress 7.1 arrived this week, and several of these smooth over changes it brought with it.
Newspack
- On sites running WordPress 7.1 with content gifting turned on, readers opening a gifted article were served a truncated version instead of the full story. WordPress changed how it identifies the code it has been handed, so the step that lifts the WooCommerce Memberships paywall stopped taking effect. (newspack@6.48.11)
- On sites with Audience Management enabled, the Continue button on the reader sign-in form kept spinning after a returning reader submitted their email and the form moved on to the password or one-time-code step. The button now clears its loading state at every step, on the inline form as well as the sign-in modal. (newspack@6.48.12)
- Donation receipt and welcome emails printed “Card – stripe” where the payment method should have appeared. Those emails now show the card brand and last four digits when the site has them — “Visa ending in 4242” — and a plain “Credit / Debit Card” when it doesn’t. (newspack@6.48.1)
- Blocks hidden from some readers stayed hidden on the page but were still returned by the site’s REST API, so an app or integration reading a post that way received content those readers were not meant to see. The API now applies the same visibility rules the page does. (newspack@6.48.8)
- Blocks hidden from some readers still appeared in auto-generated excerpts — the teasers on the homepage, archives, search results and feeds. A post’s teaser now shows the same thing its article page shows that reader. (newspack-blocks@4.30.2, newspack-listings@3.7.2, newspack@6.48.4)
- The Initial list size control under Audience → Configuration showed 2 whatever a publisher had saved, so the setting looked like it never stuck. It now shows the saved value. (newspack@6.48.6)
- On sites updated to WooCommerce Subscriptions 9.0, the subscription product types the Audience wizard creates stopped appearing in the product-type dropdown — version 9.0 turns them off by default on sites that never configured them. Newspack now switches them back on. (newspack@6.48.7)
- The safety net that publishes posts whose scheduled time passed without them going live skipped Campaign prompts and Sponsors, so one of those that missed its slot stayed unpublished until someone noticed. Both are covered now. (newspack@6.48.14)
- Four fixes tightened how Newspack handles values it can’t vouch for, all found in review. (newspack@6.48.10, newspack@6.48.9, newspack-ads@3.14.2, newspack-newsletters@3.39.1)
Newsletters
- On sites running WordPress 7.1, a newsletter re-saved in the editor lost its button widths in the email that went out, because 7.1 moved where that setting is stored. The newsletter renderer now reads both the old and the new form. (newspack@6.48.2, newspack-newsletters@3.39.3)
- On sites connected to ActiveCampaign, trashing a newsletter could delete an unrelated campaign in that ActiveCampaign account — automations and already-sent campaigns included. Newspack was sending the newsletter’s message ID to a call that expected a campaign ID; that code path is gone. Publishers who have trashed newsletters may want to check their ActiveCampaign campaign list. (newspack-newsletters@3.39.2)
- On sites running WordPress 7.1, newsletters could not be saved — the editor’s Save button stayed disabled. WordPress 7.1 added a save-state check that exposed a lock the newsletter editor was never releasing, and the lock is now released. (newspack@6.48.2, newspack-newsletters@3.39.3)
- The Newsletter Subscription block’s form response now returns a fixed set of fields instead of passing through whatever the email service provider sent back. Custom JavaScript on a site that reads provider-specific fields off that response will no longer receive them. (newspack-newsletters@3.39.4)
Campaigns
- On sites running Perfmatters, above-header prompts appeared only after a delay of several seconds, and the page shifted when they arrived. Newspack’s own Perfmatters defaults were holding back the script that reveals the prompt. Published above-header prompts now render immediately. (newspack-popups@3.16.2)
- On sites running WordPress 7.1, the first click on any link inside a prompt preview dropped out of the preview into the ordinary page, so the prompt stopped following the editor and unsaved settings stopped being reflected. Previews stay in place now. (newspack-popups@3.16.4, newspack@6.48.3)
Newspack Network
- Galleries built with WordPress 7.1’s dynamic gallery — which stores “show the images attached to this post” rather than a list of images — arrived on network sites showing a single unrelated image, or nothing at all, with no error. Distributed posts now carry the resolved images. (newspack-network@2.22.1)
Advertising
- On sites using Broadstreet as their ads provider with a custom ad background color set under Customize → Colors, empty ad slots rendered as colored gaps — most visibly a padded strip in the footer. Only slots that actually hold an ad get that background now. (newspack-theme@2.25.1, newspack-ads@3.14.1)
Listings
- For editors whose computer is set to a different timezone from the site, the Event Dates block redisplayed a saved time shifted by the offset — 6:00 PM entered on a UTC site came back as 11:00 PM. An editor who corrected what they saw would have saved a time that really was wrong. The block now shows the time that was set. (newspack-listings@3.7.3)