Posted by Kaloyan Petrov on July 22, 2012 at 3:23pm
10 followers
Jump to:
| Project: | AdaptiveTheme |
| Version: | 7.x-3.x-dev |
| Component: | Module Support |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hello,
Is there a way to export / save / reset theme settings (with custom module) the way that Omega + Omega Tools or Arctica + Nitro does? Let's say I've made some changes and want to export them to have as a reference or future reusing.
Right now theme settings only go in DB, right?
Thanks again!
Kaloyan
Comments
#1
There is a copy in the generated files directory, the same dir as the CSS files, say:
files/adaptivetheme/theme_name_files
You should upgrade to the dev version, there are some changes and a fix for some things in the generated info file.
#2
I've found these files, but I'm wondering if there's a way to version control these so that when I'm working on a team, we can be sure we're all using the same layout. Any suggestions?
#3
Yes, you can control where these are saved - under the CSS settings you can choose to save them in your themes directory, so they can come under version control. If you convert the saved info file (which is saved as a txt file to prevent Drupal thinking you have another theme installed), then that will be version controlled also - that should make migration pretty strait forward between systems.
#4
Sweet! Thanks Jeff!
#5
So over the weekend and for a bit this morning, I've tested out at_panels_everywhere, as a possibly replacement for our current standard (omega with custom panels for layouts). While there is a lot about at_panels_everywhere that I liked, the one fundamental thing I didn't like was that there is no way to revert to the theme settings in the info file. Maybe I just got comfortable with the revert functionality provided by Omega's omega_tools companion module, and maybe there is a way to do this with just Drupal core (though I don't know of any).
Is there a solution to make reverting changes on a dev/test/qa/prod server to match the code changes from my local server a one-click or single-command?
I understand that the configuration can be configured to export its contents to sites/all/themes/at_panels_everywhere/generated_files/at_panels_everywhere_settings.info.txt, and then in theory, you could copy that up to the root of the theme, and change the extension, but I'm just not sure how to forcefully make Drupal *revert* to that file's contents.
#6
There is a module you can use to completely uninstall a theme (pretty much the same thing as a reset to default settings) http://drupal.org/sandbox/jmburnz/1685382 which you can grab from GIT, or I can actually make a release if you can't do that.
Clone the 7.x-1.x branch, enable the module and in the Appearance section you will see a new tab "Nukem". This allows you to delete any themes persistent variables such as the database stored theme settings - there is no granularity here, its all or nothing.
After you have nuked your settings then go back to your themes settings page, reload it and save the settings - these will be the defaults from the info file (since all database stored settings are now smoked).
I made this module for dev purposes, since Drupal 7 lost the "reset to defaults" setting we all loved in Drupal 6.
#7
Drush support for reverting to the .info setting (similarly to doing a drush fr) would be extremely useful!