completed How To Build a Multilingual Site Using The Site Builder?

Hi Brian,

I am still stuck on this issue. I have already created 4 languages in the system. It seems that it is not still possible to build a Multilingual Site using the Site Builder in the Elastic template.

I have posted about the same subject here:

https://www.jamroom.net/the-jamroom-network/forum/using-jamroom/34639/how-to-build-a-jrelastic-multilingual-based-site-using-the-site-builder

Six months later, there seems to be no solution.

Please, providing me with a comprehensive step by step guide on "how to Build a Multilingual Site using the Site Builder" in the Elastic Template.

Thanks in advance.
updated by @pch: 09/14/16 02:53:43PM

Unfortunately there is no "comprehensive step by step guide on "how to Build a Multilingual Site using the Site Builder" in the Elastic Template" - I'm sorry to say.

You COULD do it with custom templates using the HTML Editor widget - i.e.
but that's really just using Site Builder for templates - you might as well use real templates.

Part of the problem here is that at this time there's no easy way to add custom language strings into the system that do NOT belong to a module or skin, and very, very few of our users have had a need for that. I'd like to tell you it's on it's way, but it's not, and I'm not sure when it will be supported.

If you need multilingual right now, you'd want to just use templates and not site builder - that's 100% doable right now. I know that's not what you're looking for though.

Sorry!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Have just re-read the linked post:

https://www.jamroom.net/the-jamroom-network/forum/using-jamroom/34639/how-to-build-a-jrelastic-multilingual-based-site-using-the-site-builder

and we recommend there as well that you NOT use Site Builder, and instead use templates. 6 months later I am going to continue to recommend that approach as it's already supported.

Just an FYI.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Well, Brian, once again I just feel sad. Anyway thanks for the reply.

Now, I would like to use the Elastic template for my multilingual site. I have read the other topic (see link in the first post of this topic) and I have already done some of the step. Also i have read the documentation. Well, it 's really frustrating.

Are all pages in the Elastic Template (timeline, audio, video, blog, playlist, etc) ready for a multilingual site or do I have to add the the {jrCore_lang} code in every single page?

They are already setup - the only time you would need to manually add the jrCore_lang function calls is in custom templates.

https://www.jamroom.net/the-jamroom-network/documentation/development/541/translate-jamroom-into-another-language


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Ok, thanks. Please for God's sake, do not close this topic yet. I will give it a try and give some Feedback here. Thanks

We don't manually close topics unless they are duplicates...


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Part of the problem is we're not sure on the best way to do it. There are many different ways that this problem could be approached.

One way would be to use site builder for the structure, but instead of using the ITEM LIST widget, use the TEMPLATE CODE widget

Then type the language strings directly into the separate templates. Is that better/worse than brian's idea of using {jrCore_lang ??????}. We don't know, its just different.

Each will have their advantages and dis-advantages.

Then there's the idea of using different site urls for each language:
your-site.com/en/??????
your-site.com/ja/??????

or different domains running off of the same database
your-site-en.com/??????
your-site-ja.com/??????

Thats also another valid way to approach the situation.

For the content, do you have one database for the english content and another for the other language content, or two separate sites. Either way would work but the work involved in maintaining them would be different.

The end result is: Yes it can be done. No there is no single way that is the correct way. There will be no step by step until someone builds it, then documents how they built it. Even then, that will still only be the documentation on one way to approach the problem.

Hi Michael,

Thanks for your efforts to help but I have just given up on the site builder. It isn't ready for a multilingual system yet. I am building my multilingual site manually using template.

Thanks.