Wednesday, May 22, 2019
9 changes · master
Enhancements to existing features
Odoo now stores rarely changing startup data, such as menus, translations, and page templates, in the browser cache for much longer. This reduces repeated loading work and helps users reach the web client faster, especially after the first visit.
Original PR description
Today, some resources that varies very infrequentely are requested on every page load: the menus, the translations and the qweb templates After this commit, there will be 2 improvements that will…
Today, some resources that varies very infrequentely are requested on every page load: the menus, the translations and the qweb templates After this commit, there will be 2 improvements that will make the loading of the webclient faster: 1. cache almost static resources forever when loading the /web/ page, the user session will contain the cache key to be used to fetch these resources. As the content of the resource itself it used to compute the hash, the request can be put in cache by the browser forever (for a year). The up side is that in general less requests are needed to load the web client The down side is that the load time and number of queries of /web page has increased to include what is needed to compute the hash of translations, menus and qweb templates 2. trigger the loading of the menus before the download (and startup) of the JS and CSS assets: The menus contains the definition of the action, wich is the first thing needed to load a page in odoo. Starting the loading of the menu much earlier means that when they are not yet in the browser cache (see point 1), the browser does not need to wait for the entire assets to be downloaded and parsed before starting the 'load_menu' request, but instead start it immediately and hold onto a promise to be used instead of the rpc 'load_menu'. Because the request is done before anything else is loaded, including JQuery, it is made in vanilla JS. task-id: 1943338 Co-authored-by: Julien Mougenot <jum@odoo.com> -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Reverse transfers in inventory now have the refund option selected by default. This reduces manual steps and helps ensure returned stock is handled correctly for the most common refund workflow.
Original PR description
**Description of the issue/feature this PR addresses**: - Task: https://www.odoo.com/web#id=1962183&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad: https://pad.odoo.com/p/r.61bcd8c2452ff710300a6e82db02e59e **Current behavior before PR:** - The checkbox of to_refund isn't ticked by default. **Desired behavior after PR is merged:** - The checkbox of to_refund will be ticked by default. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves how Point of Sale orders work in environments with multiple companies. It helps businesses operating several legal entities keep POS activity aligned with the correct company, reducing confusion and improving operational reliability.
Original PR description
Task ID : 1966418 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change updates how grouped data is read and prepared for reports and chart views. It should make reporting behavior more consistent across core data models, pivot views, web views, and website link charts while keeping the change mostly behind the scenes.
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
The web client now loads key menu data earlier and keeps static resources cached longer, helping users reach the app faster. Related Enterprise and Studio startup flows were adjusted so the faster loading sequence remains reliable.
Original PR description
Description of the issue/feature this PR addresses: decrease the startup time by managing the http requests made by the browser a bit better Co-authored-by: Julien Mougenot <jum@odoo.com>
This update aligns supporting code for grouped data reporting used by cohort and grid views. It helps keep business analytics views reliable as the underlying reporting method is modernized, with no expected change to everyday workflows.
Resolved issues and error corrections
The stock return process now requires users to choose a return location before completing the return. This prevents avoidable errors caused by missing location information and makes the return workflow clearer.
Original PR description
Task: https://www.odoo.com/web?#id=1986294&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a103bfb587565b245037c5bec43bf5c9 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
Miscellaneous changes
This pull request discusses making static file delivery more efficient while keeping access limited to the modules available for each user. The provided information reads more like a proposal or question than a confirmed code change, so the business impact is likely limited until implementation details are available.
Original PR description
Current behavior before PR: "security": static asset are not "public", only configured modules (for a user) should be served performance: serving static assets can be slow on odoo.sh due to Werkzeug serving them unless I' did not read correctly the code. Desired behavior after PR is merged: @KangOl Will the load_addons method be moved from http to ir.http one day ? Are the static asset server using nginx on odoo.sh ? or is it still using Werkzeug ? -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The test framework now uses the real record when checking automatic form updates, making test results more accurate. This reduces the chance of missed issues or misleading failures during development, with no direct impact on everyday users.