Odoo Changelog — 2024-07-22

Monday, July 22, 2024

4 changes · master

Bug Fixes(4)

Resolved issues and error corrections

[FIX] pos_l10n_se: refer to the new daily sales report template

Enterprisemasterpos_l10n_se

Fixes an installation error in the Swedish Point of Sale localization caused by an outdated daily sales report reference. Businesses using Swedish POS can install and use the module without being blocked by this report template issue.

Original PR description

### Steps to reproduce:
- Install pos_l10n_se
- the error `Element '<xpath expr="//div[hasclass('page')]">' cannot be located in parent view`

### Investigation:
- the reason for the error is that the `pos_daily_reports.xml` in `pos_l10n_se` refers to the no longer relevant `report_saledetails` template as it has been updated in [b3a6688a711a9229c7bfca60adf9594ad23a952d](https://github.com/odoo/odoo/pull/171383/commits)

#point-of-sale#sweden#reporting#installation

[FIX] website_studio: fix main tour at name_slugified step

PR #67080

Enterprisemasterwebsite_studio

A test tour in Website Studio was made more precise so it waits for the right page update before continuing. This reduces false failures in automated checks and helps keep releases stable without changing user-facing behavior.

Original PR description

in tour engine, we listen for mutations in the DOM in order to look for the element pointed to by the "trigger". If it is found, we execute run().
In this tour, the div[name='name_slugified'] element is found even before the textContent modifications have been made. To resolve the problem, simply be more precise in the trigger selector. It should be noted that we can therefore remove the first assertion in run() which amounts to doing exactly the same thing as the trigger.

#website#studio#testing#stability

[FIX] l10n_mx_reports_closing: addapt to new filter date

PR #65317

Enterprisemasterl10n_mx_reports_closing

This update restores the date filter behavior in the Mexican closing reports after a broader reporting change left this module out. Users working with these reports should now see date filtering work consistently with the rest of the accounting reports.

Original PR description

The commit 6fe06c57fa7d4bce9ad9a9df0f773678047b9d06 changed the way the date filter works in the account reports. During the change, it forgot to apply the change to this niche localisation module.

#localization#mexico#accounting#reports

[FIX] *: a bunch of domains and contexts which don't need to be eval'd

PR #66968

Enterprisemasteraccount_batch_paymentaccount_followupcrm_enterprisedata_cleaningdocumentsdocuments_hr_expensedocuments_projecthelpdeskindustry_fsmindustry_fsm_reportl10n_be_codaboxl10n_be_reportsl10n_be_sodal10n_cl_edil10n_mx_edil10n_pe_edimrp_account_enterprisesale_subscriptionsign

This update corrects several internal filters and default values across multiple Odoo apps so they no longer require unnecessary processing. It should make these screens and automated rules behave more consistently without changing day-to-day workflows.

### Steps to reproduce: - Install pos_l10n_se - the error `Element '<xpath expr="//div[hasclass('page')]">' cannot be located in parent view` ### Investigation: - the reason for the error is that the `pos_daily_reports.xml` in `pos_l10n_se` refers to the no longer relevant `report_saledetails` template as it has been updated in [b3a6688a711a9229c7bfca60adf9594ad23a952d](https://github.com/odoo/odoo/pull/171383/commits)

in tour engine, we listen for mutations in the DOM in order to look for the element pointed to by the "trigger". If it is found, we execute run(). In this tour, the div[name='name_slugified'] element is found even before the textContent modifications have been made. To resolve the problem, simply be more precise in the trigger selector. It should be noted that we can therefore remove the first assertion in run() which amounts to doing exactly the same thing as the trigger.