- Jul 22, 2020
-
-
Jeremy Kersten authored
Before this commit each url was processed each time, now with have a cache with the path (withtout query string) as key on each worker. It reduces drastically the time of the rewrite check on hot. (~10x) closes odoo/odoo#54690 Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
Jeremy Kersten authored
Retro-compatibility routes
-
Jeremy Kersten authored
Url for a product become: /shop/productname-id instead of /shop/product/productname-id Url for a blog post become: /blog/blogname-1/blogpost-1 instead of /blog/blogname-1/post/blogpost-1 Url for a question on forum become: /forum/forumname-1/title-1 instead of /forum/forumname-1/question/title-1 task-2295016
-
- Jul 17, 2020
-
-
Samuel Degueldre authored
In #45174, the original_id field was added on ir.attachment, so that derived images in the web-editor (cropped, resized, optimized, ...) could keep a trace of the original, such that if the user wanted to revert it or change the crop/size/optimization parameter, we could do it from the original again so that for example the quality can be increased or the crop region made bigger. The addition of this self-referencing many2one from ir.attachment to itself however will cause DELETE queries on ir.attachment to do a sequential scan on the table to update potential records referencing the deleted record in their original_id field. As the ir.attachment table tends to be one of the biggest tables in production databases (millions of records), this scan can take multiple seconds per DELETE operation, and since attachments are used everywhere in odoo to represent files, DELETE operations on them are frequent. Adding an index on the original_id field should make these DELETE operations substantially faster (scaling with the log of the number of filled original_id fields, which will be very small, instead of scaling linearly with number of records) closes odoo/odoo#54676 X-original-commit: 2b5064a00b7a5c8dc66429869287386f244b1257 Signed-off-by:
Olivier Dony (odo) <odo@openerp.com> Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
- Jul 16, 2020
-
-
Toufik Ben Jaa authored
- Since the wizards now requires ACLs, the access rights set on the lead forward partner and the lead assignation are incorrect. Only the Sales/Administrator are able to use them. With this commit we introduce the intended behavior where the sales are able to perform those tasks. closes odoo/odoo#54568 X-original-commit: 3081ca828e4a7de3861ee5b1fb9600b248c3ea07 Signed-off-by:
Toufik Benjaa (tbe) <tbe@odoo.com>
-
- Jul 15, 2020
-
-
Christophe Simonis authored
The tax mapping is only readable by internal users. As the calling method can be used by portal routes, we should browse the fiscal position in sudo mode. closes odoo/odoo#54524 X-original-commit: 46e9a9683967600c55bf43895740fff1d61eb49b Signed-off-by:
Christophe Simonis <chs@odoo.com> Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
Nicolas Martinelli authored
- Create a product with routes MTO + Buy. - Create a vendor pricelist with a minimum quantity: Min. Qty 1000 for 10 USD - Create a SO, sell 1000 quantity => A PO is created automatically in draft. - Go back to SO and update quantity to 1200. The following message pops up: "There is no matching vendor price to generate the purchase order for product..." We select the supplier based on the procurement quantity, which is lower than the minimum quantity of the supplier. To avoid this situation, we fall back on any supplier like it was the case in v12. opw-2297001 closes odoo/odoo#54526 X-original-commit: 4d4913fc Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
- Jul 17, 2020
-
-
oco-odoo authored
[FIX] account: make assignation of tax repartition and tags work in bank reconciliation widget and on misc operations Bank reconciliation widget allows creating a writeoff with tax lines, in order to simulate both the invoice and the payment into a single entry, from one statement line. Before this fix, the tax repartition used by this feature was always the one defined for invoices. Also, in some cases, the amounts reported in the tax report had the wrong sign, because of the way the tax report applies the sign multiplicator on lines' balances. This multiplicator cannot be computed properly from a payment or miscellaneous operation, so we need to rather impact the sign of the tags directly. With this fix, we guess whether or not we are refunding something from the data entered by the user, and modify the signs of the tags accordingly so that the tax has the same impact on the report as it would have had with an invoice doing the same operation. closes odoo/odoo#54691 X-original-commit: ac2662b67c878eb2ef6e9462a0e6c9f1fbdb6adb Related: odoo/enterprise#11948 Signed-off-by:
Laurent Smet <smetl@users.noreply.github.com>
-
- Jul 16, 2020
-
-
yhu-odoo authored
This commit add text "minutes" after Expected Duration on the form view of mrp.workorder. closes odoo/odoo#54592 X-original-commit: 2ec72fec26a66bd5dc49aa56c4ca44dc3f31ad06 Related: odoo/enterprise#11900 Signed-off-by:
Arnold Moyaux <amoyaux@users.noreply.github.com>
-
yhu-odoo authored
When launch a consumption warning wizard by clicking the "Mark as done and close mo" button, always close the MO. And return to tree view if we open the tablet view from a 'start' button, return to workorder kanban if we open tablet from that. Task 2278147 X-original-commit: 4d03cf5e8d29933d5f96099f8f662c9084b20197
-
- Jul 20, 2020
-
-
Pafnow authored
The record is invisible when active=False, not the field Correct rst arrow syntax Sign CLA closes odoo/odoo#54714 X-original-commit: 055cb50b Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Raphael Collet authored
When setting the inverse many2one field on a record, the record is not removed from its inverse relation if the field's current value is not in cache. Fix this by setting the field's value in cache before updating. closes odoo/odoo#54711 X-original-commit: df12c858 Signed-off-by:
Xavier Morel (xmo) <xmo@odoo.com>
-
Xavier Morel authored
Issue is specifically in the case of an onchange removing a record in an o2m in an o2m (so a sub-o2m) if loading an *existing* record in the SSF: since the server pretty much only returns a REMOVE_ALL followed by the records to keep or create, conserving the removal information requires diffing the value currently stored in the form and the result fo the onchange. Diff which was properly done for top-level o2ms, but not for the ones below that (apparently forgot this bit when improving support for nested o2ms earlier this year). X-original-commit: 177d0095
-
Xavier Morel authored
Otherwise the reStructuredText parser thinks the first definition title is part of the preceding paragraph, and the definition item is interpreted as a quote due to the indentation. closes odoo/odoo#54709 Signed-off-by:
Xavier Morel (xmo) <xmo@odoo.com>
-
- Jul 17, 2020
-
-
Andrea Grazioso (agr-odoo) authored
When the server execute the job 'Mail: Fetchmail Service' if it's processed an attachment having a Notes field with None values the following traceback will occur AttributeError: 'NoneType' object has no attribute 'split' //IdentificativoSdI','//DataOraRicezione','//Descrizione','//MessageId','//Note'. seems to be not mandatory opw-2277722 closes odoo/odoo#54636 X-original-commit: f96be5eb Signed-off-by:
Nicolas Lempereur (nle) <nle@odoo.com> Signed-off-by:
agr-odoo <agr-odoo@users.noreply.github.com>
-
- Jul 13, 2020
-
-
Martin Trigaux authored
There is no field 'ids' on a gamification.goal, but one called 'id' Without this commit, calling _get_serialized_challenge_lines (or indirectly, calling report_progress) with a non-empty subset_goals was failing due to an invalid domain. This is not supposed to happen on standard flow but can be triggered with manual modification of date fields and refreshing a challenge. Fixes odoo/odoo#25913 closes odoo/odoo#54387 X-original-commit: 1e3483d2 Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
- Jul 17, 2020
-
-
Xavier Dubuc authored
Clicking on mark as read on a given message would move all messages in inbox to history instead of only selected message(s). This commit fix that behaviour so that only the selected message(s) move(s) to history. task-2284543 closes odoo/odoo#54688 X-original-commit: 3304b89fc799b979b028aa4c7efe902b2f5276c1 Signed-off-by:
Alexandre Kühn (aku) <aku@odoo.com>
-
Olivier Dony authored
Follow-up of odoo/enterprise#11881, in order to eliminate all similar typos. The CSS pseudo-class selectors are spelled `:first-child` and `:last-child`, and never take any argument, as opposed to `:nth-child(<nth>)` for example. Ref: https://developer.mozilla.org/docs/Web/CSS/Pseudo-classes jQuery doesn't care and matches with or without the `()`, but CSS engines don't, and now libsass SCSS compilation crashes due to the empty argument list (cfr. opw-2299465) Better avoid confusion and fix the typo everywhere. closes odoo/odoo#54685 X-original-commit: 82244e17339615615535073e6f9e1ddbcf0b57d9 Signed-off-by:
Richard Mathot (rim) <rim@openerp.com> Signed-off-by:
Olivier Dony (odo) <odo@openerp.com>
-
Jeremy Kersten authored
Before this commit, in case you were in --dev-mode, if a json request crash, it was wrongly intercepted and return a Internal Server Error with status 500 and without the JSON Response For the change of http code, since it is only in dev mode, it could not impact a production server (in theory) with custom code based on it. After this commit, if your rpc fails, you will not have anymore a breakpoint in the code to help the developer to debug. But you will have a status 200 on the rpc request. closes odoo/odoo#54668 X-original-commit: 534cca31 Signed-off-by:
Olivier Dony (odo) <odo@openerp.com> Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
Aaron Bohy authored
Before this commit, it might happen that text field columns in list views were completely crushed, to let space to the other columns. This commit fixes the issue by preventing text fields from being wrapped during the ideal column widths computation. Doing so, text fields will take space they deserve according to their content. They will then be wrapped if necessary, so that they aren't trimmed, unlike e.g. char fields. Task 2275747 closes odoo/odoo#54664 X-original-commit: 5c54111127bd99eedb4e0331aba5a0200feb461c Signed-off-by:
Lucas Perais (lpe) <lpe@odoo.com> Signed-off-by:
Aaron Bohy (aab) <aab@odoo.com>
-
Joseph Caburnay authored
We now allow invoicing of finalized orders in an open session in this first iteration of order management in the pos frontend. Additionally, receipt reprinting is also introduced. With this feature, we can now reprint the receipt of old orders. closes odoo/odoo#51141 Task-id: 1981354 Related: odoo/enterprise#11690 Related: odoo/upgrade#1472 Signed-off-by:
pimodoo <pimodoo@users.noreply.github.com>
-
Joseph Caburnay authored
TASK-ID: 1981354
-
Martin Trigaux authored
A term was present twice in Italian, making the installation of Italian crash for the Swich CoA Introduced at a3029a8c Remove some reference to company accounts (it is handled by l10n_multilang, should not be set manually as working only for company wiht id 1) closes odoo/odoo#54658 X-original-commit: fb10cc6d Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
jvm-odoo authored
This commits fixes the case where you click on edit address in eCommerce payment flow and you type a wrong coupon code. Without this commit, you are redirected at /shop/payment instead of /shop/checkout OPW-2290188 closes odoo/odoo#54646 X-original-commit: 0d658349 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com> Signed-off-by:
Nicolas Lempereur (nle) <nle@odoo.com> Signed-off-by:
Jason Van Malder (jvm) <jvm@odoo.com>
-
Mohammed Shekha authored
Improve tooltip style/design to get rid of black background and purple title, instead design tooltip like popover design, to have tooltip with white background and light grey title task-2266829 closes odoo/odoo#53723 Signed-off-by:
Aaron Bohy (aab) <aab@odoo.com> Co-authored-by:
Ipsita Borisagar <ibo@odoo.com>
-
qsm-odoo authored
Use small buttons and icons. Part of https://github.com/odoo/odoo/pull/45096 task-2162952 closes odoo/odoo#45096 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
Benjamin Vray authored
Keep the selected image after moving it in the gallery. So that the options for moving the current image are always displayed. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Benjamin Vray authored
Add the width option for each slides in the carousel snippet. Remove share links from the third slide of the carousel. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Benjamin Vray authored
Add dots indicators in gallery snippet options. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Benjamin Vray authored
Snippet image gallery retains only the slideshow mode and a new snippet called 'image wall' takes the 3 other modes. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Benjamin Vray authored
Review the gallery snippet. It has been improved in multiple ways. Added new options, etc. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Benjamin Vray authored
In gallery snippet with slideshow mode, the right/left indicators have now the same behavior in editor and outside. Before this commit, these indicators were always visible in editable mode. Part of https://github.com/odoo/odoo/pull/45096 task-2162952
-
Paul Morelle authored
The permission check in BaseModel:export_data was checking if the current user was the administrator user, instead of checking if the environment was administrator (i.e. it should also check if the sudo bit is set on the environment). This commit fixes this and allows to export_data with a simple `sudo()` instead of needing a `with_user(SUPERUSER_ID)`. closes odoo/odoo#54647 X-original-commit: f69f47b6ba5c6c462bf617f4876a39233f60034f Signed-off-by:
Olivier Dony (odo) <odo@openerp.com> Signed-off-by:
Paul Morelle <madprog@users.noreply.github.com>
-
qsm-odoo authored
In some complex cases, some snippet editors were destroyed but were still referenced in memory. E.g. 1) Reorder a snippet gallery image 2) The code is implemented in such a way that reordering create a new wrapping column for each image and moves the images in them. 3) This result in having the snippet editor linked to the old columns to be explicitely destroyed and removed from memory, but not the ones linked to the images as they are still in the DOM (just moved). 4) ... but the snippet editors linked to the images are children of the snippet editors linked to the columns. They are thus implicitely destroyed... but not removed from memory. closes odoo/odoo#54643 X-original-commit: e4bf37c7fc892cdba57f0acac8e10f5698184e67 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
qsm-odoo authored
The bug was already solved with [1] but was reintroduced later for another reason. [1] solved the problem by checking that the current option is not destroyed before asking for an UI update thanks to a trigger_up (the option was destroyed because of image reordering). The bug is now reintroduced for the same basic reason: a new trigger_up was added between the potential option destroy and the destroy check, so if the option is destroyed, that trigger_up fails to be triggered and the editor is locked. This commit solves the problem once and for all, hopefully, with a more robust solution: only destroy options when none is being processed. That way we ensure that all trigger_up occuring during an option activation / update can be properly done. [1]: https://github.com/odoo/odoo/commit/9eeea4c4107dc15984c475582d5ee58a17cd2568 X-original-commit: 7770430f78ee9e122a732fa042226d362467158e
-
qsm-odoo authored
Commit [1] broke the background videos feature. This is because the 'we-imagepicker' widget is now a sub-widget of a new 'we-button-group' widget, acting as a selection choice (same as we-button in a we-select). When selecting a selection choice, the appropriate option method is called, with the selection value and params... but the params were actually the ones of the 'we-button-group' element and not the ones of the chosen widget 'we-imagepicker'. This has never been important for we-select widgets but it could have been. The problem is only solved here in master, generically for all selection widgets (currently only 'we-select' and 'we-button-group'). The params received are the ones of the active sub-widget combined with the ones of the selection widget. [1]: https://github.com/odoo/odoo/commit/bb0cd4d5c82a9c2311f8c45ced0e9fdc0397d292 closes odoo/odoo#54629 Signed-off-by:
Quentin Smetz (qsm) <qsm@odoo.com>
-
- Jul 16, 2020
-
-
fja-odoo authored
Part of: https://github.com/odoo/odoo/pull/54283 task-2278147 closes odoo/odoo#54607 X-original-commit: b13e7d7bf3565242d1f99c6d9d5dfc7a8aa2929d Related: odoo/enterprise#11906 Signed-off-by:
Arnold Moyaux <amoyaux@users.noreply.github.com>
-
- Jul 17, 2020
-
-
std-odoo authored
Bug === Register to an event with a public user. Sometimes an ACL error will be raised. Technical ========= Before flushing the environment (after the creation of the event registration in the endpoint `registration_confirm`), the ORM will recompute all needed stored fields. As we didn't write on some of them (`date_closed`, `utm_campaign_id`, `utm_source_id`, `utm_medium_id`) they are in the list `Environment::all.tocompute`. So, the ORM will recompute the fields even if the state didn't change (this behavior can be verify in `BaseModel::recompute`). This is done after the "create" call of the event registration and so without the SUDO flag. Task-2299227 closes odoo/odoo#54624 X-original-commit: 38f37cd483b7907b20171e2c44e14e69e3e00596 Signed-off-by:
Thibault Delavallee (tde) <tde@openerp.com>
-
Joseph Caburnay authored
1. Methods associated to touchmove and touchstart listeners should not call preventDefault because they are passive by default. Calling preventDefault will do nothing but in chrome browser, error message is issued. 2. We now allow resize based on touch events. closes odoo/odoo#54612 X-original-commit: c6b7133d9c9dc52a8d283124b5a4497940e54682 Signed-off-by:
pimodoo <pimodoo@users.noreply.github.com>
-
Joseph Caburnay authored
The primary goal of disableRubberbanding is to disable scrolling during touch event by default and to allow only selected descendants to have scrolling active during touchstart+touchmove event. Only elements with class="touch-scrollable" are allowed for touch scrolling. This restriction can be a good idea but it results to bug-ridden explicitness which is not necessary because scrolling should be allowed automatic by default in the first place. In this commit, we allowed scrolling by default by: 1. We remove disableRubberbanding. 2. We set the position property of .pos to fixed. This is to accomplish the original goal of disableRubberbanding (fixing the root element in its position). 3. We remove the touch-scrollable class as they are not needed anymore and no style associated to it. Removing the disableRubberbanding method also fixes the Intervention error during touch scrolling event. The reason for that error is we are calling preventDefault in the event that is passive. touchmove and touchstart events are passive by default - which means that preventDefault won't work. X-original-commit: 54f7fb49dae3aab6a005402a1ac60262bbd15edc
-