Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-52278

Structures without unique 'name' fields are not editable after upgrade from 6.1 to 6.2 SP6+

    Details

      Description

      After upgrading from 6.1 to 6.2 SP6+, there are issues with structures that have a hierarchy where the children elements have the same names as the parent elements or other children elements. (There was a bug in 6.1 that allowed children elements to have the same names as parent and other child elements. This should not have been possible to do)

      -When editing a web content that uses one of these structures, the edit fields are missing/out of order.
      -These structures cannot be edited (such as adding another field) due to the error "Please enter unique metadata field names (including field names inherited from the parent)."
      -Renaming the fields to be unique so that the previous error is not encountered will either cause a loss of data in the web content that references the fields, or will leave the original field in the content and add a new field. (This could be part of a workaround as you can just copy the content from the original field to the new field, and then reference the new field in the template and the original will be ignored)

      Steps to Reproduce

      1. In 6.1, create a structure, template, and web content where the structure has duplicate field names. For example:
        Mother (text type)
        -Age (text type)
        Father (text type)
        -Age (text type)
      2. Upgrade to 6.2 SP6+
      3. Go to Admin > Content
      4. Select web content article. Notice fields do not display correctly (Or an ArrayIndexOutOfBoundsException if you are on 6.2.10)
      5. Select Manage > Structures
      6. Edit the structure. Add a new text field and save

      Expected Result
      Able to edit and save the structure

      Actual Result
      Unable to make edits due to error

      NOTE:
      The fix for this issue will actually prevent the portal from upgrading. A VerifyException will occur and the problem structures will be identified in the logs.
      See https://www.liferay.com/es/group/customer/kbase/-/knowledge_base/article/52365947 for more information.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  2 years, 39 weeks, 3 days ago

                  Packages

                  Version Package
                  6.2.4 CE GA5
                  6.2.X EE