So I'm not sure if there's something I've not setup something correctly but I assume I'm making a feature request that, again, may not be in the scope of this module. Every time a user chooses a different color I have to flush the cache for them to see any change. Of course, this is because I have css aggregation on. Can you envision a way around this?

Comments

aacraig’s picture

aacraig commented
Version: 6.x-1.x-dev » 6.x-1.2

Yes, this is an issue. I am looking into how to resolve this, without clearing the entire css cache, if that's possible. I've added this to the roadmap, and will get to it ASAP.

pribeh’s picture

pribeh commented

Wonderful!

pribeh’s picture

pribeh commented

Hi, thanks so much for your hard work on this module. Any update on this? This is the last hurdle before I go live with this module - which is truly amazing :)

aacraig’s picture

aacraig commented

I've been trying to push out an update once a month, and I may be able to respect that schedule this month as well. Worst case scenario is that an update will come in early November, and should include this fix.

pribeh’s picture

pribeh commented

Sorry, just wondering if you got to this yet. Don't mean to be a bug. Even just a patch would be great if you've gotten to it already otherwise no worries.

aacraig’s picture

aacraig commented
Status: Active » Closed (fixed)

This has been fixed in 6.x-1.6.

pribeh’s picture

pribeh commented

Wow, this is amazing. Thank you so much. Another question though, is there a way to force the browser to reload/refresh upon user submission of the theme_hue/configure form? This could be made into another request I suppose.

aacraig’s picture

aacraig commented

The browser should load this file from the server when it is recreated using the same mechanism that other css and script files are reloaded in Drupal. On FF and Chromium I immediately see changes to the stylesheet after saving, without having to shift + reload.