Hi Roberto, the new project makes me back to multilanguage problems and solutions :)
I see that situation with i18n & localizer have changed a lot since summer when I released my first localizer-powered site, I've tried them both again yesterday. Actually I didn't like how menu translation interface looks like for now (in earlier versions there were collapsible sections so you could translate the menu much faster than now with selectbox+page refresh), but I suspect that you had the real reasons to do it. Oh, sorry, I'm offtopin' too much :)
So, the bug:
fresh Drupal 5.3 + localizer dev (27nov)
Fatal error: Call to undefined function localizer_get_uilocale() in y:\home\localizer\www\modules\localizer\modules\localizervariable.module on line 14
if I try to enable all localizer* modules at once.
If I enable localizer and THEN enable localizervariable - I get no problems, so the bug is in module load order, I suspect.
Comments
Comment #1
Roberto Gerola commented> Actually I didn't like how menu translation interface looks like for now (in earlier versions there were
> collapsible sections so you could translate the menu much faster than now with selectbox+page refresh),
> but I suspect that you had the real reasons to do it. Oh, sorry, I'm offtopin' too much :)
Hi.
I tried to balance different needs.
>If I enable localizer and THEN enable localizervariable - I get no problems, so the bug is in
> module load order, I suspect
Yes, you are right.
I'm working on this.
Thanks
Comment #2
duaelfrThis version of Localizer is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.