Wednesday, November 13, 2024
6 changes · master
Resolved issues and error corrections
Website page addresses can now keep non-ASCII characters instead of removing them. This helps users create and visit pages with localized or international URL text without broken or automatically replaced slugs.
Original PR description
Description of the issue/feature this PR addresses: Any non-ascii character is removed from URLs. Current behavior before PR: If trying to create or navigate to a page in the website using URLs containing non ascii characters, the non ascii characters are removed from the URL, and if the URL was composed completely of non ascii characters, it gets replaced with -1,-2,-3... Desired behavior after PR is merged: The non ascii characters do not get removed from the URLs, allowing users to create and browse pages with URLs containing non ascii characters --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change improves how Odoo finds text that needs translation when one translatable message appears inside another. It helps ensure more labels and messages are correctly included for translation, reducing missing translations in localized versions.
Original PR description
The current Babel library doesn't allow to extract gettext calls that are nested. Specifically:
- The Python extractor only supports a directly nested gettext call in another gettext call, like `_("Text %s", _("Nested"))`.
- The Javascript extractor doesn't supported nested calls at all.
In this commit, we patch both extraction functions, so they supported arbitrarily deep nested gettext calls, like e.g.
```python
_("Text %s", other_function(_("Deeply Nested")))
```
or the Javascript equivalent.
task-3940389This fixes a recent issue that caused automated checks to fail when web views handled monetary and date fields. It helps keep the user interface stable and prevents disruptions from incompatible field types.
Original PR description
Build errors in click all since #183882: see: https://runbot.odoo.com/runbot/build/70474087 build-error: 106152
A field used for links in the base system profiling area now uses the right format so URL links display and behave correctly. This helps users open related links reliably without changing business workflows.
Original PR description
This commit, change the field type from text to char to correctly use the url widget.
The stock forecast now correctly recognizes inventory stored in sublocations, such as warehouse shelves, when checking whether an order can be fulfilled. This prevents available stock from being incorrectly shown as unavailable, helping users reserve products accurately from the forecast view.
Original PR description
### Steps to reproduce: - Enable multisteps route in the settings - Create a storable product P and put 10 units in WH/Stock/Shelf - Create and confirm an SO for 1 unit of P - Go to the associated…
### Steps to reproduce: - Enable multisteps route in the settings - Create a storable product P and put 10 units in WH/Stock/Shelf - Create and confirm an SO for 1 unit of P - Go to the associated delivery and change the Source Location to WH/Stock/Shelf - Back to the SO, click on the chart icon > view forecast - Unreserve the 1 unit currently used by your picking ### Issue: While you have 10 units in WH/Stock/Shelf perfectly suitable to fulfill the demand of the picking, instead of displaying a line allowing you to reserve the 1 unit, you have a line telling you that the qty is "not available" -1 unit associated with the SO. ### Cause of the issue: Currently, in the `_get_report_lines` used to compute the forecast datas the `currents` dict used to compute both the reserved and the on hand quantity only updates the quantity of the warehouse if the location belongs to the warehouse: https://github.com/odoo/odoo/blob/7e8afedda2cdc5ec64c1f022c116d56ec90c907a/addons/stock/report/stock_forecasted.py#L330-L336 As such, 0 units are considered to be available in these locations and nothing can be taken from stock for these moves: https://github.com/odoo/odoo/blob/7e8afedda2cdc5ec64c1f022c116d56ec90c907a/addons/stock/report/stock_forecasted.py#L243-L249 opw-4220367 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes how certain money and date fields are handled in approval requests and rental sales orders. It helps ensure users see and enter these values consistently, reducing confusion and potential mistakes in day-to-day workflows.