[#6037] - 404 error mulitlingual installation mysql
- Closed
- 10 Feb 2015
- Medium
- Build: staging
- # 6037
- Diff
- gmobravo:patch-1
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Steps to reproduce the issue
Create a new installation with the "sample testing" data and then at the end of installation choose also the multilingual feature.
Expected result
All the menu items in the Top Menu should works both english and the language you choose to use the multilingual feature.
Actual result
404 Error when you click on the "Parks" menu item in other language than english. Only works in english.
Additional comments
This occurs becouse the sample data in the /mysql/sample_testing.sql in the "#__menu" table create the "Australian Parks" menu with "en-GB" instead '*' and as the "Parks" menu item in the Top Menu is just an alias to the "Parks Home" menu item of the "Australian Parks" menu, the the resoult is and 404 error page due the multilingual feature.
To solve this, it is necessary modify the /mysql/sample_testing.sql file and replace, in the "#__menu" table the references to the "en-GB" language, for the '*' to make it available in all the languages.
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Title |
|
||||||
| Title |
|
||||||
Its a poor UI but it does say that to install the multilingual feature you must choose no sample data
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6037.
It shows to me that the language functionality is not very robust at that point. Even if you install no sample data you can input that data manually afterwards.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-02-10 16:21:29 |
It only shows that installing multilingual from the beginning can't be done with an important sample data because we do not know when installing what will be the languages chosen by the user.
We decided to go with a simple stuff (1 category + 1 article + a Home page per language) set to these languages.
Doing more is possible but what would anyone want to be added? It is likely that each one may have different needs.
I sense a problem with the language functionality per se. The same data worked with J3.3.6 - if I didn´t overlook something - but not with the current staging branch.