Daily updates from Odoo
Thursday, July 11, 2019
9 changes
Enhancements to existing features
The stock module’s automated tests were updated so they can run successfully even when demo data is not installed. This improves reliability for deployments and development environments that use clean, production-like configurations without sample data.
Original PR description
Do not require the demo data to be able to run (and pass) the tests of stock. task-2024202
This improvement adds a new way to show product variant attributes as descriptive information rather than variant choices. It makes product pages and comparison views easier for shoppers to read by displaying selected attribute values together in a simple comma-separated row.
Original PR description
Description of the issue/feature this PR addresses: - Task link - https://www.odoo.com/web#id=1912579&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.5b65abecd81de14fed4e7251afcb6bae -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update simplifies the action dropdowns in many Odoo screens by shortening labels, removing duplicate or misplaced actions, and showing options only where they are relevant. Business users should see clearer, less cluttered menus and a more consistent experience across sales, accounting, CRM, HR, inventory, manufacturing, and related apps.
Original PR description
PURPOSE The 'action' dropdown on the controlpanel is starting to get messy. Their labels are sometimes too long/repetitive. Some actions only make sense in formview, some in listview, some in both.…
PURPOSE The 'action' dropdown on the controlpanel is starting to get messy. Their labels are sometimes too long/repetitive. Some actions only make sense in formview, some in listview, some in both. Some actions should be stat buttons. Here are some of the 'guidelines' I've followed to clean those actions: If the action already has a dedicated button in the formview, do not display it in the formview action dropdown. Action labels always start with a verb. Former actions that redirected to records are changed to stat buttons SPECIFICATION The following drive file defines all the changes to be done on actions: https://docs.google.com/spreadsheets/d/1G0AtYs6VIXFz1vG32IoL457c_oy-OCXF9Tv19vLQdz8/edit?usp=sharing The actions are grouped by object, which are grouped by product owner. The ones in green are to be kept. The 'where' column specifies whether they should be shown in formview, listview, or both. The ones in red are to be removed or moved somewhere else (stat button, menu item). When an action is removed, check whether the action it is calling is used somewhere else. If it is not the case, remove it as well (clean the code). Linked to task ID 1984526
This update improves invoice and journal entry handling by preserving due dates more reliably when no payment terms are set. It also warns users before validating empty invoices or accounting entries, helping reduce accidental or incomplete postings.
Original PR description
* remove _onchange_invoice_date_due as it is superseeded by _onchange_recompute_dynamic_lines * change invoice_date_due only if not set and if there is no payment term, it was erased and set to invoice_date_due if we did not set invoice_date_due before posting * raise a warning if we validate an empty move/invoice -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update refines how content is shown while editing website pages, making it easier for users to see and manage page elements in the editor. It should improve the page-building experience without changing the published website behavior.
Original PR description
**TASK**: [34646](https://www.odoo.com/web#id=34646&view_type=form&model=project.task&action=333&active_id=974&menu_id=4720)
Users can now search archived products by barcode when a barcode conflict prevents creating or updating another product. This makes it easier to identify which inactive product already owns a barcode and resolve the issue without exporting or manual investigation.
Original PR description
**Allow searching by barcode for the archived product** When you create a product with a barcode that has already been taken by some other product(which is archived), you will get an error that says…
**Allow searching by barcode for the archived product** When you create a product with a barcode that has already been taken by some other product(which is archived), you will get an error that says that a barcode can only be assigned to one product. Now, if you filter all the archived products and then search with the same barcode, you will not find the other product that has the same barcode as your new product. Hence, the user is unable to search as to which other product(archived) has the same barcode. Steps to reproduce: - Someone archives **Product A** with barcode: 12345 - You try to a new **Product B** using barcode 12345 - It raises an error that a product with that barcode already exists - If you try to lookup **Product A** by barcode it won't appear on archived products - If you try to export all the archived products, **Product A** won't export the barcode. - So we can't create **Product B** using barcode 12345, but we cant neither find the product that has this barcode. After this PR is merged, it will allow the user to search for products by barcode even if they are archived. **_Note: The barcode field will still remain disappeared in the template on an archived product. This PR is just for allowing to search on an archived product._** Task Link: https://www.odoo.com/web?#id=1978559&action=327&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.1118e013e6c395157a91b17029dcea74 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
IoT users can now manually enter a network range to scan instead of being limited to the browser's current network range. This makes it easier to discover and connect IoT devices located on a chosen subnet, improving setup flexibility for businesses with more complex networks.
Original PR description
Before this commit it was impossible to scan a specific range. Only the same range that the browser. Now we can add manually a range to scan. Task: 1892415
This update removes outdated internal coding patterns from several Odoo Enterprise apps and reports. It helps keep the platform easier to maintain and ready for future upgrades, with no expected change to day-to-day user workflows.
This update simplifies the action dropdowns across several Odoo apps by shortening labels, hiding actions where they are not relevant, and moving some record-opening actions to clearer stat buttons. Users should see less clutter and more consistent wording when working in accounting, HR, sales, helpdesk, manufacturing, and related screens.
Original PR description
PURPOSE The 'action' dropdown on the controlpanel is starting to get messy. Their labels are sometimes too long/repetitive. Some actions only make sense in formview, some in listview, some in both.…
PURPOSE The 'action' dropdown on the controlpanel is starting to get messy. Their labels are sometimes too long/repetitive. Some actions only make sense in formview, some in listview, some in both. Some actions should be stat buttons. Here are some of the 'guidelines' I've followed to clean those actions: If the action already has a dedicated button in the formview, do not display it in the formview action dropdown. Action labels always start with a verb. Former actions that redirected to records are changed to stat buttons SPECIFICATION The following drive file defines all the changes to be done on actions: https://docs.google.com/spreadsheets/d/1G0AtYs6VIXFz1vG32IoL457c_oy-OCXF9Tv19vLQdz8/edit?usp=sharing The actions are grouped by object, which are grouped by product owner. The ones in green are to be kept. The 'where' column specifies whether they should be shown in formview, listview, or both. The ones in red are to be removed or moved somewhere else (stat button, menu item). When an action is removed, check whether the action it is calling is used somewhere else. If it is not the case, remove it as well (clean the code). Linked to task ID 1984526