Multilingual
Permalink Browser Info Environment
Hi...
setting up standard multilingual Megameu shows only pages below the first language.
To setup multilingual i create a "dummy" home for the language I need in addition to my default language, and then I create pages under default language or under second language.
The home page (the default menu and the "dummy" one for the second language) are exludet from navigation
I attach a screenshot on what happens
Can you please help me ? I do have hudered of pages indefault language and I must manage them in two languages
setting up standard multilingual Megameu shows only pages below the first language.
To setup multilingual i create a "dummy" home for the language I need in addition to my default language, and then I create pages under default language or under second language.
The home page (the default menu and the "dummy" one for the second language) are exludet from navigation
I attach a screenshot on what happens
Can you please help me ? I do have hudered of pages indefault language and I must manage them in two languages
| Type: | Ticket |
|---|---|
| Status: | Archived |
Ok.. thank you so much... I LOVE this addon
I mean it's a workaround but it lets manage simple situations...
I'm dealing with a large site that uses a lot of features, and I really had the wish that the input of MegaMenu would be the file structure that C5 displays (even when multilingual is turned on)... in order to have a polite work... Think on what could be the confusion if I have 4 languages, each of them using multiple page header types to distinguish specific sections..
If you plan in the future to make maintenance, please keep this request live
Best regards, and my compliments for this addon
Michele
I mean it's a workaround but it lets manage simple situations...
I'm dealing with a large site that uses a lot of features, and I really had the wish that the input of MegaMenu would be the file structure that C5 displays (even when multilingual is turned on)... in order to have a polite work... Think on what could be the confusion if I have 4 languages, each of them using multiple page header types to distinguish specific sections..
If you plan in the future to make maintenance, please keep this request live
Best regards, and my compliments for this addon
Michele
Hi Michele,
I think the same thing would occur if you used the core "Autonav" block. Mega Menu is designed to be easily translatable in any language (using C5 best practices). But that is a bit different to running multiple languages on the same site.
Even though I've built with C5 for years I've never had the need to build a multilingual site so I can't provide any specific guidance on that. However there's plenty of helpful tips in the C5 community forum and also the docs on the C5 website.
Best of luck.
JB
I think the same thing would occur if you used the core "Autonav" block. Mega Menu is designed to be easily translatable in any language (using C5 best practices). But that is a bit different to running multiple languages on the same site.
Even though I've built with C5 for years I've never had the need to build a multilingual site so I can't provide any specific guidance on that. However there's plenty of helpful tips in the C5 community forum and also the docs on the C5 website.
Best of luck.
JB
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Here's a screenshot on Mega Menu where you can choose what the parent page is:
https://www.concrete5.org/files/6114/4680/8322/jb_megamenu_screensho...
(3rd field "display pages"). If you choose the home page of one language, then all the sub pages will be used as Mega Menu items.
I'd suggest having a separate header.php file for each language (eg. header_en.php) so you can have a unique site-wide editable area in your theme for each language. For example, the English menu would go in the "header_en.php" page, and all pages under that parent should use the same new page type. These issues are more about general Concrete5 functionality and custom coding and as such please note I can't provide detailed support for this. However, I hope my suggestions have pointed you in the right direction.
JB