Skip to main content

21 posts tagged with "Bug Fix"

Bug Fixes

View All Tags

1.33.1 - MCP Adapter is no longer required

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

Yoko Core no longer requires the MCP Adapter plugin. 1.33.0 made it a hard requirement, so on a site without MCP Adapter, Yoko Core showed a missing-plugin notice and could not be reactivated. 1.33.1 removes the requirement. Nothing else changes from 1.33.0.

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.

1.31.0 - A Card block that is one accessible link, Additional CSS that understands nesting, and a theme's icons in the Icon block

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

Three features. Card is a new block that works like a Group and can turn the whole card into one accessible link — the image, the padding, the gap between two lines. The Additional CSS box on every block now behaves like Sass: nesting works to any depth, and media queries work where they were silently dropped before. And a theme's own SVG files now appear in the Icon block — drop them in an /icon folder and they are there. A stretched-link fix comes with them.

1.29.1 - The primary term option works on WordPress 6.7

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

The Primary Term option that 1.29.0 added to the terms block did nothing at all on WordPress 6.7. A block set to render only the primary term rendered every term, with nothing to indicate the setting was being ignored. Sites on 6.8 were unaffected, which is why this went unnoticed. The option is also now two toggles rather than a dropdown, matching the rest of the panel it sits in.

1.29.0 - The block editor stops deleting primary terms and unpublish dates

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

Version 1.29.0 brings two per-post controls to the block editor that only ever existed in the classic one — the primary term picker and the unpublish date — and gives the terms block a primary-term option. Both controls had the same thing wrong with them, and it was worse than their absence: a save in the block editor deleted the value the classic editor had stored.

1.28.2 - Taxonomy fields suggest something before you type

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

Clicking a field in the Consolidated Taxonomy Panel before typing anything opened a dropdown with nothing in it, so an editor had to guess at a term name before the field would show them anything. It now lists the whole taxonomy on that first click, most-used terms first. The release zip also drops about a megabyte of npm lockfiles that were never used at runtime.

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.