Daily updates from Odoo
Navigate
Branch
Thursday, October 25, 2018
8 changes
New functionality added to Odoo
This change adds the portal discussion area to customer-facing documents such as invoices and sales orders, so portal users can communicate and share files directly from those pages. It also fixes visibility and display issues in the portal chatter, making the experience more consistent and less confusing.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: task link - https://www.odoo.com/web#id=37264&view_type=form&model=project.task&action=327&menu_id= -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
People with an upload share link can now submit files directly to document requests through public portal pages. This makes it easier to collect requested documents from external users without requiring extra account access or manual handling.
Original PR description
This merge implements the document request feature in the portal (share link public pages). Task: #1894421
Enhancements to existing features
Studio now shows and lets users update the technical name of custom fields from the sidebar, automatically updating related views when a field is renamed. This makes field management clearer and safer by warning users when manual renaming may affect custom code, while also improving Studio reliability when editing related records and reloading views.
Original PR description
Add the technical name of the current field on Studio's sidebar. The field is renamed on the model after changing this value. All views of the concerning model are updated with the new name. Rename automatically a field on the first label change in same session. Warn the user on manual renaming, in case of use of the name in code. Massive refactoring: - better initialization of Studio (permits to reload views); - better x2many management (use of a stack of states); - split model and view operations.
Resolved issues and error corrections
This fixes demo data in the website sales area so a sample service product uses a supported invoicing setup. It prevents an empty or confusing service policy selection when users view that demo product form.
Original PR description
Otherwise, the product is a service based on delivered quantity which is not a covered case by the service_policy field on product form view (the selection will be empty). Asked in Task-1859308 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The partner screen’s supplier invoice button now shows the correct total by including supplier credit invoices. This gives users a more complete and accurate view of supplier activity from the partner record.
Original PR description
[FIX] Partner form view supplier invoice smartbutton shows incorrect amount of invoices since it doesn't show supplier credit invoices. Description of the issue/feature this PR addresses: Smartbutton on partner shows incorrect amount of supplier invoices. Current behavior before PR: Supplier credit invoices are not shown. Desired behavior after PR is merged: All invoices are shown. Issue also present in new version. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Stock move screens will now show the detailed operations icon whenever the relevant inventory capabilities are enabled for the company. This makes the interface more predictable for users managing tracked products, multiple locations, or consignment stock.
Original PR description
…l group is active Stock moves show a detailed operations icon if the tracking, locations, or consignment allow to be configured. However it did so on a per move basis, only displaying it if the considered move has some of these features. This fix makes it that the "detailed operations" icon is always displayed if at least one group of group_tracking_lot, group_stock_multi_locations, or group_tracking_owner is active, regardless of what is set on that particular move. opw 1893106 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This update renames an internal website redirect field to avoid conflicts with reserved or commonly used field names. It helps improve system stability and maintainability without changing how users manage website redirects.
Original PR description
Part of odoo/odoo#27599 to rename fields named 'type' which may conflict
This change removes unnecessary automatic JSON parsing from a web utility used when reading view definitions. It makes attribute handling more predictable for downstream code, reducing complexity and the chance of inconsistent behavior without changing business features.
Original PR description
The utility function xml_to_json, which is mainly used by the views to parse their arch (from string to xml tree) had a peculiar behaviour: it tried to process some attributes as json. If by chance, these attributes are valid json, then they are replaced by their parsed value. It is difficult to say why it could be useful. Maybe this was done to prevent using pyeval many times later on. But if that is the case, it should be done by the view code and not the utility function (the view can precompute all attributes once). Also, this behaviour is annoying for code later in the chain, which needs to check if what it gets is an object or a string. With this change, attributes are always returned as string (at this point). Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr