What each function does:
?flush: (just existing, the =1 isn’t needed)
- Rebuilds the manifests (YAML, statics, classes, templates)
- Flushes the current page’s templates
- Regenerates images on the current page
?flush=all:
- Removes all cached templates *if the page uses SSViewer*. This means it doesn’t happen under dev/build (and never has)
dev/build:
- Rebuilds the database.
- Used to also rebuild the manifests. If your ?flush redirects you to something with a flush token in the URL, this no longer happens.
For template changes, you almost never need to flush as of 3.0. With 2.4, you need to flush if changing an include. As such, you also almost never need to use ?flush=all.
For config changes (either YAML or static based in 3.1) you need to flush.
For adding in classes or templates, you need to flush like normal.
For database changes, you tend to need to dev/build AND flush as then config needs to be flushed before changes get picked up.
>--
>You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to
silverstripe-d...@googlegroups.com.
>To post to this group, send email to
silverst...@googlegroups.com.
>Visit this group at
http://groups.google.com/group/silverstripe-dev.
>For more options, visit
https://groups.google.com/groups/opt_out.
>
---
Simon Welsh
Admin of
http://simon.geek.nz/