Details

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

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

                  Subcomponents