Wednesday, February 19, 2025
3 changes · saas-17.4
Resolved issues and error corrections
This fixes a website issue where SEO notifications could fail to appear after a page was created, published, edited, and saved without reloading. The change helps editors receive the right SEO guidance at the right time, while avoiding unnecessary notifications.
Original PR description
**Steps to Reproduce:** 1. Create a new page using the **"New"** button and save it. 2. Publish the page using the **"Publish/Unpublish"** button. 3. Enter **Edit** mode (without reloading the page), update the page content, and save. 4. The SEO notification does not appear. **Reason for Change:** This PR fixes an issue where SEO notifications were not displayed after creating, publishing, editing, and saving a page. The fix ensures SEO data includes the website's publish status, which was previously missing in [1](https://github.com/odoo/odoo/commit/45ea6e4a4a5c8e314b110a45198fbe3d57bb996e). This update guarantees that the notification appears only when necessary. task- 4046471
Installing the Field Service sales report module no longer fails if the default Field Service product was previously deleted. This avoids a blocking setup error and lets businesses add the reporting feature without restoring deleted sample or default product data first.
Original PR description
Currently a `ParseError` is arising when the user installs the `industry_fsm_sale_report` module after deleting `Field Service` product from the products.
Steps to reproduce:
---
- Install the `industry_fsm_sale` module
- Delete `Field Service` from products
- Now install `industry_fsm_sale_report` module
Traceback:
---
```
Exception: Cannot update missing record 'industry_fsm_sale.field_service_product'
ParseError: while parsing /home/odoo/src/enterprise/saas-18.1/industry_fsm_sale_report/data/product_product_data.xml:4, somewhere inside <record id="industry_fsm_sale.field_service_product" model="product.product">
<field name="worksheet_template_id" ref="industry_fsm_report.fsm_worksheet_template"/>
</record>
```
This commit solves the above issue by using `forcecreate="False"` to bypass record creation if it violates checks.
sentry-5731062091Payroll Officers can now see and use the "Report in Next Payslip" button on employee expenses. This fixes an access issue where only accountants could perform this payroll-related action, helping payroll teams process reimbursements without unnecessary handoffs.
Original PR description
Only the accountant was able to see and use the 'Report in Next Payslip' button, this commit enables the Payroll Officer to use it. task-4481091