[ https://issues.apache.org/jira/browse/OFBIZ-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395298#comment-16395298 ]
Martin Becker commented on OFBIZ-10274: --------------------------------------- OFBIZ-6262 introduced this bug because of a misunderstanding of the content locale model... > Wrong locale/fallbackLocale logic in CategoryContentWrapper leads to > unavailable alternate locale content > --------------------------------------------------------------------------------------------------------- > > Key: OFBIZ-10274 > URL: https://issues.apache.org/jira/browse/OFBIZ-10274 > Project: OFBiz > Issue Type: Bug > Components: product > Affects Versions: Trunk > Reporter: Martin Becker > Priority: Major > Attachments: OFBIZ-10274_CategoryContentWrapper_alternateLocale.patch > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)