From 03ad22535623f03ce4af84cc119e7ab79a67848a Mon Sep 17 00:00:00 2001 From: Dhrupo Date: Fri, 6 Nov 2026 23:43:53 +0600 Subject: [PATCH 1/2] Report an error when `wp theme mod set` cannot save the value --- features/theme-mod.feature | 18 ++++++++++++++++++ src/Theme_Mod_Command.php | 2 +- 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/features/theme-mod.feature b/features/theme-mod.feature index 24ad1d71..3609627f 100644 --- a/features/theme-mod.feature +++ b/features/theme-mod.feature @@ -159,6 +159,24 @@ Feature: Manage WordPress theme mods Success: Theme mod background_color set to 123456. """ + Scenario: Setting a theme mod that does not get saved + Given a WP install + And a wp-content/mu-plugins/override-theme-mod.php file: + """ + Date: Sat, 7 Nov 2026 00:29:48 +0600 Subject: [PATCH 2/2] Compare the stored theme mod when checking that `wp theme mod set` saved it --- features/theme-mod.feature | 16 ++++++++++++++++ src/Theme_Mod_Command.php | 4 +++- 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/features/theme-mod.feature b/features/theme-mod.feature index 3609627f..4fe86cae 100644 --- a/features/theme-mod.feature +++ b/features/theme-mod.feature @@ -177,6 +177,22 @@ Feature: Manage WordPress theme mods And STDOUT should be empty And the return code should be 1 + Scenario: Setting a theme mod whose value is changed when it is read + Given a WP install + And a wp-content/mu-plugins/filter-theme-mod.php file: + """ +