Hello, first let me say that AdaptiveThemes are, in my option, the fastest and best documented base theme available, period. I'm a hardcore web dev with 15 years of HTML under my belt. I started working with Drupal almost 2 years ago, and for the past year I've been trying to settle in to a Drupal base theme with SASS and mobile, etc. I was tired of reinventing the wheel, then I remembered hearing Jeff Burnz on the Modules Unraveled podcast talking about all the goodness in at-7-3.x. Long story short - AT 7-3.x is the best base theme and starting point for serious developer/themers who want to get-stuff-done, and get a best-practices HTML/CSS theme done quickly. The code documentation and organization in outstanding, and with the addition of the SASS/config.rb, AT is the best choice for me moving forward. Excellent work being done here, thanks for all you do! On to my question.... :)
Question: in the theme settings admin/appearance/settings/mysubtheme, under "Unset Contrib Module CSS" I select [x] Unset All. The boxes are all checked then I save the settings. However, when the page is refreshed, many of the check boxes have become unchecked. I'm using the AT subtheme with Panopoly, and when I unset all the things in both Contrib CSS and Libraries CSS, then save, nearly all the check boxes are unset, and still loading in the front end. Any idea why these settings aren't saving?
Steps to reproduce:
- Enable Panoply AT Subtheme
- Enable AT Extensions (save)
- Enable "Unset CSS Files" extension (save)
- check to [x] Unset All Libraries CSS
- check to [x] Unset All Contrib Module CSS (save)
As I went through these steps, I also checked to Unset all Core CSS, which DID in fact save all the checkboxes as checked. So this appears to be an issue with the Panopoly distribution version of AdaptiveThemes affecting only the Library and Contrib CSS checkboxes.... I'm not sure what to do at this point, should I open a bug report in the Panopoly issue queue?
Thank you!
--Tony
Comments
Comment #1
dshields commentedAny progress on this? I'm finding the very same thing. Certain css files won't save as "unset". My problem occurs both in panopoly and on a core drupal install using adaptivetheme..
Comment #2
rowbotony commented@dshields, I have since found a better way to unset such assets regardless of the theme you are using. Have a look at this blog post:
Death of a Themer
http://www.codeenigma.com/blog/drupal-theming-death-of-a-themer
I've settled on the Selective Assets module for my sites. It is a well-coded and stable module, but it's still a sandbox project so you'll have to download it with git.
I would like to know why this is an issue with AdaptiveTheme and/or Panopoly, but I've never been able to figure out the problem, so I'm sticking with the Selective Assets module for the foreseeable future.
http://drupal.org/sandbox/adenot/1711614
Comment #3
rowbotony commentedChanged the title to be more descriptive. I'd say this is a bug, but we'll leave it as a support request until the developer can review and determine if this is an AdaptiveTheme issue, or a Panopoly specific issue, in which case we can move it to the Panopoly issue queue.
Comment #4
dshields commentedI'm pretty sure this is an AdaptiveTheme issue and that this is the appropriate place for this discussion.
Comment #5
Jeff Burnz commentedOK, better take a look, sounds like something may have broken along the way.
Comment #6
dshields commentedThanks Jeff!
Comment #7
qayoub commentedAny solution ???