Skip to main content

1.25.1 - Soft Gate reaches the classic editor, and stops gating logged-in users

· 2 min read
Konstantin Brazhnik
Senior Full Stack Engineer @ Yoko Co

Version 1.25.1 fixes a Soft Gate bug worth updating for: the gate was showing to logged-in users, so administrators, editors and members were blurred out of their own content. It also brings per-post soft gating to the classic editor and page builders, which 1.25.0 could only do from the block editor.

  • [FIX] Stops the soft gate rendering for logged-in visitors. In 1.25.0 nothing in the render path checked login state, so the blur, the dialog and the gate assets went to everyone — administrators included. Soft gating exists to collect an email address from a stranger, so it now emits nothing at all once a visitor is signed in. Any site with Soft Gate enabled should take this update.
  • [FEATURE] Adds a Soft Gate metabox for the classic editor, with the same fields as the block editor's Document sidebar panel. In 1.25.0 the panel was the only per-post UI and it existed solely in the block editor, so a post type served by the classic editor — or taken over by Beaver Builder, Elementor or WPBakery — could not be soft gated per post at all. Both editors now write the same post meta, so a post configured in one reads correctly in the other, and a post never shows both UIs.
  • [FIX] Corrects the Soft Gate documentation where it described behavior the code did not have: the troubleshooting entry for logged-in visitors blamed a caching layer for what was really this bug, and the per-post section said classic-editor configuration was impossible.
Upgrading from 1.25.0

Nothing to migrate. Both changes are additive and read the post meta 1.25.0 already wrote, so posts configured under 1.25.0 keep working exactly as they were — they just stop gating your signed-in staff.