Odoo Changelog — 2022-09-01

Thursday, September 1, 2022

5 changes

Bug Fixes(5)

Resolved issues and error corrections

[FIX] l10n_be_intrastat: make export function public

Enterprisemasterl10n_be_intrastat

The Belgian Intrastat XML export button has been corrected so users can export reports without encountering an access error. This restores the expected export workflow for Belgian reporting and avoids manual workarounds.

Original PR description

Currently, using the xml export button on the Belgian results in an
access error because the function it is attempting to call is a private
method.

The fix removes the underscore from the begining of the method and
updates the name of the function in the place where it is called.

#belgian-intrastat#xml-export#reporting

[FIX] documents: fix traceback in search panel

PR #30971

Enterprisemasterdocuments

A bug in the Documents search panel was fixed after an internal service change caused an error in some searches. This helps users browse and filter documents without encountering an unexpected crash.

Original PR description

The API of the orm_service got changed during the development of the
documents B2B, unfortunately it made one of the function cause a
traceback.
This was uncaught since the call is mocked during the tests and does not
do the exact same error checking as the python server.

#documents#search#stability

[FIX] web_studio: fix file load order for list renderer patch

PR #30957

Enterprisemasterweb_studio

This fixes the load order for a Studio list view adjustment so it is applied at the right time. It helps prevent inconsistent behavior in list views when Studio customizations are active.

#studio#list views#reliability

[FIX] account: upload buttons on Accounting Dashboard are disabled

PR #30815

Enterprisemasteraccount_bank_statement_importl10n_be_sodaMEDIUM

The Accounting Dashboard upload buttons now work again after being disabled during a recent interface migration. This lets users upload bank statements and related accounting files directly from the dashboard as expected.

Original PR description

OWL disables view buttons that are missing attributes.
These buttons used legacy javascript, and were omitted from the accounting owl migration.

Activate those buttons.

#accounting#dashboard#upload

[DRAFT][FIX] website_event_track_gantt: put the field back where they were

PR #30856

Enterprisemasterwebsite_event_track_gantt

This fixes an issue where an unexpected track button could appear instead of the event stage in the event planning view. The change ensures the correct field is targeted so event organizers see the intended stage information in the right place.

Original PR description

Currently, the strange track button appears instead of the stage in the event.
This is because the "website_event_track model" had only one track_count field
before commit1, but after commit1, the "mass_mailing_event_track" model added
a "track_count" field before the stage of the event view. As a result, the
"website_event_track_gantt" model event view will not find the correct position
if it tries to replace the fields with track_count.

This commit solves the above problem by targeting the track_count field inside
the "sheet" of the parent view.

commit1 - https://github.com/odoo/odoo/commit/0501bbd62e517f6c215d9e7e36d61747c7f5816b

task-2964291

#events#planning#display-fix

Currently, using the xml export button on the Belgian results in an access error because the function it is attempting to call is a private method. The fix removes the underscore from the begining of the method and updates the name of the function in the place where it is called.

The API of the orm_service got changed during the development of the documents B2B, unfortunately it made one of the function cause a traceback. This was uncaught since the call is mocked during the tests and does not do the exact same error checking as the python server.

Currently, the strange track button appears instead of the stage in the event. This is because the "website_event_track model" had only one track_count field before commit1, but after commit1, the "mass_mailing_event_track" model added a "track_count" field before the stage of the event view. As a result, the "website_event_track_gantt" model event view will not find the correct position if it tries to replace the fields with track_count. This commit solves the above problem by targeting the track_count field inside the "sheet" of the parent view. commit1 - https://github.com/odoo/odoo/commit/0501bbd62e517f6c215d9e7e36d61747c7f5816b task-2964291