Details

    • Similar Issues:
      Show 5 results 

      Description

      The Journal portlet provides a very interesting functionality of storing structured content and then applying templates to it. This functionality is useful also outside the world of web content and due to that it's a common pattern to use its backend to build 3rd party applications on top of it. The downside of this, is that the data stored in JournalArticle by those applications also appear as if they were web content.

      The solution is to apply the className-classPK pattern to separate the JournalArticle entries that are for Web Content (classNameId=0 for example) from those that have other purposes.

        Issue Links

          Activity

          Hide
          Jonas Yuan added a comment -

          vote +1

          Show
          Jonas Yuan added a comment - vote +1
          Hide
          Juan Fernández added a comment -

          This improvement will be used for LPS-16635 implementation

          Show
          Juan Fernández added a comment - This improvement will be used for LPS-16635 implementation
          Hide
          Alfred Pucay added a comment -

          rolled back due to exposing different issue

          Show
          Alfred Pucay added a comment - rolled back due to exposing different issue
          Hide
          Alfred Pucay added a comment -

          Sorry I reopened the wrong issue!

          Apologies.

          Show
          Alfred Pucay added a comment - Sorry I reopened the wrong issue! Apologies.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 45 weeks, 5 days ago

                Development

                  Structure Helper Panel