1347 Posts in 439 Topics by 514 members
|Go to End|
21 May 2013 at 9:14pm
Hi, sorry if this is a silly question (I'm new to Silverstripe, working on my first site today), but is there anyway of disabling the need for the query string`?flush=1` (`?flush=all`) upon changing a template file?
I can understand the need for caching while a site is in production, but during development, when you could be making lots of small changes to the template files, it would get very annoying to have to append the query string to every url I access on the site.
..or am I missing something?
22 May 2013 at 9:58pm
Though in development it does add several seconds to page load time, which, if you're working on CSS and other stuff can prove annoying. Something like $_GET['flush'] = 1 in your _config.php or _ss_environment might work.
22 May 2013 at 10:04pm
I might have been a little bit preemptive in my posting.
Having read the tutorials on this site, it was suggesting that you need to run the `?flush=1` after each and every template change because of the caching...
... however, having started building a site using SilverStripe, I've found that I've not yet needed to run the flush command, as the changes are reflecting straight away. I'm not sure why this is, I'm just glad it's working.
The only other thing I've done is created a silverstripe-cache directory, I don't know if this would have something to do with it?
In any case, right now I'm happy - I just hope that I've not somehow disabled the caching for when I come to putting the site online.
|Go to Top|