Multilanguage site

Hi,

how can I create multilanguage OnePage website?

In english language all is ok, but when I created menu in russian language, ID for anchor is created in russian language and not function correctly.

Thanks

Rudolf

pinochico Probably, the solution provided here by another member could help :

Hi, thanks for reply,

but I think my problem is another (Do You read my post correctly?):

When I create menu in russian or czech language, then anchor has name "ВВОДЯ"
Then I see anchor for section - <div class="section onepage introducing section2" id="Вводя">
And menu has this link url - <a href="#%D0%92%D0%B2%D0%BE%D0%B4%D1%8F">Вводя</a>

So I think this is wrong and menu in russian language after click will not go slowly as english menu.

Now I know - the anchor is created in php from menu name (not alias) and I think this is problem for multilanguage website 🙂

So, how can I change/upgrade/fixed?

Thanks

Rudolf

P.S.
Pls for everybody, as first option before answer - go on website a try yourself 🙂

I was looking for a net and I programed a little bit and

this is help for creating multilanguage web site with template JA OnePage:

Copy function modChrome_onepage from modules.php in location:
templates/ja_onepage/html/modules.php
Rename to
function modChrome_onepage_title
Change code
<h2><span><?php echo $module->title; ?></span></h2>
to
<h2><span><?php echo jText::_($module->title); ?></span></h2>
Module title in administration change to language constant:
for example:
Introducing change to TPL_TITLE_INTRODUCING
This language constant add to language override for frontend:
for example: for EN - language/overrides/en-GB.override.ini
Now this module title is used as anchor, so in menu Introducing You have to add anchor:
index.php?Itemid=435#tpl_title_introducing
For subtitle now add new language constant:
from:
TPL_SUBTITLE_INTRODUCING
to
TPL_SUBTITLE_TPL_TITLE_INTRODUCING
For every module choose Module style from onepage to your new:
onepage_title

ah ok sorry yes a slight misunderstanding here

Thanks for posting your comprehensive solution

It looks like you fully resolved the problem yourself - is this correct?

Thanks again
Paul

Yes 🙂

Thanks again for posting your comprehensive solution

Best of luck with the website 🙂

We've marked this ticket resolved 🙂