Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5742

JCR Export: creates dangerous file-length

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Neutral Neutral
    • None
    • None
    • build
    • None

      While working with the module structure we keep running into problems when exporting jcr nodes. The current export functionality relies heavily on the combination of filename and sv:node content to backup and restore information. This, in turn, stores the full jcr path as part of the exported filename, which can lead to various errors with different OS (windows for instance has a 255 character filename-length limit).

      This is only a mild annoyance whenever you are able to export from a previous subnode (ie, the module as a whole), but turns into a real problem quickly whenever you have to add a node entry in a referenced module (e.g: when adding an available component to a page from another module). Since this is a true limitation, it would be great if the current import/export methods could be overhauled. Since storing the path as part of the xml dom, it would not necessarily seem to be a huge problem to implement.

        Acceptance criteria

              Unassigned Unassigned
              madppiper Paul Piper
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:

                  Task DoD