Thursday, November 16, 2023
10 changes · 17.0
New functionality added to Odoo
Odoo now integrates a website scraper that automatically generates website content by analyzing existing websites. Users can leverage this feature in two ways: by starting a trial from odoo.com with a scrape request, or through the website configurator with a special parameter. This enhancement streamlines website creation by reducing manual content entry.
Original PR description
This commit integrated the website scrapper into Odoo. There are two ways to scrap a website. - The user comes from odoo.com and starts a trial with a scrap request. In this case, there is a todo.action to show a waiting screen. - The user is using the website configurator. There is a "secret" param to be able to scrap a website. See community PR: https://github.com/odoo/odoo/pull/126703 task-3339551
Enhancements to existing features
Portal pages like tickets and tasks were loading slowly because they were downloading oversized avatar images. This fix reduces the avatar file size from the largest version to a smaller one that still looks perfect on screen, significantly improving page load times especially for users with slower connections.
Original PR description
## Description Portal routes `/my/tickets` or `/my/tasks` were reported slow to load with many items. ## Analysis The avatars that are loaded are of too large sizes (encoded in base64) compared to their rendering size. `o_avatar` limits the dimensions to `1.7145em` (roughly `27px` on desktop), so it's useless to load `avatar_1024` for those image sources. This has a significant impact when the user has a slow connection, the server is hosted far away from the user, or the images used are of badly compressed (so each images takes a quite a few MiB). ## Fix Scan for all instances of the usage of `avatar_1024` on an `<img>` with the class `o_avatar` and reduce it to `avatar_128`. ## Reference opw-3470171 ## Linked PR https://github.com/odoo/odoo/pull/141877 Forward-Port-Of: odoo/enterprise#50557
Resolved issues and error corrections
This fix corrects how the Production Analysis report calculates the quantity of products produced. The report was using an outdated field that no longer accurately reflects completed quantities after production moves are finalized. The update ensures the report displays the correct production quantities to help you track manufacturing output accurately.
Original PR description
product_qty no longer represent done qty after the move is done. Change to use quantity to calculate quantity produced on the Production Analysis report.
This fix addresses an issue in the barcode scanning system for manufacturing orders where unpicked items were incorrectly being included during validation. The change adds test coverage to prevent this problem from recurring in the future.
Original PR description
Fixes same issue as odoo/odoo#141210 except for the MO flow in barcode. This commit simply adds a test to prevent this from happening again. COM PR: odoo/odoo#141797
This update fixes a technical issue that prevented users from opening the attendance app's gantt view in studio mode. The problem was caused by missing context information that affected date calculations. With this fix, users can now access and customize the gantt view in studio mode without encountering errors.
Original PR description
Prior to this commit, opening studio mode on the gantt view of the attendance app would lead to a traceback in get_gantt_data() This is due to the fact that start_date is not well assigned because context seems to be lost in studio mode.
This update improves UPS international shipping by automatically including commodity codes in shipping requests. This ensures that commercial invoices generated for international shipments now properly display commodity information for each item, making customs documentation more complete and accurate.
Original PR description
This commit adds the commodity code in the request for international shipping in UPS, so that the commercial invoice has it listed for every commodity. opw-3487614 Forward-Port-Of: odoo/enterprise#50687
This fix resolves a system error that occurred when viewing the Cost Analysis report in manufacturing operations after inventory revaluation. The error happened when multiple valuation records existed for the same scrap component. The fix ensures the Cost Analysis report displays correctly in all inventory scenarios.
Original PR description
Steps to reproduce the bug:
Steps to reproduce the bug:
- Configure Product Category All to use FIFO automated valuation
- Create two products that are storable with category All: “P1” and “C1”
- Set costs on the products:
- “P1”: 40
- “C1”: 25
- On”P1” create a BoM with Product B as the component
- Create an MO and scrap the component into negative quantities
- Complete the MO and view the Cost Analysis, it works.
- Purchase and receive the component product so that the negative inventory is revalued for the scrap move:
- in the PO -> C1 = 47
- Try to view the Cost Analysis
Problem:
Traceback is triggered:
Error when render the template
ValueError: Expected singleton: stock.valuation.layer(7, 11)
<span t-esc="scrap.stock_valuation_layer_ids.unit_cost"
t-options="{"widget": "monetary", "display_currency": currency}"/>
opw-3574431
Forward-Port-Of: odoo/enterprise#50692
Forward-Port-Of: odoo/enterprise#50534This fix corrects a bug where quality inspection worksheets completed from the manufacturing shop floor were always marked as passing, regardless of actual results. The system now properly validates worksheet checks through the correct quality check wizard, allowing quality steps to accurately fail when inspection criteria are not met.
Original PR description
Before this commit, Quality steps of type worksheet done from the mrp shop floor, always passed. This is because since #44696, worksheets should be accessed through the `action_open_quality_check_wizard` to properly perform the worksheet check.
This update fixes an issue with UPS shipment processing by ensuring that email addresses for both the sender and receiver are included when sending shipments. This improvement helps ensure that UPS has complete contact information for delivery notifications and customer communication.
Original PR description
This commit includes email address of the sender and the receiver in send_shipping request. opw-3487959 Forward-Port-Of: odoo/enterprise#48689
This fix ensures that operation instruction PDFs are now displayed in the shop floor view even when a Quality Control process is attached to the operation. Previously, the system would hide the PDF when QC was present, making it difficult for workers to access important instructions. Now PDFs will always be shown when available, regardless of QC status.
Original PR description
### Steps - Create a product with its bill of materials - Include an operation with a pdf as instruction - Create a MO and confirm. - Go to shop floor and you will see the link to pdf in the operation record. - Go to the BOM and add a QC on the the operation - Create another MO, confirm and go to shop floor ### Issue The pdf doesn't appear. ### Reason In the method which checks if we display the worksheetData ``showWorksheetCheck()``, it returns false when there is a Quality Control present. After discussing with @MGM, it should always return the pdf if it's present. opw-3509503 Forward-Port-Of: odoo/enterprise#49389