Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-10274

Wrong locale/fallbackLocale logic in CategoryContentWrapper leads to unavailable alternate locale content

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Trunk
    • 16.11.05, 17.12.01, 18.12.01
    • product
    • None

    Description

      The current logic in CategoryContentWrapper tries to find a ProductCategoryContent related Content object for the session locale or configured fallback locale. This could make sense, if there are multiple ProductCategoryContent entries of same type but different languages. However the standard model to define alternate locale contents is to have ONE ProductCategoryContent and different locale contents assigned to it via a ContentAssocs. This is exactly what the ContentWorker.renderContentAsText logic resolves for the caller putting in the parent contentId, as it it used in the ProductContentWrapper and others.

      Therefore the content persistet correctly as alternate locale content is currently not accessible via CategoryContentWrapper!

      FIX: Remove wrong locale/fallbackLocale logic which ignores the correct alternate locale content model to let CategoryContentWorker work like ProductContentWrapper with alternate locale content logic in ContentWorker.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mbrohl Michael Brohl
            mbecker Martin Becker
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment