Monday, December 31, 2018
3 changes · master
Enhancements to existing features
Several core setup forms now have a clearer page structure, making them easier for developers and implementers to adapt safely. This helps reduce customization friction around banks, countries, contact tags, titles, industries, and related reference data without changing day-to-day business workflows.
Original PR description
Description of the issue/feature this PR addresses: Not perfectly created views with hard to reach elements for developers. Current behavior before PR: Multiple base views have no `<sheet>` set and have some annoying parts to xpath. Desired behavior after PR is merged: The form views have a `<sheet>` set and have names set on the most important items for easy `xpath` expressions. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes resource form views easier to customize by allowing cleaner targeting of specific sections. It helps future configuration and development work happen more quickly with less risk of fragile changes.
Original PR description
Description of the issue/feature this PR addresses: Allow easier `xpath` expressions on forms Current behavior before PR: Not easy to xpath into some parts of the form views Desired behavior after PR is merged: Easy and clean `xpath` expressions to change the views -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fix ensures link tracking records cannot be duplicated when they have the same URL and campaign details. It helps keep marketing tracking data cleaner and more reliable by enforcing the intended uniqueness rule.
Original PR description
Description of the issue/feature this PR addresses: In module `link.tracker`, a `_sql_constraints` definition is wrongly written as `sql_constraints`. This typo is causing the constraint `'unique (url, campaign_id, medium_id, source_id)'` not being applied on model `link.tracker`. Current behavior before PR: The sql constraint `'unique (url, campaign_id, medium_id, source_id)'` has no effect. Desired behavior after PR is merged: The sql constraint `'unique (url, campaign_id, medium_id, source_id)'` is applied. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr