Wednesday, July 31, 2024
7 changes · 17.0
Resolved issues and error corrections
Odoo now lets teams hide the time portion in date-and-time fields when it is not needed. This makes forms cleaner and helps users focus on the relevant date information without extra detail.
Original PR description
Before this commit: - There was no option to hide the time part from the datetime widget. After this commit: - A 'show_time' option is added to the datetime widget. When set to false, it hides the time part from the datetime. Enterprise PR: https://github.com/odoo/enterprise/pull/67258 Task-3698841 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures that fields using the HTML widget show formatted content instead of visible HTML tags when viewed in read-only mode. It prevents confusing display issues in business documents such as sales quotations when views are customized.
Original PR description
…field Steps to reproduce ================== - Go to sales - Open a quotation - Using the debug tools, edit the view so that the x2many name field uses the html widget: `widget="html"` instead of the section_and_note_text widget => In readonly mode, the html tags are displayed as is Cause of the issue ================== Since the field is not of type html, `this.props.record.data[this.props.name]` isn't wrapped in a markup instance. This means that the output of `t-out="markupValue"` is the escaped html value Solution ======== If the value isn't already a markup, wrap it in one. opw-4061739
Point of Sale receipts now use wider print margins to prevent the left edge from being cut off on some external printers. This makes printed receipts more reliable for businesses using non-standard printer setups while keeping the change small and focused.
Original PR description
Steps to reproduce: - Sell any item in POS (Pick item > Payment > Bank > Validate) - Print receipt with 0 margin (current default) on external printer - Leftmost part of the receipt is truncated Why is this an issue: Frankly, since this issue only occurs on external printers and we haven't had complaints from people using Odoo supported devices (by that I mean connected to an IoT box) this could be considered not to be our problem. The receipt margins have been made smaller since 15.0 though so there could be more people with this issue. I've tried printing one here and it is very slightly cut off, but that might depend on the device. What this fix does: This fix aims to reestablish margins as close to the way they were in 15.0 as possible (Don't want to go overboard and cut off the right) As it was in this commit b29c4a6113a002528aeed1fa59e823172bfce841 opw-3996929 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Inventory settings page now points users to the correct documentation for packaging and storage locations. This avoids dead or incorrect help links, making it easier for users to find guidance when configuring inventory features.
Original PR description
Update links to Packaging and Storage Location documentation on Inventory > Settings > Configuration page
This fix prevents an error page when someone tries to download tickets for an event that has already been deleted. Instead of triggering a system traceback, the ticket download flow now handles the missing event more safely, improving reliability for users and support teams.
Original PR description
When the event is deleted and the user tries to download tickets for that event, a traceback will appear. Steps to reproduce the error: - Go to Website > Events > Open any event > register > confirm…
When the event is deleted and the user tries to download tickets for that event,
a traceback will appear.
Steps to reproduce the error:
- Go to Website > Events > Open any event > register > confirm registration of the ticket
- Go to Events > Open that event > delete attendees > delete that event
- Download tickets of that event
Traceback:
```
TypeError: unsupported operand types(s) or combination of types: 'str' and 'event.event'
File "odoo/http.py", line 2248, in __call__
response = request._serve_db()
File "odoo/http.py", line 1823, in _serve_db
return self._transactioning(_serve_ir_http, readonly=ro)
File "odoo/http.py", line 1843, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 134, in retrying
result = func()
File "odoo/http.py", line 1821, in _serve_ir_http
return self._serve_ir_http(rule, args)
File "odoo/http.py", line 1828, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 1966, in dispatch
return self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 756, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/event/controllers/main.py", line 50, in event_my_tickets
if not consteq(tickets_hash, hash_truth):
```
https://github.com/odoo/odoo/blob/7b9df7c95c5f6a96d4d00c5d64e394141124752b/addons/event/controllers/main.py#L50 Here, when user deletes the event, 'event_sudo' will be empty,
So, eventually 'hash_truth' will be empty.
So it will lead to the above traceback.
sentry-5499927956
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update ensures the relevant currency is active before an automated landed costs test runs. It helps prevent false build failures and keeps validation of multi-currency landed cost behavior reliable.
Original PR description
The aim of this commit is to fix runbot build error. Before the commit: The test could fail if the EUR currency was inactive After the commit: The test activate the currency first --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale accounting entry descriptions are now prepared for translation, so users can see clearer localized text in generated accounting records. This helps businesses using Odoo in multiple languages keep their POS financial documents understandable and consistent.
Original PR description
closes: #174647 Forward port of #174511 (Original PR in V16) CC : @vlst-odoo Note : i only cherry-picked the change of the .py file. I think that it was not a good idea to change the pot / po files in the original PR because when we forward-port the PR it generates conflicts on each version. This one should be OK against 17.0 (+ saas + master versions)