We're having a problem with LinguaPlone 2.4 on Plone 3.2. Our site has a few custom content types for farmer profiles.
A content editor can add a grower in the default language (en) and then translate it into the other supported languages (fr & de).
Most of the time this works just fine. However, sometimes the "translate into" action moves the English grower into the (French/German) grower folder, removing it from its original location. The english content item now appears in the folder for the other language, and is identified as a frensh/german content-item.
This issue appears to be independent of browser as our users are experiencing it in both Firefox and IE. It also appears to be independent of CacheFu/Varnish as it persists when folks use a subdomain which bypasses Varnish.
Has anyone seen similar behaviors form LinguaPlone? Suggestions for how to go about tracking this down?
thanks
--
David Siedband
------------------------------------------------------------------------------
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users