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

Error 404 with multilingual feature sample data installation and solution. #6036

Closed
gmobravo opened this issue Feb 10, 2015 · 2 comments
Closed

Comments

@gmobravo
Copy link

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.

System information (as much as possible)

Additional comments

This occurs becouse the sample data in the 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 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.

As my skills does not allow me to creat a new pull in the GitHub I put the solution here:
We have to replace the "en-GB" reference for a '*' in the lines 385, 387, 388, 389, 439, 440 of the /installation/sql/mysql/sample_testing.sql file

@infograf768
Copy link
Member

You should NOT use a sample data when installing a multilanguage site from scratch. This is clearly stated on the page where one chooses a sample or not.
Closing as not a bug.

@javigomez
Copy link
Contributor

Thanks @gmobravo for the report. Jean Marie is right, when we did the multisite installer we were forced to add this clause at the demo data:

screen shot 2015-02-10 at 09 56 43

Because to be able to generate the dummy data internationalised we needed to have a clean database, otherwise we couldn't predict possible conflicts. So is a must that we do not add any demo data.

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

4 participants