Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-22260

As legacy User I want node assignment remote id to be kept on publish

    XMLWordPrintable

Details

    • Ventoux Sprint 5, Ventoux Sprint 6
    • 2

    Description

      Given I want to use workflows my content is not necessarily published straight away, and in case of approval workflows my editor might change the locations of my draft before publishing it.

      Technical implications:

      • For Legacy storage engine
        • eznode_assignment.priority column is missing (can be set to default: 0 to make sure legacy kernel does not need to be updated)
        • eznode_assignment.remote_id should be same format ( was more or less done in #EZP-20089)
      • For legacy kernel & LegacyStorageEngine:
        • remote_id needs to be copied to ezcontentobject_tree on publishing by operations (needed by ezcontentstaging, contact person gaetano.giunta@ez.no)

      For reference here is old version of legacy schema (note: at least eznode_assignment.remote_id has become varchar in between):
      http://doc.ez.no/schemadoc/tables/ezcontentobject_tree.html
      http://doc.ez.no/schemadoc/tables/eznode_assignment.html

      Attachments

        Activity

          People

            Unassigned Unassigned
            andre.romcke-obsolete@ez.no André Rømcke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2 days Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days, 7 hours, 30 minutes
                3d 7h 30m