Contributors mailing list archives
Re: Robust renaming in codeby
Tecnativa. S. L., Pedro M. Baeza
I "forbid" (not real forbidding, but persuasion) to do this in my customers, as the maintenance cost for such a whim doesn't worth it IMO. They adapt to current nomenclature easily when you involve serious (but real) costs about that.
Anyway, if you still want do it, it depends on what to rename:
- Fields: override `string` attribute of the field.
- Menus: XML with the original XML-ID, but for translations, you need to add a i18n_extra folder.
- Hardcoded string in reports: XML inheritance, replacing contents (which is also very bad for compatibility, but reduced if using a lower priority - 9999 or so-).