Thanks ot2sen.
So as quoted below, one should have a menu module for each language. Did I get this right?
And yes I know it is not the same thing, anyway there could be a database migration option. It is not easy to migrate 1000 translated items though. I think the new core system is very usefull, so magguire would be asked to create a upgrade or migrate script for that as well!
Quote:
Defining a Default Home page Menu item per language
As the Language Switcher Module is set to redirect to another Content Language Home Page, one has to be defined for each language. Important Note: A default Home page taggged to "All" should still exist, although the module displaying it does not have to be published.
There is a big problem if you want to do that good:
You have to assign the original language module to be displayed on all pages except of pages where translations are. So every time you change sth. in translation section, you have to update the menu module appearance.
I think my solution above is way easier to do, isn't it? How is this connected with performance?
What is better - to have more different modules displayed on different pages or to have one single module with more items and not all of them visible on all pages?
If it is the same what performance is concerned I would prefer my solution. What do you think?
