Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.1
    • Fix Version/s: 5.1.0
    • Component/s: None
    • Labels:
      None

      Description

      Previously, our load order was portal.properties, then usually portal-ext.properties, and then possibly portal-liferay.com.properties. The latter caused a lot of confusion because the property may not be read if an overriding property is stored in the database (which is also scoped per company). Therefore, to simplify the cases, it can only be loaded per company via the gui (which is persisted in the database). If this causes a lot of problems, we can easily add it back.

      This change was added as part of LEP-6389.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support