[cache_form side issue]<br>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 <a href="http://drupal.org/node/512026">http://drupal.org/node/512026</a>.<br>
<br>cache_form should not be cleared as if it were a re-creatable cache.<br><br>-Randy<br><br><div class="gmail_quote">On Fri, Sep 17, 2010 at 7:48 PM, Nikola Kotur <span dir="ltr"><<a href="mailto:kotnick@gmail.com">kotnick@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="im">
On Fri, 2010-09-17 at 17:49 +0300, blouhwtf wrote:
<blockquote type="CITE">
<br>
</blockquote>
<blockquote type="CITE">
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.
</blockquote>
<br></div>
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.<br>
<br>
So, when I work on forms, I put this:<br>
<br>
cache_clear_all(NULL, 'cache_form');<br>
<br>
Just after bootstrap in index.php.<br>
<br>
Otherwise, 'drush cc all'.<br>
<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Randy Fay<br>Drupal Module and Site Development<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>