Thursday, May 12, 2016
3 changes · master
Enhancements to existing features
The Live Chat History page now shows a helpful message when there are no records to display instead of leaving users facing a blank area. This makes the page easier to understand and reduces confusion for website/live chat managers.
Original PR description
Description of the issue/feature this PR addresses: - History menu tip Task:https://www.odoo.com/web#id=23716&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad:https://pad.odoo.com/p/r.8fec0172b043abccbf68600d693643b0 Current behavior before PR: - When user goes to Website Live Chat -> History , blank stripe appears. Desired behavior after PR is merged: - When user goes to Website Live Chat -> History , blank stripe appears, so add one appropriate message for user's understanding. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr …ecause when user goes to Website Live Chat > History , blank stripe appears.
Resolved issues and error corrections
This update corrects how database query placeholders are written in the Point of Sale reporting code and shared test utilities. It helps prevent potential errors when reports or tests run, improving reliability without changing user-facing workflows.
Original PR description
Description of the issue/feature this PR addresses: Addresses the use of %d as a placeholder within the point_of_sale module's "pos_order_report" report and openerp/tests' common.py. Per psycopg's documentation[1], "the variables placeholder **must always be a %s**, even if a different placeholder (such as a %d for integers or %f for floats) may look more appropriate." [1] http://initd.org/psycopg/docs/usage.html#passing-parameters-to-sql-queries See, too, commit ed7567d3f55b12181693ae27c0019aad849b7a80 Current behavior before PR: Untested, but the use of %d should lead to an error. Desired behavior after PR is merged: Compliant type ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Cody K
Belgian VAT reporting was updated around manual adjustments for VAT grids 61 and 62. The change removes a duplicate adjustment wizard from Enterprise because that functionality is already available in the community edition, helping avoid overlap and confusion.