Monday, June 17, 2024
36 changes
10 changes
Enhancements to existing features
The subscription dashboard data has been refreshed to improve the information shown to sales teams. This helps users rely on more current and relevant dashboard views when tracking subscription sales performance.
The WhatsApp event integration is simplified so it no longer installs or depends on website event features. Event date information is handled directly by the event module, reducing unnecessary dependencies and cleanup while keeping messaging templates working.
Original PR description
RATIONALE Whatapp_event depends on website_event, which makes no sense. The only usage seems to be "whatsapp portal url" which is either * the portal url on some hardcoded models, if available; * the event website url (fuck it if not published by the way); * or contactus page because yolo All this could be moved into a website_whatsapp module or something like that anyway, to have a real whatsapp_event bridge module with only event. PURPOSE Remove dependency to website_event, to be event only. 'website_url' field existence can be checked with an "in", no need of a module just for that. Move "date_range" field from whatsapp to event, as anyway it calls a method already used in various templates. Move method itself on event model as it depends only on model. Rename field to "event_date_range" to match event dates fields naming. Remove dead code. Task-3768779
Resolved issues and error corrections
This fix prevents spreadsheet pivot insertions from creating an extra table unless the pivot is added directly from the pivot view. It avoids unintended table creation and keeps spreadsheet behavior consistent for users.
Original PR description
Creating a table should be done only when the pivot is inserted from the pivot view, not when it is inserted with the command "INSERT_PIVOT". Task: 3987435
Code cleanup and technical improvements
This update reorganizes how Odoo marks records' main attachments, moving model-specific logic to the relevant business records instead of the attachment layer. It improves code separation and batch processing, helping modules like invoice extraction, expenses, recruitment, documents, and localization behave more consistently.
Original PR description
Currently updating main attachment is done a bit through two methods * one model-based "_message_set_main_attachment_id"; * one attachment-based "register_as_main_attachment"; Attachment-based method is overridden in various addons to implement model specific behavior. This makes no sense: model-specific behaviors should be implemented on the right model. With this commit, "register_as_main_attachment" now correctly calls "_message_set_main_attachment_id", which is the method to override when adding model-specific behaviors. "register_as_main_attachment" still exists notably due to attachment viewer that takes an attachment as main record. It now delegates the model update to the model itself, leading to clearer code separation. Various calls and main attachment update are updated accordingly. Finally we also make 'register_at_main_attachment' batch-enabled. It groups attachments per model, allowing to benefit from cache. Task-3599245
Miscellaneous changes
Steps to reproduce : --------------------------- - Install pos and product barcodelookup - Go to settings disable variants - Try to scan a product having variants - Click on save button Issue : -------- Can't save and traceback comes. Cause : ---------- It was trying to set the variants but the variant field was not in the form as it's disabled from settings. Fix : ----- Create and set the attributes only if the variant is enabled. Forward-Port-Of: odoo/enterprise#64678 Forw
Original PR description
Steps to reproduce : --------------------------- - Install pos and product barcodelookup - Go to settings disable variants - Try to scan a product having variants - Click on save button Issue : -------- Can't save and traceback comes. Cause : ---------- It was trying to set the variants but the variant field was not in the form as it's disabled from settings. Fix : ----- Create and set the attributes only if the variant is enabled. Forward-Port-Of: odoo/enterprise#64678 Forward-Port-Of: odoo/enterprise#62991
1 change
Resolved issues and error corrections
Product Label Reports have been updated and are now being blocked from editing in Studio. These reports are primarily composed of automatically generated data rather than editable model fields, making them unsuitable for customization through the Studio interface. This change prevents users from attempting to modify reports that cannot be properly edited.
Original PR description
Since https://github.com/odoo/odoo/commit/1f438ca0e109b9e93c895824bd8342a2df170503 , the various product label reports have changed their name. Is still does not make much sense to edit them from studio, since they are composed of mostly generated data and not model fields. We thus blacklist them again. opw-3942356
A bad fw-port caused the xml to be changed wrongly. The test class was deactivated, so it got merged without being seen. runbot-68044 Forward-Port-Of: odoo/enterprise#64660
Original PR description
A bad fw-port caused the xml to be changed wrongly. The test class was deactivated, so it got merged without being seen. runbot-68044 Forward-Port-Of: odoo/enterprise#64660
Currently importing a DIAN document produces a blank invoice, because `_get_ubl_cii_builder_from_xml_tree` does not return anything, since the node `UBLVersionID` contains "UBL 2.1" rather than just "2.1" as in the other usual formats. Use the node `ProfileID` to treat the DIAN xml documents (using the `UBLVersionID` might have side effects if other specific formats also fill it with "UBL 2.1"). Forward-Port-Of: odoo/enterprise#64426
Original PR description
Currently importing a DIAN document produces a blank invoice, because `_get_ubl_cii_builder_from_xml_tree` does not return anything, since the node `UBLVersionID` contains "UBL 2.1" rather than just "2.1" as in the other usual formats. Use the node `ProfileID` to treat the DIAN xml documents (using the `UBLVersionID` might have side effects if other specific formats also fill it with "UBL 2.1"). Forward-Port-Of: odoo/enterprise#64426
A string domain is being used without being evaluated, leading to a traceback ### Steps to reproduce * Turn on debug mode * Go to the “Journal Entries” window action via Settings > Technical > Actions > Window Actions * Give any domain to the “Domain Value” field of the window action * Go to Tax Report via Accounting > Reporting > Statement Reports > Tax Report * Click the “Closing Entry” button * Click the “Post” button to post the closing entry you will run into the following tr
Original PR description
A string domain is being used without being evaluated, leading to a traceback ### Steps to reproduce * Turn on debug mode * Go to the “Journal Entries” window action via Settings > Technical > Actions > Window Actions * Give any domain to the “Domain Value” field of the window action * Go to Tax Report via Accounting > Reporting > Statement Reports > Tax Report * Click the “Closing Entry” button * Click the “Post” button to post the closing entry you will run into the following traceback: `IndexError: string index out of range` ### Fix The `account.action_move_journal_line` (Journal Entries window action) record was being reused for consistency. However, domains added to that record should not be propagated in this context. So in this case, the solution is to remove the domain from the returned action. opw-3903500 Forward-Port-Of: odoo/enterprise#64597
When deleting a line from an order, the preparation display wasn't updated. This commit fixes this issue. TaskId: 3976728 Community PR: https://github.com/odoo/odoo/pull/168694 Forward-Port-Of: odoo/enterprise#64241
Original PR description
When deleting a line from an order, the preparation display wasn't updated. This commit fixes this issue. TaskId: 3976728 Community PR: https://github.com/odoo/odoo/pull/168694 Forward-Port-Of: odoo/enterprise#64241
If the network is really slow, when you order a drink at the frontdesk. The visitor_id will not be set correctly, and you will have a traceback. Steps to reproduce: ------------------- * Install frontdesk * Enable "host selection" on the frontdesk station * Choose open kiosk * With the developper tool make the network slow, and use a mobile view * Click on check in, then try to order a drink > Observation: You get a traceback Why the fix: ------------ The `createVisitor` functi
Original PR description
If the network is really slow, when you order a drink at the frontdesk. The visitor_id will not be set correctly, and you will have a traceback. Steps to reproduce: ------------------- * Install frontdesk * Enable "host selection" on the frontdesk station * Choose open kiosk * With the developper tool make the network slow, and use a mobile view * Click on check in, then try to order a drink > Observation: You get a traceback Why the fix: ------------ The `createVisitor` function was not awaited during the setup of the page. But it is required to order the drink. opw-3889245 Forward-Port-Of: odoo/enterprise#62899