Let WP_SCSS_OPTIONS in wp-config.php override the saved settings - #282

Summary

• Done when: with define('WP_SCSS_OPTIONS', array('base_compiling_folder' => 'Current Theme', 'scss_dir' => '/scss', 'css_dir' => '/css', …)) in wp-config.php and no wpscss_options row in the database, the front page compiles and enqueues the CSS, and the settings page names the overridden keys. Checked in Docker (WP 7.1.4, PHP 8.4), along with a partial override (only compiling_options) layered over saved settings, always_recompile => true and enqueue => false.
• Fixes Configure plugin via define or json #222: the settings could only live in the database, so they couldn't be versioned or set per environment from code. A filter in a theme wasn't an option either: the plugin reads its settings when it loads, before the theme runs. The constant is merged over the saved option. It adds the trailing slash the settings form would add, accepts true/false for the two checkboxes (the compiler checks for the string '1'), and runs through the existing Leafo-name cleanup, so the old snippet from the issue thread still works.
• How this could fail: the form fields still show the database values for any key the constant overrides. An admin who edits one and saves sees "Settings saved" and nothing changes. The warning above the form names those keys, so it's visible, but someone who doesn't read it could be confused.

🤖 Generated with Claude Code