Doing some theming here...
I've noticed that the color module functionality is...
- You can select your pre-configured scheme(s) in the drop-down, as laid out in the theme's color.inc file.
- Once there in the UI, any changes to any of the individual colors instantiates a "Custom" scheme, and the dropdown selector reflects that fact. so far, so good.
The problem is this: Once you change one of your custom colors, you can never go back to the custom scheme you had once set up, even though that scheme continues to persist, as long as you don't click 'Save' in the UI. I've tried clearing all caches, to no avail. Someone please let me know if I'm wrong on that.
This could be solved in one of two ways that I can anticipate, either
- Provide a 'Current Scheme' (or maybe, 'Revert') button in the dropdown, which would cancel your pending unsaved custom colors by reverting to what the theme is currently using.
- Provide a means for the user to save his current custom scheme as a named scheme which would then show up in the dropdown list.
So I am soliciting tips on how I might most easily implement either of the above functionalities. I'd rather not have to build a "Save Your Colors" module. (Does that already exist?)
Thanks...
Recent comments
Perhaps, these latest lines of random test failures can be considered in the meeting too?
December 18th, 2025 - Weekly Meetings
There are some test failures in the user module after merging in the latest commits. Randomly, only in one PHP version - and always a different one. See also this Zulip...
December 18th, 2025 - Weekly Meetings
Two issues would benefit from testing and code reviews; they've been around for a while and no takers. It would be a shame for these to miss the next releases. View Table Headings...
December 18th, 2025 - Weekly Meetings
For the dev meeting: Progress all over the place. Nine pull requests are currently marked RTBC - time to consider merging? Bug fixes mostly, and not too complex. Issue #6987: There's...
December 18th, 2025 - Weekly Meetings
In a blog post titled "Github Tips and Tricks for Contrib Maintainers", I'd like to see some of the following topics: When is the README sufficient for documentation? When should...
Github Tips and Tricks for Contrib Maintainers