Tuesday, January 23, 2024
29 changes
Resolved issues and error corrections
This fix enables Odoo to properly process emails that use the Hebrew character encoding format "iso-8859-8-i". Previously, emails from customers using this encoding would fail to process. The fix adds support for this encoding variant, which uses the same character set as the standard Hebrew encoding but differs only in text display direction—a distinction that doesn't affect how Odoo processes the email content.
Original PR description
One of our customers is receiving emails with headers and attachments encoded using the "iso-8859-8-i" charset instead of "iso-8859-8" which is natively supported by Python. Both encoding are using the same character set[^1] and only differ in the way the text is rendered on screen[^2][^3] which is not relevant for Python. Add an alias for iso-8859-8-i so that the emails that this customer receive stop failing in Odoo. Note that there is a PR opened on CPython for exactly that, see [bpo18624](https://bugs.python.org/issue18624). [opw-3653210](https://www.odoo.com/web#id=3653210&cids=1&model=project.task&view_type=form) [^1]: https://encoding.spec.whatwg.org/#legacy-single-byte-encodings [^2]: <data:text/html;charset=iso-8859-8,hello%20%E0%E1%E2%E3> [^3]: <data:text/html;charset=iso-8859-8-i,hello%20%E0%E1%E2%E3> Forward-Port-Of: odoo/odoo#150344 Forward-Port-Of: odoo/odoo#149827
Users were unable to exit inline code blocks in the text editor because pressing backspace would delete the formatting marker, trapping them inside the code block. This fix allows users to navigate out of inline code blocks using arrow keys, improving the editing experience and making the editor more intuitive to use.
Original PR description
**Current behavior before PR:** If we entered text within a inline-code block and pressed the backspace key,the zero-width space (zws) at the end of the inline-code block would be deleted. Consequently, there was no way to exit the inline-code block. **Desired behavior after PR is merged:** Users can now navigate out of the inline-code block by using the right or left arrow keys when inside an inline-code block. task-3613340 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#145936
Fixed a technical error that prevented users from generating the BIR 2307 Report when creating vendor bills with certain tax configurations in the Philippines localization module. The issue occurred when processing bills with lines that had no product assigned but included Philippine taxes, causing the report generation to fail with an error.
Original PR description
### Steps to reproduce * install `l10n_ph` * switch to a Filipino company * create a vendor bill with a line with no product and a tax that has a "Philippines ATC" defined (ex: 5% WI010 - Prof Fees) * attempt to generate the `BIR 2307 Report` through the action menu You should be met with a traceback. opw-3683037 Forward-Port-Of: odoo/odoo#150380
This update fixes a compatibility issue with the Point of Sale system on newer server versions that use NetworkManager instead of the older wpa_supplicant tool for network setup. The system now automatically detects which network management tool to use based on the server version, ensuring the Point of Sale terminals can properly connect to WiFi networks without conflicts.
Original PR description
Above IOT Image 23.09, the Debian "bookworm" distribution is used. This distribution uses the NetworkManager configuration tool suite to setup the network. This break the code used until 23.09 included. In this PR, the code check the Image version and switch to NetworkManager if necessary. Before: Conflict with wpa_supplicant management in Debian "bookworm" Now: The network management tool is choosen in relation to image version mool --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#150473 Forward-Port-Of: odoo/odoo#149970