- Nov 27, 2020
-
-
Martin Trigaux authored
Courtesy of Transifex's translators for reporting bad/unclear sentences. closes odoo/odoo#62539 Related: odoo/enterprise#15032 Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Nicolas Lempereur authored
related to opw-2339906 closes #62527 closes odoo/odoo#62546 X-original-commit: 62e9e72f Signed-off-by:
Nicolas Lempereur (nle) <nle@odoo.com> Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
- Nov 26, 2020
-
-
Benjamin Frantzen (bfr) authored
Task ID : 2390526 closes odoo/odoo#62450 X-original-commit: 6918d922 Signed-off-by:
Josse Colpaert <jco@openerp.com> Signed-off-by:
bfr-o <bfr-o@users.noreply.github.com>
-
- Nov 27, 2020
-
-
Achraf (abz) authored
What are the steps to reproduce your issue ? 1. Install "website_sale_comparison" 2. Create a product with only one variant with one attribut 3. Click on "Go to website" smart button 4. Enable "Customize/List View Variant" 5. Click on "Compare" button What is currently happening ? Nothing What are you expecting to happen ? Add product to the comparison list Why is this happening ? Because the product has just one variant and attribut so odoo don't display it on the product page. The system cannot find the ids as they are not on the page How to fix the bug ? Specify the product id in this case opw-2377711 https://www.odoo.com/web#id=2377711&action=4043&model=project.task&view_type=form&cids=1&menu_id=4720 closes odoo/odoo#62419 X-original-commit: dd37cd06 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com> Signed-off-by:
Achraf <abz-odoo@users.noreply.github.com>
-
Nicolas Martinelli authored
- Create Product A with UOM of type Unit - Create Product B with UOM of type Unit - Create BOM of type Kit on Product A with Product B as a component with UOM of type Unit - After saving BOM, change the UOM of Product B with UOM from another categories (e.g. kg) and save the product - Try to access product list A warning appears and prevent showing the products in any way. It is caused by the call to `_compute_quantities`. In this case, it is ok to skip the error. Indeed, it will raise later on when trying to use the kit. But at least, it gives the possibility to the user to access the product list. opw-2393711 closes odoo/odoo#62531 X-original-commit: 6de2537a Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
- Nov 26, 2020
-
-
wan authored
Reproduce: * On a fresh db, create a payment * Change the date to another month * Validate Issue: * The name is computed before creation because it is the first of journal/period. * It is not visible * It is given to the create vals of the move_id, so it is not correctly recomputed * The sequence/name are not in sync. opw-2390747 closes odoo/odoo#62297 Signed-off-by:
Laurent Smet <smetl@users.noreply.github.com>
-
- Nov 25, 2020
-
-
Nicolas (vin) authored
This PR makes three of the invoicing tour steps optional so that avoiding one doesn't break the flow of the tour anymore. It also entirely removes the step for changing the sequence of invoice as it's an advanced feature task id #2368759 closes odoo/odoo#61219 Signed-off-by:
Quentin De Paoli (qdp) <qdp@openerp.com>
-
- Nov 27, 2020
-
-
nie authored
This reverts commit 80902bee as the backport to 12.0 did not apply. closes odoo/odoo#62520 Related: https://github.com/odoo/odoo/pull/62418 X-original-commit: d6b50b76 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com> Signed-off-by:
backspac <backspac@users.noreply.github.com>
-
- Nov 26, 2020
-
-
Adrien Widart authored
When generating an efaktur, an error is raised To reproduce the error: (Use empty DB) 1. Set the company's country to Indonesia 2. Install Accounting (account_accountant) 3. Accounting > Customers > e-Faktur 4. Create & Save 5. Accounting > Customers > Customers 6. Create a customer - Set country to Indonesia - Add a TVA number 7. Accounting > Customers > Invoices 8. Create one for this customer - Add a product 9. Save & Confirm 10. In Action, "Download e-faktur" => An error is raised. OPW-2387843 closes odoo/odoo#62435 Signed-off-by:
adwid <adwid@users.noreply.github.com>
-
- Nov 27, 2020
-
-
Achraf (abz) authored
This PR decreases the opacity of dark squares and remove the white background of the logo in the certification templates to make it look better opw-2387563 https://www.odoo.com/web#id=2387563&action=4043&model=project.task&view_type=form&cids=1&menu_id=4720 closes odoo/odoo#62507 Signed-off-by:
Achraf <abz-odoo@users.noreply.github.com>
-
- Nov 26, 2020
-
-
Andrea Grazioso (agr-odoo) authored
Steps to reproduce: Create a new local Odoo DB Create another company on the DB install the CRM module Create an opportunity on the CRM app for each company. Execute This server action (CHANGE THE res_id TO THE IDs OF THE OPPORTUNITY CREATED): ``` for _ in range(0, 300): for _ in range (0, 75): env['ir.attachment'].sudo().create({'name': 'test','res_model': 'crm.lead', 'res_id': 31, 'type': 'binary'}) for _ in range (0, 75): env['ir.attachment'].sudo().create({'name': 'test','res_model': 'crm.lead', 'res_id': 45, 'type': 'binary'}) ``` go to the Settings / Technical / Database Structure / Attachments. Server will look in endless call because the search try to retrieve `limit` records, but after applying company record rule we have `limit - e`, so it begin a second search for e records. Even the second search will look for limit and possibly will find less, starting a third... If the sub call is aware of how much records we actually need after checking permission, we can return the recordset if we have collected enough opw-2369722 closes odoo/odoo#62448 X-original-commit: 6a8f28c4 Signed-off-by:
agr-odoo <agr-odoo@users.noreply.github.com>
-
- Nov 23, 2020
-
-
Andrea Grazioso (agr-odoo) authored
Create a sale order for a stored product, save and confirm. Validate delivery Return and validate. Return (the return, so delivery again) and validate. Try return again. The quantity to return in the widget will be 0. Attempting to fix manually will worsen the situation creating negative quantities on further action. This occur because when creating the return the system tries to identity other sibling return moves to set the correct quantity This commit fine tunes 73de0645b730e1f1183b7c770e878b4c4ff1e0f1 aiming to collect quantities only on actual sibling returns (moves sharing the same parent) opw-2379663 closes odoo/odoo#62165 X-original-commit: fe8c6db1 Signed-off-by:
William Henrotin <Whenrow@users.noreply.github.com> Signed-off-by:
agr-odoo <agr-odoo@users.noreply.github.com>
-
- Nov 27, 2020
-
-
Denis Roussel authored
closes odoo/odoo#62496 X-original-commit: 0ddad8128d3ea4ab75b98bea8da3c1de676c1b5d Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
Williams Estrada authored
closes odoo/odoo#62492 X-original-commit: 4fe35257 Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Romain Derie authored
Without this commit, when the compare/reset view feature was reading the arch, it would translate it. 3 issues : - When reading from file (hard reset), it would translate the file version - When reading current arch, it would translate it - When reading compare view arch, it would translate it closes odoo/odoo#62433 X-original-commit: c33c6316 Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com> Signed-off-by:
Romain Derie <rdeodoo@users.noreply.github.com>
-
- Nov 26, 2020
-
-
Nicolas Galler authored
Behavior prior to this commit: - when the warehouse uses a 3-step manufacturing process, if I create a Sales Order, the MO generated does not show the SO# as "Source", instead it shows the MO# Behavior after this commit: - the MO source shows the SO# (similar to how it works when using the 2-step or the 1-step manufacturing process) - the origins are assigned thus: - Delivery Picking = SO name - Post-prod Picking = SO name - MO = SO name - Pre-prod Picking = MO name Note: - there is no implementation change in this commit - we just ported the test from the original commit in 13.0 (the behavior in 14.0 was already OK) opw-2380717 closes odoo/odoo#62432 X-original-commit: 0bc86a8d Signed-off-by:
Nicolas Galler <ngaller@users.noreply.github.com>
-
- Nov 27, 2020
-
-
Aaron Bohy authored
Consider the following situation: - have a form view with an x2many field displayed as a list - the x2many field has a form view that contains an x2many field, which isn't in the list - for that x2many field, we can also open a form view to see/edit the related records. As the x2many field isn't in the list, when we open a subrecord, we modify the fieldsInfo to add the information about the x2many field we didn't know before. Doing so automatically applies raw changes that we might have stored earlier (from onchanges) for that field, because we couldn't apply them before knowing the type of that field. Before this commit, the function that applies the raw changes was called recursively on the dataPoint and all its children (thus on the x2many list datapoint), which produced a crash as this function is designed to work on dataPoints of type record. Actually, calling it on sub datapoints is useless, as it properly works recursively, and applies raw changes on x2many fields itself when necessary. This commit ensures that we don't call this function on list datapoints anymore. Closes #62334 OPW 2389991 closes odoo/odoo#62399 Signed-off-by:
Géry Debongnie (ged) <ged@openerp.com>
-
Xavier Morel authored
Only updates outdated requirements which actively cause issues: * freezegun broken in 3.8 (removal of time.clock) * xlrd broken in 3.8 (removal of time.clock) * also monkeypatches xlrd.xlsx for 3.9 (removal of Element.getiterator, breaks because of defusedxml) * jinja triggers DeprecationWarning in 3.8 * pillow triggers warning in 3.9 * lxml, greenlet don't compile in 3.9 * reportlab doesn't work in 3.9 New versions try to match those of Debian Bullseye. Also adds a script to more easily compare dependency versions between the requirements files and what's in various distributions (currently supports checking against debian and ubuntu). Furthermore updates warnings filtering: * removes xlrd (mischeck was monkeypatched as noted above) * removes setuptools (was for older versions, one would hope this isn't an issue anymore) * adds babel: python-babel/babel#684 fixes the deprecation warning but is not part of any release yet * ignores error related to `random.sample` on a set, this is a diagnostics bug because recordsets implement both Sequence and Set, and the stdlib checks for Set first (bpo-42470) See #59980 Closes #61103 closes odoo/odoo#62380 Signed-off-by:
Xavier Morel (xmo) <xmo@odoo.com>
-
Anh Thao Pham (pta) authored
- Install website_slides - Connect with an user (i.e. Mitchell Admin) - Go to Website and open a Course quiz for the first time (i.e. "Test Yourself" from "Basics of Furniture Creation" Course) - Answer correctly The number of won karma is the one from the last attempt reward and is not saved in user's total xp. When submitting the quiz, quiz_attempts_count is incremented via a SQL query, but its value is not updated in cache directly. When the karma gain is computed from the attempts count, the value used is the old one in cache. opw-2389969 closes odoo/odoo#62421 Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
Leo Tran authored
Done at #62137 closes odoo/odoo#62478 X-original-commit: 60d723cb Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Christophe Monniez authored
Fixes #62214 closes odoo/odoo#62475 X-original-commit: 45afa3a2 Signed-off-by:
Christophe Monniez (moc) <moc@odoo.com>
-
- Nov 26, 2020
-
-
Joseph Caburnay authored
There is a situation in pos_restaurant such that when an order is deleted from the ticket screen, it persists to show when the table is opened. To reproduce: 1. Create an order in T1 then add items to it. 2. Get out of the table (back to floor). 3. Open ticket screen. 4. Delete the order in T1. 5. Close the ticket screen. 6. Open T1, the order is still there (bug). This commit fixes this behavior such that in step 6, new order should show and not the deleted order. Note that we also made a change in the template in order to allow checking the number of synced orders during testing. We want to make sure that the table is clicked when the sync finishes to prevent concurrency issue during testing. closes odoo/odoo#62403 Signed-off-by:
pimodoo <pimodoo@users.noreply.github.com>
-
- Nov 27, 2020
-
-
Nicolas (vin) authored
In the hr localization, some of the tax report lines have a line code without tag name, and are then used in some formulas. This is incorrect since the tag name is needed to get a balance. This PR will fix this by removing the codes and their appearance in the formulas, since these lines have no incidence in the result. Task id #2376724 closes odoo/odoo#61413 Signed-off-by:
Quentin De Paoli (qdp) <qdp@openerp.com>
-
- Nov 26, 2020
-
-
nie authored
Steps: - Install Contacts - Have Multi-Companies enabled - Go to a Contact of type "Company" - Click "Sales & Purchases" - Assign it the company you're on - Save and Edit again - Remove the assigned company - Go to a contact of type "Individual" linked to this company - Click "Sales & Purchases" Bug: The company has not been deleted on the linked Individual Explanation: When we delete the company of a contact, the value of `vals.get('company_id')` is `False`. This is why it didn't enter the propagation process. opw:2391464 closes odoo/odoo#62461 X-original-commit: 80902bee Signed-off-by:
backspac <backspac@users.noreply.github.com>
-
Sébastien Theys authored
task-2292595 closes odoo/odoo#62454 Signed-off-by:
Christophe Monniez (moc) <moc@odoo.com>
-
- Nov 19, 2020
-
-
Didier (did) authored
closes odoo/odoo#61987 Signed-off-by:
Yannick Tivisse (yti) <yti@odoo.com>
-
- Nov 26, 2020
-
-
Stephane Mangin authored
closes odoo/odoo#62434 X-original-commit: 52cd0a74 Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Benoit Socias authored
Before this commit if a product template has no image, no image was displayed in the website shop for the product After this commit if a product template has no image, the image of the first variant is displayed in the website shop https://github.com/odoo/odoo/issues/52463 closes odoo/odoo#62431 X-original-commit: 643c8a9d Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
Goffin Simon authored
Steps to reproduce the bug: - Create a BOM kit K with two components C1 and C2 Bug: It was possible to set an operation on K PS: Operation is not supported on BOM kit opw:2393302 closes odoo/odoo#62427 Signed-off-by:
Simon Goffin (sig) <sig@openerp.com>
-
Jairo Llopis authored
This makes the act of replacing the dummy text easier. @Tecnativa closes odoo/odoo#62413 X-original-commit: 115d9a58 Signed-off-by:
Jérémy Kersten (jke) <jke@openerp.com>
-
Ivan Yelizariev authored
STEPS: * Create a BoM with two components purchased the same vendor, but with different "Delivery Lead Time". First component must have lower value * Create Manufactoring order, Mark as ToDo * Open created purchase order BEFORE: Order Date is equal "MO planned day MINUS delivery lead time for the first component" AFTER: Order Date is equal "MO planned day MINUS maximum amout delivery lead time for the components" --- opw-2388031 closes odoo/odoo#62404 X-original-commit: 8f0cc360 Signed-off-by:
Ivan Yelizariev // IEL <yelizariev@users.noreply.github.com>
-
Vishnu Vanneri authored
Fiscal positions shouldn't be deleted if used by existing account moves closes odoo/odoo#62398 X-original-commit: 6f5801a7 Signed-off-by:
Victor Feyens (vfe) <vfe@odoo.com>
-
- Nov 25, 2020
-
-
Lucas Lefèvre authored
The mock implementation of `name_get` does not fully reflect the real server implementation. The real implementation is described in tests added in this commit. Note: in my wildest dreams, the mock server tests would be run against the real *and* the mock implementation to ensure they do not diverge. closes odoo/odoo#62347 Related: odoo/enterprise#14990 Signed-off-by:
Aaron Bohy (aab) <aab@odoo.com>
-
- Nov 23, 2020
-
-
Didier (did) authored
task-2387820 closes odoo/odoo#62166 Signed-off-by:
Alexandre Kühn (aku) <aku@odoo.com>
-
- Nov 26, 2020
-
-
Achraf (abz) authored
What are the steps to reproduce your issue ? 1. Install "google_calendar" 2. Log in with "admin" 3. Create an eventX with "admin" and "demo" has attendees 4. Run "Google Calendar Synchronization" from "Scheduled Actions" What is currently happening ? eventX is successfully added to Google but without admin if you sync Odoo to Google one more time, Google will overwrite eventX and it will remove admin from attendees What are you expecting to happen ? Sync Odoo to Google and Google to Odoo without lost attendees Why is this happening ? Because there is a filter that prevent addition of current user to the attendees How to fix the bug ? Remove the filter This reverts commit 287ee0f8. opw-2382443 closes odoo/odoo#62406 Signed-off-by:
Nicolas Martinelli (nim) <nim@odoo.com>
-
Nicolas Galler authored
Leftover from commit b5e39fc closes odoo/odoo#62379 Signed-off-by:
Nicolas Galler <ngaller@users.noreply.github.com>
-
- Nov 25, 2020
-
-
Swapnesh Shah authored
Followup on 911ada2d When modifying the company_id of a pricelist, the check to ensure a website has a pricelist available wasn't triggered. This commits ensures the Each website has Valid Pricelist with Correct or Empty company. Fixes #50707 closes odoo/odoo#62358 X-original-commit: f196430b Signed-off-by:
Romain Derie <rdeodoo@users.noreply.github.com>
-
- Nov 26, 2020
-
-
Bruno Zanotti (ADHOC) authored
closes odoo/odoo#62395 X-original-commit: 8fdf193c Signed-off-by:
Josse Colpaert <jco@openerp.com>
-
Stefano Consolaro authored
closes odoo/odoo#62377 X-original-commit: 73293a2b Signed-off-by:
Martin Trigaux (mat) <mat@odoo.com>
-
Nicolás Mac Rouillon authored
For this case, if the invoice currency is different from the invoice company currency, the tax calculation is considered the value in a different currency, and the subtotal is the sum of the amount untaxed + the taxes (wrongly in company currency) result in an incorrect value. This is verified when printing the invoice report closes odoo/odoo#62386 X-original-commit: 91f152f4 Signed-off-by:
Josse Colpaert <jco@openerp.com>
-