Odoo Changelog — 2019-03-18

Monday, March 18, 2019

3 changes

Improvements(3)

Enhancements to existing features

[IMP]base: Improved logger message of PDF report generation

Coremasterbase

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

#pdf reports#logging#traceability

[IMP] im_livechat: set default user image instead of placeholder

PR #30821

Coremasterim_livechatweb

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

#livechat#avatar#user image

[IMP] web: only display missing view erorr in debug assets

PR #31884

Coremasterweb

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

#debug#testing#views

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

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

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