You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CSS scope guard was reading weeks-stale stylesheets. Builderius keeps the current saved state in its branch/commit storage (the newest builderius_commit named by the branch's active_commit meta), not in the builderius_dsm snapshot posts the guard indexed — and the global stylesheet's entity is the settings set (the old global-settings slug is defunct). The guard and its refresh route now resolve the live commit, keeping the old snapshot read as a fallback for installs without commit rows. Before the fix the ownership index could miss almost every current global class, so the "rules are stored in the other scope" warning never fired for recently saved styles.
Changed
Settings-page copy rewritten in plain British English. Every description now says what the feature does in full sentences, with consistent terms throughout. A few clearer titles: Search field icons, Tidier Navigator icons, Collapse & expand buttons, Right-click menu enhancements, CSS scope guard, Unsaved-changes marker, Preview overlay contrast fix.
New
The builder UI is translatable. Every string the plugin renders in the builder — tooltips, menus, dialogs, toasts, screen-reader announcements — now goes through WordPress internationalisation and ships on the config object, with a POT template in /languages and bundled-translation loading (Domain Path + load_plugin_textdomain()). The only strings left in English are the native Builderius menu labels the plugin matches against to drive the builder. Translators: placeholders use sprintf syntax, and counted strings ship as singular/plural pairs.