Monday, January 28, 2019
14 changes · master
Enhancements to existing features
Portal users can now sign documents using typed or uploaded signatures in addition to drawing them. The shared signature component reduces duplicated work across apps and makes the sales order signing flow more responsive and easier to maintain.
Original PR description
Purpose ======= The goal is to avoid duplicate code between portal and sign (enterprise), and also to allow the user to use the signature mode 'auto' and 'load' in portal (before this commit only 'draw' was available in portal). The sales order signature (currently the only portal signature) has been changed to use this new code. This signature widget has been improved: Improved style: - better structure and use of BS classes - removed most of custom CSS - made it more responsive Changed code to follow guidelines, added JSDoc. Technically =========== New widget NameAndSignature common to portal and sign (enterprise). Reworked existing portal signature form to use new widget. Related to enterprise PR odoo/enterprise#3266 task-1894903
Odoo now standardizes selection field values so they must be stored as text rather than mixed data types. This improves consistency across accounting, inventory, import/export, language, and web-related flows, reducing ambiguity and future maintenance risk.
Original PR description
Task https://www.odoo.com/web#id=1911598&model=project.task&menu_id=4720
Stock movements now show the most relevant product description for receipts, deliveries, or internal transfers based on the type of operation. This helps warehouse and purchasing teams see useful notes at the right step, reducing confusion during handling and fulfillment.
Original PR description
Task link : https://www.odoo.com/web#id=1880135&action=327&model=project.task&view_type=form&menu_id=4720 Pad link : https://pad.odoo.com/p/r.5c9fae02edc22c1d7c63e8c492b24947 Purpose: It's show the description of receipts/deliveries/internal treansfer based on picking. This commit is related to task ID : 1880135 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
The signature flow was updated to use a shared signing component across the customer portal and Sign app, reducing duplicated work and making the experience more consistent. Business users should see a cleaner, more maintainable signature dialog with supporting updates to signature styling and contract signing tours.
Original PR description
Purpose ======= The goal is to avoid duplicate code between portal and sign (enterprise). Technically =========== New widget NameAndSignature common to portal and sign (enterprise). Reworked existing sign dialog to use new widget. Related to community PR odoo/odoo#29453 task-1894903
This update standardizes selection field values so they are stored and handled as text across affected business apps. It reduces inconsistencies and future compatibility issues without introducing a visible workflow change for most users.
Original PR description
odoo/odoo#29039
The barcode app now shows product descriptions in picking details, helping warehouse operators see planning notes or add useful handling instructions. This makes stock processing clearer and reduces the chance of missed context during operations.
Original PR description
Pad:https://pad.odoo.com/p/r.5c9fae02edc22c1d7c63e8c492b24947 Task:https://www.odoo.com/web#id=1880135&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
Resolved issues and error corrections
Point of Sale now keeps the product's normal tax when a selected fiscal position does not define a specific tax mapping. This prevents sales from being recorded without tax in that scenario, helping ensure more accurate checkout totals and tax reporting.
Original PR description
**Description of the issue/feature this PR addresses:** If a fiscal position is set in the point of sale and a product tax isn't mapped in it no tax will be applied for that product. **Current behavior before PR:** Taxes aren't applied in such case **Desired behavior after PR is merged:** Taxes default to the product defined ones if no map is set in the fp cc @Tecnativa -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes automated browser tests wait for the actual page to finish loading instead of sometimes mistaking a blank startup page as ready. It reduces rare, misleading test failures and helps keep development validation more stable.
Original PR description
cherry-pick of 03a88196525 In an HttpCase test, when the browser_js method is used, an optional javascript code can be used to check that the page is ready to execute the test. When no 'ready' code is given it defaults to check the 'document.readyState' status. In some rare cases (discovered by @Xavier-Do) this status is checked on the 'about:blank' page. As the page seems ready, the test code is evaluated and fails. With this commit, when no specific ready code is provided, the test will wait for a chrome devtools event that ensure the page is fully loaded before starting the test.
This fix removes duplicate field entries that appeared in website sales and eLearning configuration views after a previous update. It helps keep the interface cleaner and avoids confusion for users managing products or course channels.
This change prevents automated browser tests from checking readiness too early, before the intended page has loaded. It reduces rare, hard-to-reproduce test failures and improves confidence in build results without changing user-facing behavior.
Original PR description
In some rare case the _wait_ready was executed before the expected page was loaded This should be impossible since navigate_to should ensure that the url is loaded, but since this bug is difficult to reproduce, this fix should be enough waiting for a better solution. This bug was leading to some test failling, especially the test_01_js_interpretation (a + b + c === 6) Side note: The only way to reproduce this bug 100% of the time was to reboot, and only the very first build was failling. Killing chrome wasn't enough. Installing only test_assetsbundle was enough, using chrome version 71.0.3578.98 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 update fixes several issues in the website slides and learning content area, including broken statistics, PDF display problems, and unreliable like/dislike actions. It also improves access handling so users only see upload and tagging options when they have the right permissions.
Original PR description
Purpose of this merge it to merge various fixes and small improvements related to slides module. As an update of this module is pending fixing it before is quite helpful. This merge is linked to task ID 1933820 and PR #30553.
This update brings forward a set of fixes that improve day-to-day reliability in accounting, inventory, website sales, and project views. It prevents incorrect accounting references and tax totals, preserves manufacturing consumption data, restores missing messages/options, and improves compatibility on small screens and different browsers.
This update fixes misspellings in website snippet text. It improves the professionalism and clarity of website content for users and visitors without changing functionality.
Original PR description
opw-1931844 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 fixes a visual glitch that occurred when users liked or disliked slides on the website learning pages. The change makes the interaction look more reliable and polished for visitors using slide content.
Original PR description
Description of the issue/feature this PR addresses: Issue: https://youtu.be/1XKl4Zf016A 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