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

Storing a draft with a bad object relation link should not create an entry in ezcontentobject_link

    Details

      Description

      If you create an ezobject:// link with a bad object ID and store the draft, you get properly warned that the object ID does not exist.
      However, from that point forward, an entry in ezcontentobject_link has been created that will never go away.

      (It will, if you discard the draft at this point. But if you remove the link and publish the draft, the bad entry stays in the table. Each new published object version adds a new bad entry. Removing the object (not move to trash) removes the bad entry. - Gunnstein)

      This will cause problems moving forward – you will get exceptions in the new stack if you use $repository->getContentService()->loadRelations().
      In those cases, unless you manually delete the entry in ezcontentobject_link, a content editor will never be able to fix the problem.

        Activity

        Eduardo Fernandes (Inactive) created issue -
        Eduardo Fernandes (Inactive) made changes -
        Field Original Value New Value
        Description If you create an ezobject:// link with a bad object ID and store the draft, you get properly warned that the object ID does not exist. However, from that point forward, an entry in ezcontentobject_link has been created that will never go away.

        This will cause problems moving forward -- you will get exceptions in the new stack if you use $repository->getContentService()->loadRelations(). In those cases, unless you manually delete the entry in ezcontentobject_link, a content editor will never be able to fix the problem.
        If you create an ezobject:// link with a bad object ID and store the draft, you get properly warned that the object ID does not exist.
        However, from that point forward, an entry in ezcontentobject_link has been created that will never go away.

        This will cause problems moving forward -- you will get exceptions in the new stack if you use $repository->getContentService()->loadRelations().
        In those cases, unless you manually delete the entry in ezcontentobject_link, a content editor will never be able to fix the problem.
        Eduardo Fernandes (Inactive) made changes -
        Status Open [ 1 ] Confirmed [ 10037 ]
        Paulo Lopes (Inactive) made changes -
        Status Confirmed [ 10037 ] InputQ [ 10001 ]
        Damien Pobel (Inactive) made changes -
        Assignee Gunnstein Lye [ gunnstein.lye@ez.no ]
        Gunnstein Lye made changes -
        Status InputQ [ 10001 ] Development [ 3 ]
        Gunnstein Lye made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 30 minutes [ 1800 ]
        Worklog Id 51476 [ 51476 ]
        Gunnstein Lye made changes -
        Description If you create an ezobject:// link with a bad object ID and store the draft, you get properly warned that the object ID does not exist.
        However, from that point forward, an entry in ezcontentobject_link has been created that will never go away.

        This will cause problems moving forward -- you will get exceptions in the new stack if you use $repository->getContentService()->loadRelations().
        In those cases, unless you manually delete the entry in ezcontentobject_link, a content editor will never be able to fix the problem.
        If you create an ezobject:// link with a bad object ID and store the draft, you get properly warned that the object ID does not exist.
        However, from that point forward, an entry in ezcontentobject_link has been created that will never go away.

        (It will, if you discard the draft at this point. But if you remove the link and publish the draft, the bad entry stays in the table. Each new published object version adds a new bad entry. Removing the object (not move to trash) removes the bad entry. - Gunnstein)

        This will cause problems moving forward -- you will get exceptions in the new stack if you use $repository->getContentService()->loadRelations().
        In those cases, unless you manually delete the entry in ezcontentobject_link, a content editor will never be able to fix the problem.
        Gunnstein Lye made changes -
        Status Development [ 3 ] Development review [ 10006 ]
        Gunnstein Lye made changes -
        Status Development review [ 10006 ] Development Review done [ 10028 ]
        Gunnstein Lye made changes -
        Fix Version/s 5.1 Maintenance [ 12301 ]
        Fix Version/s 5.2 Maintenance [ 12782 ]
        Fix Version/s 5.3.4 [ 13879 ]
        Gunnstein Lye made changes -
        Affects Version/s 5.1 [ 11280 ]
        Gunnstein Lye made changes -
        Status Development Review done [ 10028 ] Documentation done [ 10011 ]
        Paulo Nunes (Inactive) made changes -
        Status Documentation done [ 10011 ] QA [ 10008 ]
        Assignee Gunnstein Lye [ gunnstein.lye@ez.no ] Paulo Nunes [ paulo.nunes@ez.no ]
        Gunnstein Lye made changes -
        Time Spent 30 minutes [ 1800 ] 3 hours, 30 minutes [ 12600 ]
        Worklog Id 51482 [ 51482 ]
        Gunnstein Lye made changes -
        Affects Version/s 5.4-dev [ 13485 ]
        Affects Version/s 5.4 [ 13180 ]
        Gunnstein Lye made changes -
        Fix Version/s 5.4 [ 13180 ]
        Paulo Nunes (Inactive) made changes -
        Assignee Paulo Nunes [ paulo.nunes@ez.no ]
        Status QA [ 10008 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        André Rømcke made changes -
        Workflow eZ Engineering Scrumban Workflow [ 64956 ] EZ* Development Workflow [ 85456 ]
        Alex Schuster made changes -
        Workflow EZ* Development Workflow [ 85456 ] EZEE Development Workflow [ 124287 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Eduardo Fernandes (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 3 hours, 30 minutes
              3h 30m