I agree with McFly, I’m a CI / non-framework-php dev and the single reason I wanted to use EE is because it’s based on CI (and I thought, that if something goes wrong, I’ll just use CI stuff within it…), not quite the case and I’m really regretting it.
My issue is that I need to build a fairly complex site that will be available in 9 languages.
After reading through various tutorials and how-to’s I figured out how to do that, however, the only feasible approach that I can take (and still please my clients requirements, when it comes to the backend data entry) is using cookies for the language selection, not using the language selection in the uri and using a single template for every language.
This is still pretty simple in my book, it’s heavy on the server, but still does the job.
How I intend to do this (I’m usign EE 2.0):
1. The user clicks an area, that sets a cookie (gonna use jquery, as the site relies heavily on it and does not care about non-js users) and reloads the page.
2. The page checks if the lang cookie is set, if it is, defines the content of the cookie as a variable.
3. The variable is read by every single bit that requires text, something like this is used:
{if title_<?php echo $lang; ?>} {title_<?php echo $lang; ?>} {if:else} {title} {/if}
This way the required language is displayed if the related custom-field is populated via the backend, otherwise English is displayed as a fallback.
Now the only place where this collapses is the list of categories. I have no fricking clue how to change the names of the categories themselves, depending on the required language.
A product will be associated to a category and then the list of categories will be displayed as a nav list. This nav list, at least as far as I know will have to be in English across all of the languages.
I have no clue how to work around this :(
EDIT
Custom fields for categories :D enough said.