Under normal use, not triggering node_save() works fine. However, when using Entity Cache, this presents quite a problem, as the entity cache is not cleared. Similarly, when using Cache Actions to manage the full calendar view cache, there is no way to set up a rule (w/o custom code) to properly clear the cache.
I'm not sure the best approach to take on the entity cache issue. For the rules issue, a patch could be provided to that module to trigger off of field_attach_presave, instead of node_save, since node_save calls that function.
Comments
Comment #1
tim.plunkettI'm going to call this works as designed. Sorry, but I'd like to keep it generic. I'm surprised a module called *Entity* Cache relies on node_save like that.
Comment #2
tim.plunkettOkay, berdir talked me into adding this.
I want to stab hook_entity_update for switching the params around. So so so so stupid.
Comment #3
tim.plunkettClosing as a dupe of #1457868: Work with entitycache