[ 
http://issues.apache.org/jira/browse/OFBIZ-161?page=comments#action_12429460 ] 
            
Jacopo Cappellato commented on OFBIZ-161:
-----------------------------------------

I think that this link can be useful to help understand the whole picture:

http://ofbizwiki.go-integral.com/Wiki.jsp?page=LocalizedProductDescriptions



> Fix contentwrapper locale rendering bug
> ---------------------------------------
>
>                 Key: OFBIZ-161
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-161
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Bug
>          Components: product
>            Reporter: Si Chen
>         Attachments: content-wrapper-locale.patch
>
>
> Wanted to check with everybody before committing this to make sure I'm not 
> going down the wrong way.
> It seems to me that you should be able to create content for products and 
> categories in different languages in the Catalog Manager by clicking on the 
> [Content] tab of Product or Category, then click on [Prepare Create] for say, 
> Description or Long Description.  Then you should be able to enter a locale, 
> and that content should be the one for that language locale.  However, the 
> Product and Category ContentWrappers were not rendering them.
> After a little digging, it seemed to me the problem was that they were both 
> looking for the ProductContent and ProductCategoryContent entities, then 
> getting the first and most recent record of each as the Content to render.  
> There was no filtering of locale of the Content entity--hence no way to 
> control which locale was being rendered.  
> I made this little patch to change the lookup to ProductContentAndInfo and 
> the comparable Categoryentity.  It  fixed it for me, so now I can enter 
> English as en_US and French as fr_FR, and the content for those languages 
> would render separately.
> However, one problem is that this content lookup is very strict - if you 
> create your content as en, it will not find it as en_US, or vice versa.  
> Is this the right way to use the content manager?
> Is there a way to make it so that en_ will work for en_US--other than some 
> fancier searching technique?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to