Tuesday, March 25, 2025
1 change · saas-17.4
Resolved issues and error corrections
The Twitter integration setting now uses a more specific label to avoid a naming conflict with another integration setting. This prevents unnecessary system warnings during module loading without changing user workflows.
Original PR description
The field `res.config.settings.twitter_api_key` has the same label `API Key` as the field `res.config.settings.employment_hero_api_key` from module `employment_hero`, which takes it from its related…
The field `res.config.settings.twitter_api_key` has the same label `API Key` as the field `res.config.settings.employment_hero_api_key` from module `employment_hero`, which takes it from its related field `res.company.employment_hero_api_key`[[1]](https://github.com/odoo/enterprise/blob/365fbed2db68626bc175aed4a349c09d872cc717/l10n_employment_hero/models/res_company.py#L19C5-L19C28)[[2]](https://github.com/odoo/enterprise/blob/365fbed2db68626bc175aed4a349c09d872cc717/l10n_employment_hero/models/res_config_settings.py#L9). Having multiple fields on the same model with the same label generates [warnings](https://github.com/odoo/odoo/blob/1ca879612fe546108fd1067839924ae8c25b2bb9/odoo/addons/base/models/ir_model.py#L1193-L1196) when loading the module. The [view](https://github.com/odoo/odoo/blob/ef3aac00ce7737498589a3df68be47c7a3b45d24/addons/website_twitter/views/res_config_settings_views.xml#L12-L16) using the twitter_api_key field already sets the same label. The module is removed in 18.0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr