Item10582: automatic deletion of destination directory in file output breaks per-page or per-sub-web publishing
Priority: Urgent
Current State: Closed
Released In: n/a
Target Release: n/a
Version 2.20.
The new version of the
file
backend automatically deletes the destination directory prior to starting a new publishing run. This breaks two existing working scenarios:
- Currently the plugin does not recursively handle webs (as far as I can tell), so the only way to publish a nested web hierarchy is to publish each sub-web individually.
- Per-page publishing
In both cases existing, unrelated, content is scrubbed.
I can see the need for purging the destination to remove orphaned content, but I think the mechanism either needs to be much more sophisticated or much simpler (e.g. an explicit purge operation). I'd err on the side of simplicity.
Thanks,
Diab
--
DiabJerius - 31 Mar 2011
The output options gives you the controll needed to keep published output separate, I'm not rushing into this because I don't have time to do a proper fix. Please go ahead if you have a better idea....
--
CrawfordCurrie - 25 May 2011
I removed that. Added re-gathering of previously generated input for index and sitemap. Purge is manual.
--
Main.CrawfordCurrie - 20 Apr 2017 - 17:58