Hey guys, I was wondering how you guys are dealing with cache/optimizations on your development machine, between drupal cache, panels cache, browser cache and other css/js compression settings etc.. I've found it difficult to deal with all of them. I have a feature/module that deal with production settings so i can develop without annoying production settings (css/js compression, drupal cache, theme registry, devel settings among others...) and revert them back on production when the new release is online. Problem is i can't find a way to deal with panels cache. The question is: how can i find a way to disable panels cache easily while on a dev environment ? (using drush cc or emptying the cache with devel is still a pain) How do you guys are doing it ? Thank you !
On 9/17/2010 7:49 AM, blouhwtf wrote:
Hey guys,
I was wondering how you guys are dealing with cache/optimizations on your development machine, between drupal cache, panels cache, browser cache and other css/js compression settings etc.. I've found it difficult to deal with all of them. I have a feature/module that deal with production settings so i can develop without annoying production settings (css/js compression, drupal cache, theme registry, devel settings among others...) and revert them back on production when the new release is online. Problem is i can't find a way to deal with panels cache.
The question is: how can i find a way to disable panels cache easily while on a dev environment ? (using drush cc or emptying the cache with devel is still a pain) How do you guys are doing it ?
Thank you !
The best way to easily disable the Panels cache would be to put some kind of flag in the cache.inc plugin itself, probably. This might be a good patch to provide to add a devel.module setting to disable Panels caching.
On Fri, 2010-09-17 at 17:49 +0300, blouhwtf wrote:
I was wondering how you guys are dealing with cache/optimizations on your development machine, between drupal cache, panels cache, browser cache and other css/js compression settings etc.. I've found it difficult to deal with all of them.
I usually use clear_cache_all() function to clear specific cache I'm working all. Not using cache at all is a waste of time, especially regarding menus, that can grow in some projects. So, when I work on forms, I put this: cache_clear_all(NULL, 'cache_form'); Just after bootstrap in index.php. Otherwise, 'drush cc all'.
[cache_form side issue] Just a word of warning: cache_form is not actually a cache table, even though it accidentally took on the use of the cache table. There is an RTBC issue in D7 to rename the cache_form table to form_state (which is what it's about). See http://drupal.org/node/512026. cache_form should not be cleared as if it were a re-creatable cache. -Randy On Fri, Sep 17, 2010 at 7:48 PM, Nikola Kotur <kotnick@gmail.com> wrote:
On Fri, 2010-09-17 at 17:49 +0300, blouhwtf wrote:
I was wondering how you guys are dealing with cache/optimizations on your development machine, between drupal cache, panels cache, browser cache and other css/js compression settings etc.. I've found it difficult to deal with all of them.
I usually use clear_cache_all() function to clear specific cache I'm working all. Not using cache at all is a waste of time, especially regarding menus, that can grow in some projects.
So, when I work on forms, I put this:
cache_clear_all(NULL, 'cache_form');
Just after bootstrap in index.php.
Otherwise, 'drush cc all'.
-- Randy Fay Drupal Module and Site Development randy@randyfay.com +1 970.462.7450
participants (4)
-
blouhwtf -
Earl Miles -
Nikola Kotur -
Randy Fay