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

"Allowed content types" seems to be mandatory even when canceling the creation of a content type with a "Relation list" fieldtype

    Details

      Description

      Steps to reproduce

      *Create a content type with a relation list fieldtype (don't choose anything in "Allowed content types")
      *Cancel the creation of the content type

      A message saying that " Form did not validate. Please review errors below. " is presented.
      It's not possible to cancel the creation unless we choose some content type from the list

        Issue Links

          Activity

          Hide
          Damien Pobel (Inactive) added a comment -

          Most likely it's almost the same as EZP-25006

          Show
          Damien Pobel (Inactive) added a comment - Most likely it's almost the same as EZP-25006
          Hide
          Gunnstein Lye added a comment -

          Yes, it's the same I think, but ok to keep them separate until we have confirmed the same fix for both.

          Show
          Gunnstein Lye added a comment - Yes, it's the same I think, but ok to keep them separate until we have confirmed the same fix for both.
          Hide
          Bertrand Dunogier added a comment -

          I'm logging it as a duplicate. We should try to confirm quickly (ping Paulo Nunes).

          Show
          Bertrand Dunogier added a comment - I'm logging it as a duplicate. We should try to confirm quickly (ping Paulo Nunes ).
          Hide
          Bertrand Dunogier added a comment -

          And also duplicate from https://jira.ez.no/browse/EZP-24947.

          Show
          Bertrand Dunogier added a comment - And also duplicate from https://jira.ez.no/browse/EZP-24947 .
          Hide
          Paulo Nunes (Inactive) added a comment -

          Gunnstein Lye], Bertrand Dunogier: The fieldtypes are different, thus the different issues. But the behavior is the same in both.
          If, from development perspective, the root is the same, then one of them might be closed as duplicate.
          Alternatively, when the fix is done, both can be send back to QA with that reference for the fix verification to be done in both of them

          Show
          Paulo Nunes (Inactive) added a comment - Gunnstein Lye ], Bertrand Dunogier : The fieldtypes are different, thus the different issues. But the behavior is the same in both. If, from development perspective, the root is the same, then one of them might be closed as duplicate. Alternatively, when the fix is done, both can be send back to QA with that reference for the fix verification to be done in both of them
          Hide
          Gunnstein Lye added a comment -

          I have closed https://jira.ez.no/browse/EZP-25006 as a duplicate of https://jira.ez.no/browse/EZP-25015
          Most likely this one is too, but I can't verify it at the moment due to another bug which now gives me another error for relation list:

          Could not find 'eZ\Publish\SPI\Persistence\Content\FieldValue\Converter\*' with identifier 'ezxmltext'

          Show
          Gunnstein Lye added a comment - I have closed https://jira.ez.no/browse/EZP-25006 as a duplicate of https://jira.ez.no/browse/EZP-25015 Most likely this one is too, but I can't verify it at the moment due to another bug which now gives me another error for relation list: Could not find 'eZ\Publish\SPI\Persistence\Content\FieldValue\Converter\*' with identifier 'ezxmltext'
          Hide
          Gunnstein Lye added a comment -

          Confirmed, it's a duplicate of https://jira.ez.no/browse/EZP-25015

          Show
          Gunnstein Lye added a comment - Confirmed, it's a duplicate of https://jira.ez.no/browse/EZP-25015

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Nunes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              4 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 - 1 hour, 30 minutes
                1h 30m