Frontend localisation
This is an open discussion with 8 replies, filed under Installation.
Search
Ouch. My mistake. Does this commit fixes it?
Oh yes! Thanks vladG! :D
Sorry but I have another issue: I click on translations, create new, I write on each fields, select pages, etc, but when I save it I get an HTTP 500 (Internal Server Error).
Odd ... I don't encounter any issues when creating new translations.
Check your error log and put the error here, please.
I install this extension on a clean installation of symphony but I have the same problem. Sorry but after I install this extension, have I to create new translations or have I to setup "it" in "preferences"? Maybe I'm wrong in this step. However, this is the error in log:
09/05/2012 6:57 pm > Error: The selected language, it, could not be found. Using default English dictionary instead.
Indeed there was some sloppy code. I fixed it and a friendly message is now displayed on Translations page. Grab the latest version and check it out.
@admin
Please close this thread as there should be only one thread for Frontend Localisation.
Thanks!
Create an account or sign in to comment.
Hi! I have installed "fontend localisation" but I give a symphony's error when I click on "Translation" in backend. I have installed "FLang detection gTLDs" before. In the attached image there's the error that symphony return me.
How can I solve my issue? Help me please!