This is a typical issue for mono language site not in eng-GB and I'm afraid there's no easy solution currently.
The cleanest solution is probably to remove the eng-GB language through /content/translations in the admin interface. But if I remember correctly, to be able to do this, you have to translate all existing objects and classes in fre-FR and then remove the eng-GB versions for each... On an existing project this can be quite long but I think it should be feasible through a script if you consider that not yet translated objects/classes should be the same in fre-FR.
@Damien thanks, i was afraid of this answer (i've seen the 'eng-GB' hardcoded somewhere :-s). Think i should'nt have created the french language, it would have been simplier. Anyway, that's a new website, i might restart the install ^^'
@Thiago that's a solution, but i don't like overriding BO functions, specially "the create here" drop down (which has discutions about usability if i remeber correctly).
eng-GB is not "hardcoded" in eZ. It's just that the default content classes are all created in english, and you have to de-translate them before english can be deactivated. Starting with a very empty content setup is your best bet (get no demo content from packages or start the db using the sql provided with sources instead of using the setup wizard)
Principal Consultant International Business
Member of the Community Project Board
