Uploaded image for project: 'Content Importer'
  1. Content Importer
  2. MGNLCI-13

Safety mechanism to prevent accidentally overwriting content

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    Description

      When one approves/runs the import task in the pulse, the content will overwrite any existing content which shares an UUID on the content in the import file without warning.

      This can be problematic with the common use case of sample content.

      The system should protect the developer from accidental overwriting. To be determined is how. Maybe a simple warning / confirmation box if the UUID exists.

      Scenario:
      (I acknowledge that this scenario involves a lot of mistakes from a developer.)

      • A developer may import sample content such as sample pages. They may use those pages as a starting point and rename them.
      • The import could be run again, if for example a light module was removed and then re-added to an import directory. (this could be on purpose if the developer wants to see the original un-edited samples again.)
      • Developer approves the import in the pulse - they do not expect their page to be overwritten because they have renamed the page.
      • Page is overwritten. No way to get the page back, unless it was versioned.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              czimmermann Christopher Zimmermann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD