When should i use vBO "flush cache"?

[Vitaly]

Sinse i constantly develop & deploy new mods to production site, should i use "flush cache" after ACP operations? Such as:

- install new mod
- change settings
- edit phrases
- change TMS rules
and so on...

 

[Deceptor]

Flushing in most places is automated, you can find the current actions that will kill the flush (or do a full flush) in class_vboptimise.php:

		// ACP Actions to flush cache on
		$actions = array(
			'updatetemplate',
			'inserttemplate',
			'productimport',
			'rebuild',
			'insertstyle',
			'update',
			'clear_cache',
			'purgecache',
			'displayorder',
			'savestylevar',
			'insert',
			'import',
			'replace',
			'kill',
			'productsave',
			'productdependancy',
			'productcode',
			'productdisable',
			'productenable',
			'productkill',
			'dooptions',
		);

		// ACP actions to kill whole cache as a failsafe
		$full = array(
			'clear_cache',
			'purgecache',
		);

For the most part, this handles nearly all places but there are some still pending (like stylevar replacements) - we'll be expanding the list for the RC1 release of v3 - meanwhile you're free to expand the lists yourself for any actions you find that don't flush the cache

 

[Vitaly]

Thanks, that's ok.

 

[hornstar]

Will the flush be working automatically with 3.8 in the next update?

 

[Deceptor]

The rules defined above apply to 3.8 too, is there any specific action that isn't flushing cache for you hornstar?