Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10 languages = 30-50 navigation menu blocks #1690

Closed
bd0bd opened this issue Mar 5, 2016 · 9 comments
Closed

10 languages = 30-50 navigation menu blocks #1690

bd0bd opened this issue Mar 5, 2016 · 9 comments

Comments

@bd0bd
Copy link

bd0bd commented Mar 5, 2016

10 main menu blocks
10 services menu blocks
10 about menu blocks

It is minimum 30 menu blocks we need for a small multi lang website.
If we add additional ones then it will be 40 or 50 menu blocks.

Also we would need to have additional 10 header blocks for each language.

It is too much blocks.
I think it is sickly abnormal situation for a respectable CMS like Backdrop.
We are respectable I think so :)

This CMS is an international one and it is not a new on the market but still it has no a normal and easy solution implemented.

@findlabnet
Copy link

@bd0bd, you absolutely right: full i18n implementation - a must in today's world. Even for Drupal 6 site by using this contribute 10-15 languages is not a problem.

@herbdool
Copy link

herbdool commented Mar 6, 2016

Backdrop CMS, since it is born out of Drupal 7, currently only has whatever Drupal 7 had for multilingual support in core. If you've ever built a multilingual website with Drupal 7 you'll know that for complex multilingual support you soon have to use the Internationalization (or i18n) and/or Entity Translation contrib modules.

I currently don't need i18n but figured I would eventually so recently I attempted to port Internationalization to Backdrop and made some progress with the base module. But that module is a complex beast and it would take some time to port all the submodules to Backdrop. One key issue is that i18n relies on the Drupal Variable module which is based on the old configuration in the database system in Drupal and not the new configuration management system in Backdrop (or Drupal 8). And even if these modules get ported, the core maintainers may go a different route whenever they are able to provide more multilingual support in core.

In short, porting this could use other people's help. I'm not working on it at the moment (but may pick it up again at some point in the future).

@bd0bd
Copy link
Author

bd0bd commented Mar 8, 2016

@findlabnet, do you mean this module is a complete solution (not only for menu blocks but for all other aspects) for multi lag website?

@herbdool, of cause it would be very good if somebody would port it. I would do it but I can not.

@findlabnet
Copy link

@bd0bd

this module is a complete solution

silver bullet doesn't exists at all, but for example, one menu with 10 translations seems much better than 10 menus - one per language, plus translatable variables for fields such as site name, etc. Anyway, features of this module very good documented in Drupal world.

@herbdool
Copy link

herbdool commented Apr 3, 2016

There's been a start at porting i18n but still a ways to go.

@bd0bd
Copy link
Author

bd0bd commented Apr 3, 2016

I know. I have already try it.

@herbdool
Copy link

herbdool commented Apr 3, 2016

I haven't tried it but I doubt it's usable yet. I started porting it separately and found it required a lot of work.

@bd0bd
Copy link
Author

bd0bd commented Apr 3, 2016

4 main problems with multi lang site:

menu
home page
header
views pages

These are the key things should be solved firstly in my opinion.

@ghost
Copy link

ghost commented Sep 27, 2019

Going to close this in favour of something like #3369 where different issues can be separated and and worked on independently.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants