Friday, July 24, 2020
15 changes · master
Enhancements to existing features
Grouped rows in list views now use tighter spacing and better caret alignment. This makes grouped lists look cleaner and more consistent, especially when selection checkboxes are shown.
Original PR description
This PR changes a bit the style of groups in list view * reduced padding-top/bottom of group headers to 5px * increased the padding-left by 2px of carets to align them with selection checkboxes (in enterprise) Task 2301397 ENT PR: https://github.com/odoo/enterprise/pull/11955
Resolved issues and error corrections
Odoo now avoids repeating an internal setup step for finding add-ons during normal startup and module lookups. This reduces unnecessary work while preserving the needed setup for early command discovery, helping keep startup behavior reliable.
Original PR description
The `initialize_sys_path` is the function responsible of getting the custom Odoo import hooks to work, i.e. addons import via `import odoo.addons`. This function is called by some other module related functions to ensure the paths are correctly setup. We are confident it is useless to re-initialize the path in many places. The `load_openerp_module` function is called during server bootup by both `odoo-bin server` and `odoo-bin shell`, both command parse the configuration before starting the server which initialize the paths already. Most call to `get_module`, `get_module_path` and `get_resource_path` are done in models or controllers where a registry is setup already. There is one notable exception which is the subcommand discovery done during the bootup, for that specific case, we initialize the paths with a partially loaded configuration. Task: 2200956
Miscellaneous changes
RATIONALE Even will soon gain a major update called Event Online, allowing to better support full-online events. In order to prepare its merge, preparatory merge are done to lessen the final diff. PURPOSE Prepare Event Online support by providing fixes and preparatory cleaning commits. SPECIFICATIONS Prepare some cleaning in sales_team / event common test files in order to ease new tests writing. Provide fixes for event after some testing in 13.3 Update demo data, notabl
Original PR description
RATIONALE Even will soon gain a major update called Event Online, allowing to better support full-online events. In order to prepare its merge, preparatory merge are done to lessen the final diff. PURPOSE Prepare Event Online support by providing fixes and preparatory cleaning commits. SPECIFICATIONS Prepare some cleaning in sales_team / event common test files in order to ease new tests writing. Provide fixes for event after some testing in 13.3 Update demo data, notably to prepare future Event Online support. See sub commits for more details. LINKS Task ID 2289148 (Event Bugprovements) Prepares Task ID 2283796 (Event B2Basics) Prepares Task ID 2252655 (master Online Event task) Forward-Port-Of: odoo/odoo#53956 Forward-Port-Of: odoo/odoo#53944
Grouped list headers now display without shadow effects that caused thin white gaps near borders. The header background is also slightly softened, improving visual consistency and readability in list views.
Original PR description
This PR removes the box-shadows on group header in list view. These box-shadows caused a visual glitch, there was a white line of 2-3px between the text and vertical borders. This PR also adds a slight transparency on group header's background. Task 2301397 COM PR: https://github.com/odoo/odoo/pull/54736
This corrects a small mistake in the multicurrency revaluation wizard so default values are requested using the proper input. It helps ensure the accounting report workflow initializes correctly and avoids unexpected behavior from the previous typo.
Original PR description
Wrong usage of fields instead of default_fields arg in default_get override. Finetuning of https://github.com/odoo/enterprise/commit/a8c2bceb178d2d2f0b365cd126744459dbd1626c
Various improvements and fixes are done: * Before, if we had PREFIX/9 and PREFIX/10, the highest number was the lexicographic order, leading to proposing PREFIX/10 again and again. Because of performances, we can't execute the regex in the SELECT query and we need to store it in the database. This will allow to do an indexed search. See https://github.com/odoo/odoo/pull/52986 and https://github.com/odoo/odoo/pull/52790 * The regex can now take more kinds of patterns. Before, we had to have
Original PR description
Various improvements and fixes are done: * Before, if we had PREFIX/9 and PREFIX/10, the highest number was the lexicographic order, leading to proposing PREFIX/10 again and again. Because of…
Various improvements and fixes are done: * Before, if we had PREFIX/9 and PREFIX/10, the highest number was the lexicographic order, leading to proposing PREFIX/10 again and again. Because of performances, we can't execute the regex in the SELECT query and we need to store it in the database. This will allow to do an indexed search. See https://github.com/odoo/odoo/pull/52986 and https://github.com/odoo/odoo/pull/52790 * The regex can now take more kinds of patterns. Before, we had to have the grouping keys in a certain order, with required groups for each reset mode. This is not longer the case. It allows having a suffix in multiple parts for instance, and to have the year/month in it. * We can handle the year with 2 digits now. It needs a separator between the year and the month if we are in a monthly pattern. * The prefix used is no longer the highest with a lexical order, but the last used in the relevant range (journal/date) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54408 Forward-Port-Of: odoo/odoo#53393
Make the error message more comprehensible for users, using the record's display name, the company's name, the field's label and value. Incompatible companies on records: - 'Foo' belongs to company 'X' and 'Contact' (partner_id: 'Bar') belongs to another company. Forward-Port-Of: odoo/odoo#44859
Original PR description
Make the error message more comprehensible for users, using the record's
display name, the company's name, the field's label and value.
Incompatible companies on records:
- 'Foo' belongs to company 'X' and 'Contact' (partner_id: 'Bar')
belongs to another company.
Forward-Port-Of: odoo/odoo#44859QR-BILL report has no margin so we can position things exactly where they needs to be according to standard. For example the form must stick at the bottom and have 100% width, so we can't use paperformat margin that would not allow to have 100% width. With this change, we set default padding on header so it match better "European A4" paperformat (that has 5mm top margin and 7mm right and left margin) for stylistic purpose. This is currently not configurable so for custom header size still nee
Original PR description
QR-BILL report has no margin so we can position things exactly where they needs to be according to standard. For example the form must stick at the bottom and have 100% width, so we can't use paperformat margin that would not allow to have 100% width. With this change, we set default padding on header so it match better "European A4" paperformat (that has 5mm top margin and 7mm right and left margin) for stylistic purpose. This is currently not configurable so for custom header size still need view editing to change current values, but this at least make the edition easy. opw-2267041 Forward-Port-Of: odoo/odoo#54719 Forward-Port-Of: odoo/odoo#54717
- Create a partner, set a VAT number - Create an invoice - Download the E-Faktur The NPWP (VAT number) remains zero. opw-2296971 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54885
Original PR description
- Create a partner, set a VAT number - Create an invoice - Download the E-Faktur The NPWP (VAT number) remains zero. opw-2296971 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54885
When a user with access to company A tried to make a purchase on the website of company B, he would face a traceback upon calling `_get_pricelist_available`. This happens because we eventually try to access to the current company (B) while forcing environment of the user (in company A), thus forfeiting the superuser privileges, which triggers an access error. opw-[2303488](https://www.odoo.com/web?debug=1#id=2303488&model=project.task&view_type=form&menu_id=5200) Forward-Port-Of: odoo
Original PR description
When a user with access to company A tried to make a purchase on the website of company B, he would face a traceback upon calling `_get_pricelist_available`. This happens because we eventually try to access to the current company (B) while forcing environment of the user (in company A), thus forfeiting the superuser privileges, which triggers an access error. opw-[2303488](https://www.odoo.com/web?debug=1#id=2303488&model=project.task&view_type=form&menu_id=5200) Forward-Port-Of: odoo/odoo#54809
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54890
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54890
This button has now a "btn-secondary" class. **Task ID:** #2288963 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54207
Original PR description
This button has now a "btn-secondary" class. **Task ID:** #2288963 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54207
The tour system is made such that we always have at most one tip displayed on every screen. Since commit [1], "inactive tips" (i.e. tips that aren't displayed because there's already an higher priority tip displayed), are rendered, but turned invisible (s.t. their action is still consumed when their anchor is clicked on), whereas before [1], those inactive tips weren't rendered. As a consequence, in the enterprise Home Menu with **a lot** of apps installed (e.g. on runbot), it lags when
Original PR description
The tour system is made such that we always have at most one tip displayed on every screen. Since commit [1], "inactive tips" (i.e. tips that aren't displayed because there's already an higher…
The tour system is made such that we always have at most one tip displayed on every screen. Since commit [1], "inactive tips" (i.e. tips that aren't displayed because there's already an higher priority tip displayed), are rendered, but turned invisible (s.t. their action is still consumed when their anchor is clicked on), whereas before [1], those inactive tips weren't rendered. As a consequence, in the enterprise Home Menu with **a lot** of apps installed (e.g. on runbot), it lags when the user scrolls, because all those invisible tips still do a lot of computation to reposition themselves. This commit skips these positionning computation for invisible tips. [1] 3bf1d8418f41bcaa0ba4b153620def11aaea0a2b Issue spotted while testing task 2263600 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54911
Forward-Port-Of: odoo/enterprise#12004
Original PR description
Forward-Port-Of: odoo/enterprise#12004
Understanding how a pivot is build is not particularly easy. One reason being the funky cache structure. This commit hides the cache data stucture complexity inside a new object with a nice public API with proper names and documentation. Co-authored-by: fleodoo <fle@odoo.com> Forward-Port-Of: odoo/enterprise#11931
Original PR description
Understanding how a pivot is build is not particularly easy. One reason being the funky cache structure. This commit hides the cache data stucture complexity inside a new object with a nice public API with proper names and documentation. Co-authored-by: fleodoo <fle@odoo.com> Forward-Port-Of: odoo/enterprise#11931