Wednesday, January 24, 2024
9 changes · 17.0
Resolved issues and error corrections
Users can now add a Project field in Studio without being stopped by an access error related to project stages. This improves the setup experience for teams using CRM, Projects, and Studio, especially for users who do not have project stage permissions enabled.
Original PR description
Steps to reproduce: - Install Studio, CRM and Projects. - Go to a lead and open the studio edit for it. - Now try to ad a new many2many field as "Project". We will receive an access error related to the "stage_id" field which will not be available for all the users unles we activate it in the project module, but by adding the groups to the field itself we can make it so it will ignore it when no it doesn't have the proper rights. note: for the existing databases we might need to clear the cache in order to make it work. opw-3603635
This update fine-tunes the customer portal after its redesign by improving spacing, headings, column layouts, and invoice presentation. It also fixes a small display issue where the message count appeared without a space, making portal pages clearer and more polished for customers.
Original PR description
# Portal layout fixes This PR fixes some issues within Portal, mainly about spacing, layout, and font-size. **Requires**: https://github.com/odoo/enterprise/pull/53383 ## Why do we introduce these changes We recently merged the portal redesign. While the redesign is almost done for every screen, we needed to fine tune some spacing or fix some layout issues. ## List of the different changes ### portal: - [x] Review the unconsistent use of hr tag - [x] Improve information architecture by fixing the typescale of the subtitles - [x] Remove the subtitle above the products table, improving the design of the invoice - [x] Fix an issue about the number of messages in the chatter missing a space task-3651084
This fix removes unnecessary EDI (Electronic Data Interchange) fields from internal transfer payment forms in Mexico. Internal transfers don't require SAT (tax authority) signatures, so displaying these fields was confusing. The change simplifies the user interface by hiding these fields when processing internal transfers.
Original PR description
An internal transfer must not be signed in the SAT. Odoo does not allow generating a EDI document in that process, but shows all the MX fields to EDI documents. Now, the fields are not in the view for internal transfers. Forward-Port-Of: odoo/enterprise#44420 Forward-Port-Of: odoo/enterprise#42569
This update corrects variable names in subscription payment tests to accurately reflect what they store. Previously, variables labeled as "payment_method" were actually storing payment tokens, which caused confusion with a new payment_method variable being added to the system. This fix ensures clearer code organization and prevents naming conflicts.
Original PR description
Many tests were giving the name `payment_method` to variables that are actually storing a payment token. This conflicted with the `payment_method` variable being added to `PaymentCommon`. See also: - https://github.com/odoo/odoo/pull/149833
This update fixes a visual glitch in the navigation menu's toggle arrow when using right-to-left languages like Arabic or Hebrew. The arrow now displays correctly in RTL mode, improving the user experience for international users.
Original PR description
Prior to this commit, the `o_menu_toggle` arrow had a glitch when the language was set on RTL. This commit adapts the arrow to fix this glitch. task-3548808 | Before | After | |--------|--------| |  |  | Forward-Port-Of: odoo/enterprise#51554
A translation string in the timesheet leaderboard feature was not properly exported for translation. This fix ensures the string is now available for translation into all supported languages, improving the user experience for non-English speaking teams.
Original PR description
This PR adds a missing translation string that was incorrectly not exported
This update removes an unused payment field that was incorrectly appearing in the Approval Types configuration form. The field had no functionality and was never used by the system, so hiding it cleans up the user interface and reduces confusion when managing approval types.
Original PR description
The field ´has_payment_method´ (approval_category.py) is not related to anything but is rendered in form view. Steps to reproduce: ------------------- * Open ´Approvals´ app * Select ´Configuration´ * Select ´Approval Types´ * Select any type Why the fix: ------------ The field is never used anywhere. opw-616042 Forward-Port-Of: odoo/enterprise#54237
A previous fix for spreadsheet tour data was incomplete because pivot formulas were trying to access records that don't exist in test environments. This update adds a dedicated test spreadsheet file that uses only actual available data, making the tests more reliable and preventing errors during automated testing.
Original PR description
The fix proposed in 5d19c678 was not thorough as the pivot formula present in the demo sheet will call `name_get` on given record ids that are likely not existing without the demo data (see [1]). This revision adds a dedicated spreasheet file that goes around that problem and limits the name_get calls to actual data (in this case, rely on the country_ids). [1] https://runbot.odoo.com/runbot/build/54397846 Forward-Port-Of: odoo/enterprise#54846 Forward-Port-Of: odoo/enterprise#51734
This update corrects an unintended spacing issue in the web editor where the "Slideout Effect" option was appearing indented below the "Colors" option in the Footer settings. The fix ensures that spacing is only applied between related options on the same row, preventing unrelated options from appearing misaligned.
Original PR description
Since [1] a margin is applied when another `o_we_user_value_widget` follows a color palette. Unfortunately this is also applied when the two elements are not on the same row. Because of this the "Slideout Effect" option below the "Colors" option of "Footer" looks like it is indented while it is unrelated to the color selection. This commit restricts that margin to elements that belong to the a `we-row`. [1]: https://github.com/odoo/odoo/commit/2f81c6ae68751d5f93c30aef822730ee04ead391 task-3696870 Forward-Port-Of: odoo/odoo#150614