Daily updates from Odoo
Navigate
Branch
Monday, March 18, 2019
9 changes
Enhancements to existing features
The Point of Sale app now prevents fiscal year or period lock dates from being set when open POS sessions would be affected. It also stops new POS sessions from being created before a lock date, helping businesses avoid sessions that cannot be closed or posted to accounting.
Original PR description
Without that, it is impossible to close these sessions, as the lock date forbids posting accounting entries for them.
PDF report generation messages now show the type of business record alongside the record IDs. This makes logs clearer for support and operations teams when tracing which reports were generated.
Original PR description
Description of the issue/feature this PR addresses: Improved in logger message Current behavior before PR: When user generates PDF report Logger doesn't displays model name `The PDF report has been generated for records [1]. ` Desired behavior after PR is merged: Show model name along with records Ids `The PDF report has been generated for model: sale.order, records [1]. ` -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Live chat now shows a standard user avatar when a visitor or operator has not set a personal image. This avoids the generic missing-image placeholder and makes conversations look more polished and consistent.
Original PR description
Description of the issue/feature this PR addresses: - Task - https://www.odoo.com/web#id=1924666&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.e25a7fd535b599e0a272183ac6cbbd8d Current behavior before PR: - When user image isn't set, at the time of livechat default placeholder is displayed. Desired behavior after PR is merged: - When user image isn't set, at the time of livechat default user image will be available instead of the default placeholder. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo will now show missing view warnings only when developers are using debug assets mode. This prevents expected Enterprise-only view references from causing failed automated click-through tests while still keeping useful diagnostics available for developers.
Original PR description
This error is there to help developpers realize their view has not been loaded due to an error. However, we have cases where we define actions containing views that only exist in Enterprise to avoid creating an entire bridge module just to add one view to an action. The error was triggered in this case which resulted in a red build for the click all runbot test, even though this was not really a true error, as it was intended. This commit changes the error to only appear in debug=assets such that it will no longer put the click all runbot tour red while still providing help for the developper trying to debug his view since he will need to be in debug=assets to debug his view anyway. 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
Images and other attachment previews in chat now expand to the full available message width. This makes shared pictures, PDFs, and videos easier to view directly in conversations without extra opening or zooming.
Original PR description
Task Link: https://www.odoo.com/web#id=1941601&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.393faf958ee09a5d0062ca416709cfa1 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The website theme customization dialog now shows heading colors correctly again instead of appearing transparent. This prevents confusion when users adjust website styling and helps ensure theme settings display as expected.
Original PR description
Since the bootstrap update that was merged with https://github.com/odoo/odoo/commit/754ec4450832dceef83c3a0abb79401f2e7ec05d the customize theme dialog was showing transparent colors for the headings. This was because bootstrap changed the value of the related variable from 'inherit' to 'null' to avoid an useless css rule if the headings are supposed to have the same color as the body text.
This fix updates the website eLearning code to use the proper frontend component for non-animation behavior. It helps keep course category and slide archive interactions stable and aligned with the platform's expected website behavior.
Original PR description
Purpose ======= This follows up commit d946b7a85d2c1bbc20ace8e2b269be56a63876fd that cleans wrong uses of sAnimations for non-animated behaviors. 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
This fix corrects promise handling issues introduced during the move to jQuery 3 in the Website app. It helps restore reliable website editor and theme behavior, reducing unexpected failures for users managing website content.
Original PR description
Since the switch to jQuery 3, Odoo uses native promises in its JS. Some mistakes were made in the website app during conversion from old jQuery deferred to native promises. - `this` -> `self` when wrapping in a promise - `.always(fct)` -> `.then(fct).guardedCatch(fct)` - a function returned sometimes a jQuery deferred, sometimes a native promise. This made the caller fail when using `always` or fail when using `guardedCatch`
Code cleanup and technical improvements
Event website menus are no longer wrapped in card-style containers. This keeps cards reserved for actual records or title-and-body content, making event pages visually clearer and more consistent.
Original PR description
With https://github.com/odoo/odoo/pull/30559 we introduced cards to wrap menus. We changed our mind, only use card for records and title/body contents.