Skip to main content

1.33.0 - SEOPress schema cleanup, soft-gate hooks, and a required MCP Adapter

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

Yoko Core now tidies the structured data SEOPress generates for events and posts, so Google can read dates, locations, attendance mode and tickets, and a new WP-CLI command shows exactly what a page emits. The soft gate gains two developer hooks: one lets known members past it, the other reacts when someone fills in its form. Yoko Core now requires the MCP Adapter plugin — install it before updating. Three fixes: a renamed standalone SSO plugin no longer crashes wp-admin, ACF's styled selects work again, and testing-walkthrough scenarios no longer vanish.

  • [DEPENDENCY] Yoko Core now requires the MCP Adapter plugin. WordPress will not activate Yoko Core without it. An already-active Yoko Core keeps running after the update, but shows a missing-plugin notice and cannot be reactivated until MCP Adapter is installed. MCP Adapter is not on WordPress.org, and its folder must be named exactly mcp-adapter: a GitHub zip unpacks under a different name, which WordPress does not accept.

  • [NEW FEATURE] SEOPress Event & Article schema — Yoko Core corrects the Event schema SEOPress generates automatically:

    • dates in the format Google expects;
    • a structured address;
    • in-person, virtual or hybrid attendance, taken from the Event Format;
    • the online location and the ticket offer, at the public (non-member) price;
    • the event's own page as its URL, not the venue's website.

    For posts, the schema author can come from an Author byline field instead of the WordPress user.

  • [CLI] wp yoko schema show <post-id> prints the final Event or Article JSON-LD for a post, with those corrections applied. It is read-only, so support can check a page without viewing its source.

  • [NEW FEATURE] Soft gate: bypass cookies. The yoko_soft_gate_bypass_cookies filter lets a site name cookies that carry a known visitor past the gate without an access link, for example a member cookie left by SSO. The rules are matched in the browser, so they are safe behind the full-page cache.

  • [NEW FEATURE] Soft gate: yoko_soft_gate_submitted fires once when a visitor submits the gate's form, whether that is the built-in email field or an embedded Gravity Form. A site can use it to tag the lead or pass it on to a CRM.

  • [BUG FIX] A site running the standalone SSO & Content Protection plugin from a renamed folder, as a GitHub zip installs it (yoko-sso-cp-main), no longer crashes in wp-admin and WP-CLI with Cannot declare class Yoko_Co_SSO. Yoko Core now skips its bundled copy whenever the class is already declared. On one client's staging site this had been failing every deploy since May.

  • [BUG FIX] ACF's "stylised UI" select fields work again in wp-admin. Yoko Core loaded its own copy of Select2 under the shared select2 name on every admin screen, which stopped ACF from loading its own, so those fields showed as a plain dropdown with the value echoed beside it. Yoko Core now uses a private name for its copy.

  • [BUG FIX] The Testing Walkthrough builds its tabs from the config's phases list instead of a fixed set of five. Before, a scenario whose phase was not one of those five was silently left out, although it still counted towards the progress total. A config without phases gets the original five tabs, and a scenario whose phase is not declared still gets a tab of its own.