2009/1/18 Charlotte Webb charlottethewebb@gmail.com:
On 1/17/09, Thomas Dalton thomas.dalton@gmail.com wrote:
Back in the day, we used to use null edits intentionally to update pages after templates changed. Now we have the job queue to do that for us, but it still works as far as I know.
That's nice I know. This does have its uses but there ought to be some way to do this other than the usual get and post. Maybe some kind of &action=null which handles it internally and skips the pre-save transform and any surprises that may create. Something like &action=purge but more thorough (?).
There's rarely any need now we have the job queue, so I'm not sure it's worth the time it would take to implement such a feature. Null edits work well enough for the few times they are needed.