From 6db7eb9e876cf66ac057d55f603797e080463948 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 27 Oct 2025 16:19:04 +0000 Subject: [PATCH] Fix setSiteLanguage blueprint step to use option instead of constant MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changed the implementation from using defineConstant('WPLANG') to update_option('WPLANG') so the site language can be changed from the WordPress admin UI (Settings > General). Constants cannot be modified after they are defined, but options can be updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../blueprints/src/lib/steps/set-site-language.ts | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/packages/playground/blueprints/src/lib/steps/set-site-language.ts b/packages/playground/blueprints/src/lib/steps/set-site-language.ts index bbcb2247f2..3344f61782 100644 --- a/packages/playground/blueprints/src/lib/steps/set-site-language.ts +++ b/packages/playground/blueprints/src/lib/steps/set-site-language.ts @@ -59,10 +59,16 @@ export const setSiteLanguage: StepHandler = async ( ) => { progress?.tracker.setCaption(progress?.initialCaption || 'Translating'); - await playground.defineConstant('WPLANG', language); - const docroot = await playground.documentRoot; + // Set the site language as an option (not a constant) so it can be changed from the admin UI + await playground.run({ + code: `