It looks like this issue was originally reported as a bug back in August '06 on v4.3.3.  It hasn't been assigned to anyone yet though so its not clear when a fix might be coming.  See the link below for more info.  In the meantime, if anyone has any workaround ideas besides the one I posted above, I'd be interested in hearing them.

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=3947

 

While working with localisation, I recommend you to take a look at this issue concerning errors in the DotNetNuke default resource files supplied in the original core and modules. Sebastian Leupold has published a correct resource file in this thread in the DNN Blog.

If you work with localisation with an defect English Resource File in your DNN installation, your localized resource fiel will be corrupt as well, and you will have to rework all your effords all over again.

---

Trafic injured non profit Site owner/webmaster/admin/user without programming skills, eager to help other injured and sever ill persons.

This has nothing to do with edit permissions. The problem is on module caching: when a module is cached it is not "recreated" as normal modules. Instead the final html is saved/retrieved directly.

If your module should present different output depending on the active language then you cannot use caching.

---

Vicenç Masanas
Banyoles, Girona - Spain