Configurable export that keeps unapproved drafts

[hjelmevold]

cms2xp exports all approved content, and disregards any unapproved drafts if there already is an approved version. Perhaps there could be an option to also export all unapproved drafts in a separate cms_content export folder, so the cms2xp process ends up generating folders cms_content_draft, cms_content_approved, cms_users and the app folder?

[Bellfalasch]

Summary: Content in CMS with drafts not yet approved, will export only the approved version, dropping any changes from the draft, with CMS2XP. This could potentially be bad, since information is lost.

[aro]

The reason is that XP export format does not supports versions. The dump format does, but then you have to overwrite all the data in XP. The dump format is also more complex to generate.

Options:

• generate 2 exports, one for draft and one for master. This can be a bit tricky
• generate 1 export like now, and add publishing status metadata as a mixin

[sigdestad]

I propose we skip this and write in the CMS2XP doc that only the latest and approved version of content will be exported.

Ok?

[hjelmevold]

won't fix. we only migrate current versions.