Tuesday, September 3, 2024
6 changes · saas-17.4
Resolved issues and error corrections
Saving a map block on an event registration page no longer triggers an error that blocks further editing. This helps website editors update event pages reliably without losing the ability to continue making changes.
Original PR description
In the register page of the events, when you add a map block, and save it, you'll get an UncaughtPromiseError. To Reproduce on Runbot: 1. Go to the events page. 2. Click on one of the events. 3. Go to /register page 4. Go to Editor and add a map block 5. Save it Upon saving, you'll encounter the error, and further cannot make any edits. The issue is due to calling _manageIframeSrc on the element where there is no iframeEl defined yet. So, we'll add the iframeEl first and call _manageIframeSrc. opw-4104300
Fixes an error that occurred when adding and saving a map block on an event registration page. This prevents the editor from getting stuck, allowing website managers to continue updating event pages normally.
Original PR description
In the register page of the events, when you add a map block, and save it, you'll get an UncaughtPromiseError. To Reproduce on Runbot: 1. Go to the events page. 2. Click on one of the events. 3. Go to /register page 4. Go to Editor and add a map block 5. Save it Upon saving, you'll encounter the error, and further cannot make any edits. The issue is due to calling _manageIframeSrc on the element where there is no iframeEl defined yet. So, we'll add the iframeEl first and call _manageIframeSrc. opw-4104300
This fixes an issue where customer loyalty point balances were missing from the Point of Sale customer list. Staff can now see loyalty points when selecting a customer, helping them apply loyalty benefits correctly during checkout.
Original PR description
Problem: The loyalty points of customers are not displayed in the partner list Steps to reproduce: - Install "point_of_sale" app and "pos_loyalty" module - Click on Customer - The loyalty points are not shown Solution: The content of the mutex of checkMissingCoupons is executed only once at the beginning of the order. "this.models["loyalty.card"]" contains all the loyalty cards and then allow to fetch them. In previous version, the coupons were loaded with json which doesn't exist anymore. opw-4035387 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoices created from Point of Sale orders now use the correct product name information. This prevents missing product names in generated PDF invoices, improving invoice clarity for customers and staff.
Original PR description
Problem: The wrong field was used for the product name on the invoice, causing some or all product names to be missing in the generated PDF. Steps to reproduce: - Go to PoS. - Add some products. - Generate an invoice for a customer during checkout. - The invoice (PDF) is missing some or all product names. opw-4140603 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue that could prevent customers from connecting Instagram accounts to Social Marketing when an Instagram post, such as some videos or Reels, has no media URL. The app now handles the missing value safely so users can continue the connection process without being blocked.
Original PR description
Issue: When clients attempt to connect their Instagram account to the Social Marketing app, an error occurs if their account contains a post without a media_url value (in our case, this issue involved a video). Steps to Reproduce: It's quite difficult to reproduce because, according to my research, it doesn't happen with all videos. This issue might be related to the fact that new Instagram videos have become Reels. I tried with a test Instagram account, but I couldn't replicate this case. Fix: Use a default empty string instead of None (via get). This prevents the user from encountering the error and getting blocked. opw-4085729 opw-4141505 opw-4141479 opw-4105134 opw-4114002
This update ensures the “In Payment” invoice status is only shown when the full Accounting app is installed, avoiding confusion for users who only handle invoicing. It also limits several accounting report menus to users with the right permissions, so people only see reports relevant to their role.
Original PR description
The `In Payment` state should only apply when `accountant` is installed. Users with Invoicing (enterprise) currently reach this state even though they might not do reconciliations. Reporting menus visibility restricted to access rights - Unrealized currency gains/losses (Accountants: readonly) - Budget report (Accountants: readonly) - 1099 Report (Accountants: readonly) - Follow-up Reports (Invoicing & Banks: basic) Task-4130326