[support] Site in development:

[sander-martijn]

My question is why would you want to or need to?  I have caching and 
aggregation of css files both disbaled under admin>performance until I 
am ready to go live and have had no problems whatsoever with caching of 
content or template files as I am developing.  A lot less risky than 
putting that code in and risking forgetting about it and going live with 
it.  I would only use a call like that on a one off basis if I was 
having a problem in that place that I could not fix through settings and 
would take it out again as soon as possible.  Those are the types of 
things you forget about, go live with and then wonder why the site is so 
slow.

.s


J-P Stacey wrote:
> Hi,
>
> On a site that's in development (where e.g. theme files are being moved 
> around a lot, and in fact database contents are being copied from one 
> development system to another with their system tables intact and hence 
> incorrect on the new system), is there any reason *not* to call 
> module_rebuild_cache and system_theme_data on every page (apart from 
> performance)?
>
> I notice that the former uses UPDATEs on the system table in the database, 
> whereas the latter uses DELETE/INSERTs to flush out all themes before 
> re-INSERTing them.
>
> Cheers,
> J-P
>