In earlier versions of DNN, there used to be problems when translating modules friendly names. One of the most annoying symptom was the creation of a 'zombie module' upon an upgrade. Say you translated 'links' as 'liens', you got 2 modules after upgrading. Obviously some code was using the friendly name instead of the modulename.
I think there is a large consensus that the term 'friendlyname' implies something that you could change as you want, without compromising the future of your portal integrity.
In earlier posts, I read intentions to clean up the code so the module friendly names would become 'code neutral'
As of DNN 3.2.2, there are still issues with module friendly names. For example, if I reinstall the links module, it will reset the module friendly name to the english default, including the description.
As a sidenote,modules friendly Name change is mainly used for localization, but it can be used for other purpuses. For example renaming the friendly name of Text/HTML as _Text/HTML to display on top of the module listbox, or grouping module in any order you wish.
So the questions are :
1. Does anybody here have a clear picture of what can be - and what should NOT be changed in module friendly names as of DNN 3.2.2+ ?
2. Would you please Vinçens get module developpers informed that their code should not rely on module friendly names, and that upgrades should not change these fields (friendlyname and description)- this should be a criteria for a 'localizable' label.
3. Should not module friendly names be completely moved out the resx files ?
Thanks for your attention on this
Benoit