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
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists