Jump to:

23477 Posts in 18941 Topics by 2878 members

General Questions

SilverStripe Forums » General Questions » Best practice: translatable DataObjects

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Page: 1
Go to End
Author Topic: 596 Views
  • Blackboard
    Community Member
    1 Post

    Best practice: translatable DataObjects Link to this post


    I've been testing the translatable module lately, and looking for a way to handle large amount of dataObjects, and beeing able to make a translation of every dataObject in e.g. an DataObjectManager list. The way the extension works, it only gives the dataObject an additional textfield where locale has to be written manually. I don't think this is a good idea, telling an average admin to handle large datasets this way, as there is no relation to other languages. Is there a way to extend the translatable functionality to dataObjects, giving every dataObject the translate-tab. This way admin can easily see if this dataObject has been translated into other languages, and do so if needed.

    How does large sites handle dataobject in different languages? Do I really need to have duplicates of lets say every document in an dataObjectMangager in both/all languages? I know the files exists, but do I really need to create a whole new dataObject having no relation to the default locale?

    Hope someone have experienced similar challanges, and found a good solution.

Page: 1
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.