Monday, January 7, 2019
6 changes · master
Enhancements to existing features
Users can now manage Odoo's paid service settings from clearer dedicated sections, including turning services on or off and recharging credits directly from the database. This makes services like SMS, postal mail, contact enrichment, and invoicing-related mail easier to find and administer.
Original PR description
Allow users to: - access the IAP services settings in a dedicated section - enable/disable them at will - recharge credits from database Task #1909302 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo can now accept configuration folders, making it easier to separate shared default settings from operator-specific overrides. This helps teams manage configuration items with different lifecycles without adding extra workaround layers.
Original PR description
rcfolders are a flexible way to decouple config items according to their invidual lifecycle. That means that mix and match config straegies using magic [DEFAULT] become possible. This avoides…
rcfolders are a flexible way to decouple config items according to their invidual lifecycle. That means that mix and match config straegies using magic [DEFAULT] become possible. This avoides wrapping the ini-config API in cases where two sets of conig items origin from two different sources. Eg.: ConfigMaps **Description of the issue/feature this PR addresses:** - monolithic config files do not cater to the different life cycles of config items **Current behavior before PR:** - not possible to apply mix-and-match config strategies without effectively wrapping the config API into another abstraction layer (eg. ENV variables). **Desired behavior after PR is merged:** - Provide a default config file (managed by the team) - Easily override with a custom config file, managed by the individual operator **Note:** Please do not close, even if not immediately accepted (wishlist tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another. Replaces: https://github.com/odoo/odoo/pull/22573 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
Invoice OCR settings have been reorganized so they appear in the appropriate accounting settings area and are available to invoicing users. The update also clarifies labels and highlights company-specific options, making configuration clearer for multi-company businesses.
Original PR description
Since https://github.com/odoo/enterprise/commit/e1a3ecef7606159c3ae4ed6bc93034bcecb14085, account_invoice_extract depends on account_accountant and not account. So this commit move the settings of account_invoice_extract from account to account_accountant, add the multi-company icon to company-dependant setting and rename some labels
Resolved issues and error corrections
Website pop-up dialogs now place the primary action button in the expected corner, making important actions easier and more intuitive for users to choose. The update also includes small layout fixes to improve consistency and readability in affected website screens.
Original PR description
Modal primary button should be the one in the corner (left if buttons aligned left, right if buttons aligned right) as in the Bootstrap doc. More than a simple guideline, the user will intuitively click on the button in the corner as it is supposed to be the primary one. Plus some DOM fixes (o_technical_modal was missing, H2 was too big especially since BS4) task-1922120
This fixes a broken option that lets users search through available fields when building domain filters. The search input is now correctly passed through and enabled for mass mailing, making it easier to configure mailing audiences.
Original PR description
PR #27788 introduced the possibility to add a `showSearchInput` property to domain widgets, which should allow users to fuzzy search on the fields list.
This feature was buggy and was not properly working when the field was declared with such option:
```xml
<field name="domain_field" widget="domain" options="{'showSearchInput': true, 'model': 'model_field'}"/>
```
This commit fixes that problem, and BTW it enables the feature in `mass_mailing`, which is one of the modules where this feature is most useful.
Another question that I still cannot understand is: **Why default to false?** But I didn't want to change that in this PR for now.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
@Tecnativa @mge-odoo @qsm-odooThe UPS delivery website modal now places the main action button in the expected corner position. This makes the dialog easier and more intuitive for customers to use, reducing the chance of clicking the wrong option.
Original PR description
Modal primary button should be the one in the corner (left if buttons aligned left, right if buttons aligned right) as in the Bootstrap doc. More than a simple guideline, the user will intuitively click on the button in the corner as it is supposed to be the primary one. task-1922120