Friday, August 9, 2024
5 changes · saas-17.4
Resolved issues and error corrections
Users can now insert images from valid web links even when the link does not end with a typical image file extension. The editor checks whether the link actually loads as an image, reducing false rejections and making image insertion smoother.
Original PR description
Description: Previously, when attempting to insert an image via URL, the system incorrectly flagged certain valid image URLs as unsupported due to a limited validation method based solely on file extensions. This resulted in users being unable to insert valid images into the editor even when the URLs contained valid image content. This PR addresses the problem by enhancing the URL validation process on the client side. The system now checks whether the URL actually loads an image when used as an image source. In cases where this method fails the URLs are validated based on their content type. Only if both validation methods fail will the URL be considered invalid for image insertion. Desired behavior after PR is merged: Users are now able to successfully insert images from valid URLs. task-3323862 Co-authored-by: Deependra Solanki <deso@odoo.com>
This fix adds missing styling needed for full-screen views launched from Point of Sale. It helps prevent display issues such as incorrect scrolling in booking management Gantt views, making related workflows easier to use.
Original PR description
In 38d741f6b1d9ba2911632185bd81bf6cb6d98383 we added the functionality to render fullscreen actions, but failed to include the appropriate css assets. One of the impacts of this is the incorrect scrolling of the gantt view for booking management. In this commit we add the correct css assets. Task: 4106537 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures Odoo only includes readable, relevant action information when embedded actions are present. It prevents failures caused by unsupported date/time data being saved in JSON, helping scheduled bank synchronization and invoice send-and-print flows run reliably.
Original PR description
With the recently added embedded actions with commit https://github.com/odoo/odoo/commit/f983703dfa3c5102fa818523ae419a70cc4b5230, added below line where it returns non related fields to actions,…
With the recently added embedded actions with commit https://github.com/odoo/odoo/commit/f983703dfa3c5102fa818523ae419a70cc4b5230, added below line where it returns non related fields to actions, which may generate an error. https://github.com/odoo/odoo/blob/ebf6da8d24c72a391113310e66285ded1f5fc9b5/odoo/addons/base/models/ir_actions.py#L232-L236 ___ Currently there are two scenarious where error occurs: 1 In the `account_online_synchronization` module, a below exception was generated when cron `Account: Journal online sync` run. 2 While clicking send and print Steps to produce: - Install l10n_hu_edi - switch to the new company - Create an invoice with a line - Confirm it and click send and print ___ ERROR: ``` TypeError: Object of type datetime is not JSON serializable ``` This exception was generated because [code](https://github.com/odoo/enterprise/blob/b491d3fa529115229fcce58500f742a992a7f2e5/account_online_synchronization/models/account_online.py#L423 ) tries to store a dictionary of action with a datetime object in the json field `connection_state_details`, but when data is converted to cache at [4]-https://github.com/odoo/odoo/blob/ebf6da8d24c72a391113310e66285ded1f5fc9b5/odoo/fields.py#L3346 , it throws an exception because `json.dumps` does not support datetime objects. This commit will resolve the issue by following: 1. Override the `_get_action_dict` in 'ir.actions.act_window'. 2. In overridden '_get_action_dict' it just adds readable embedded field data when `embedded_action_ids` is available. sentry-5655598227
Self-ordering point-of-sale orders now receive the correct sequence information when created. This ensures order tracking numbers increment as expected, helping staff and customers follow orders reliably.
Original PR description
Before this commit: ==================== The order tracking number did not increment because the sequence number was not passed when creating an order from the UI. After this commit: =================== The order tracking number now increments correctly, as the sequence number is properly passed when creating an order. task- 4104325
This fix makes financial report annotations load more efficiently and reliably. It prevents errors during period comparisons and ensures annotations correctly include relevant parent-company fiscal years.
Original PR description
During the development of the new annotation system, some comments were left on the side to implement the annotation systems as fast as possible, this PR takes care of two of those comments. Each in a separate commit. task-4045835