Edit conflicts during archiving are not handled gracefully

[roysmith]

See this edit

I had just left a comment on the SPI and then immediately archived it. SPI helper put up an error about an edit conflict (dirty page cache, I guess), so I just did it again. That ended up archiving it twice. Not fatal, but if there's an easy way to make the two operations atomic, that would be nice.

[Dreamy-Jazz]

There has been several times that SPI pages have their cache not re-generated even after edits. I suspect that, because SPI helper reads from the page content, in general when the edits do not show up to the user SPI helper can only read from the content it gets and attempting to detect conflicts would be difficult.

• One solution is to purge the page every time the tool is loaded, which seems a little excessive.
• Another solution is for archiving only and attempts to detect whether the latest archived section has the same content as the section being archived. If it does it warns via an alert box which should allow continuing if that's the intended action.

[roysmith]

I like the second idea (checking if the archive already has the same content)