Daily updates from Odoo
Navigate
Branch
Friday, March 23, 2018
13 changes
Enhancements to existing features
Website shop managers will now see more clearly when a product is unpublished, reducing the chance of confusing unavailable items with live products. The e-commerce product list view also removes publish controls to keep the experience consistent across view modes, while bulk publishing is expected to be handled from the backend in the future.
Original PR description
This commit attempts to make it more obvious when a product is not published. It also removed the publish management from the e-commerce list view in order to have the same layout philosophy for the 2 view modes. Note that there should be a publish management in the back end list view in the future so it won't really remove the functionnality (fast publishing multiple products). task-44005 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 web notification component has been separated into its own template and styling files. This makes it easier to reuse notifications outside the main Odoo backend, supporting more flexible future interface development without changing visible behavior for users.
Original PR description
Like Dialog, the Notification Manager can actually be used independently of the backend - except for its CSS & Templates which where shared with the rest of the web client. This commit extracts the templates to their own file and leverage the lazyloading mechanism introduced in 5f1ef09. The less code is put in its own file as well, but remains in assets_backend at the moment - if someone needs it in frontend assets, it will need to be added specifically. This allows for a more versatile JS Framework that can more easily be used to develop something else than the official web client, for example. 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 sales confirmation button label has been updated from "Confirm Sale" to "Confirm Order". This makes the wording clearer and more consistent for users working with sales orders.
Original PR description
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
This update adds a direct documentation link in the Authorize.Net payment configuration area. It helps users find setup guidance faster, reducing friction when configuring online payments.
Original PR description
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
This update expands customer rating capabilities across projects, tasks, and issues, making it easier to collect feedback and monitor satisfaction. It adds dashboards, automated rating emails, clearer public rating views, and integration with sales service customers so teams can better track service quality.
Original PR description
Task: https://www.odoo.com/web#id=22054&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
This update corrects unclear English and removes an unnecessary guideline in the Sales Management user tour. It is a minor wording cleanup that helps users see clearer instructions without changing business behavior.
Original PR description
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
Resolved issues and error corrections
Customers can no longer change their VAT number or company name in the portal once sales orders or invoices already exist for their account or related company. This helps preserve consistency on commercial and accounting documents and reduces the risk of incorrect business records.
Original PR description
…/invoices This commit prevent VAT edition if an user has already at least one SO or one invoice on his account. Any module could override this feature to add their own condition to prevent VAT edition. task-33088 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
Sales order reports now show payment terms only once, matching the behavior of invoices. This reduces confusion for customers and keeps sales documents cleaner and more professional.
Original PR description
Payment terms show up twice in the sales order; This way, the SO behaves like the invoice. 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
This fixes an error that could occur when a cashier selected the invoice download option while validating a point of sale payment. The change helps ensure customers can receive their invoices without disrupting the checkout process.
Original PR description
- In pos payment page when we select invoice download option and validate payment that moment
traceback occurred.
- because in _match_payment_to_invoice method when we find account_precision do not find pricelist
record.
issue : https://www.odoo.com/web?#id=1827750&view_type=form&model=project.task&action=333&active_id=1278&menu_id=4720
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-prThis fix prevents purchase order lines from trying to update product records when a product is selected. Standard purchase users can now save purchase orders and proceed to approval without needing manager-level permissions.
Original PR description
…should be readonly. Issue: currently, since "product_type" is not set readonly, it is triggering write() of product.product model when saving a PO having PO line with product_id. And it is failing…
…should be readonly. Issue: currently, since "product_type" is not set readonly, it is triggering write() of product.product model when saving a PO having PO line with product_id. And it is failing by throwing access error for users belonging to purchase "User" group users due to the fact that write() is permissible to purchase "Manager" group users only. solution: made the "product_type" related field readonly since it is used in purchase order views domain with lone purpose to set "received_qty" field non-editable when order line product is of type stockable/consumable. Task : https://www.odoo.com/web?debug#id=1818787&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.d3b2047e143dc4a698ac859eaf8fb203 Description of the issue/feature this PR addresses: Steps to reproduce : Login as admin to set "Two Steps approval" (5000 min) Login as demo Create a PO gives access error like this.. Sorry, you are not allowed to modify this document. Only users with the following access level are currently allowed to do that: Accounting & Finance/Billing Manager Inventory/Manager Purchases/Manager (Document model: product.product) Current behavior before PR: Doesn't let me save the order line having product_id Desired behavior after PR is merged: Should let me save the order (and move to the approve step) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
FedEx shipping quotes now work correctly for deliveries sent within India. The update includes the customs clearance details FedEx requires, helping businesses see accurate delivery costs before shipping.
Original PR description
… delivery from India to India so pass required value of customclearancedetails while getting rates from Fedex Description of the issue/feature this PR : task : https://www.odoo.com/web#id=58746&view_type=form&model=project.task&menu_id= pad : https://pad.odoo.com/p/r.a5f9856990585b4d5e6b990761da7fa9
Features or functions removed from Odoo
An old web report entry point that was no longer used and could fail with an error has been removed. This reduces confusion and avoids exposing a non-working path, with little expected impact because current reporting flows use other supported mechanisms.
Original PR description
it raises error because dispatch_rpc method doesn't handle case when
service_name is equal to 'report'
```
Traceback (most recent call last):
File "/mnt/odoo-source/addons/web/controllers/main.py", line 74, in wrap
return f(*args, **kwargs)
File "/mnt/odoo-source/addons/web/controllers/main.py", line 1511, in index
action["report_name"], report_ids, report_data, context])
File "/mnt/odoo-source/odoo/http.py", line 115, in dispatch_rpc
result = dispatch(method, params)
UnboundLocalError: local variable 'dispatch' referenced before assignment
```
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCode cleanup and technical improvements
This update reorganizes the Product Extended module files and refreshes some internal naming and metadata. It should make the module easier to maintain without changing day-to-day product management behavior.
Original PR description
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