Daily updates from Odoo
Tuesday, October 22, 2019
23 changes · master
Features or functions removed from Odoo
The stock app no longer shows a limited warning wizard for overprocessed transfers because it only displayed one affected product and did not take any action. This cleanup simplifies the transfer workflow and removes a misleading screen without changing core stock processing.
Original PR description
As this wizard only shows the first product overprocessed and does nothing else, we remove it completely for cleaning purposes. task-1938108
Miscellaneous changes
followup of 8a0fc6476c70a4126043de3b3efbd1096e41f968 task-2065018 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 Forward-Port-Of: odoo/odoo#39200
Original PR description
followup of 8a0fc6476c70a4126043de3b3efbd1096e41f968 task-2065018 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 Forward-Port-Of: odoo/odoo#39200
Oversight of package.py refactor. Forward-Port-Of: odoo/odoo#39162
Original PR description
Oversight of package.py refactor. Forward-Port-Of: odoo/odoo#39162
Description of the issue/feature this PR addresses: This is a forward-port of https://github.com/odoo/enterprise/pull/6267 from 12.0 to saas-12.3 NB : It was moved from enterprise to community. 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 Forward-Port-Of: odoo/odoo#39123
Original PR description
Description of the issue/feature this PR addresses: This is a forward-port of https://github.com/odoo/enterprise/pull/6267 from 12.0 to saas-12.3 NB : It was moved from enterprise to community. 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 Forward-Port-Of: odoo/odoo#39123
Chart of Accounts (COA) Template for Lithuania's Accounting (VAS-15). Data is multi language (English and Lithuania). This module also includes: * List of available banks in Lithuania. * Tax groups (to map different tax amounts). * Most common Lithuanian Taxes. * Fiscal positions for different countries/groups. * Account Tags used for reporting purposes. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged:
Original PR description
Chart of Accounts (COA) Template for Lithuania's Accounting (VAS-15). Data is multi language (English and Lithuania). This module also includes: * List of available banks in Lithuania. * Tax groups (to map different tax amounts). * Most common Lithuanian Taxes. * Fiscal positions for different countries/groups. * Account Tags used for reporting purposes. 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 Forward-Port-Of: odoo/odoo#39027
In deliveries slips, you can directly create a new serial number. If you have multiples companies, a field "company" appears. But if you have only one company, it doesn't appears and there is no default value for it. As the field is required, it returns an error "Company field required". Before this commit: - The company_id field in stock_production_lot model does not have a default value. After this commit: - The company_id field has a default value which is the
Original PR description
In deliveries slips, you can directly create a new serial number.
If you have multiples companies, a field "company" appears.
But if you have only one company, it doesn't appears and there is
no default value for it.
As the field is required, it returns an error "Company field required".
Before this commit:
- The company_id field in stock_production_lot model does not
have a default value.
After this commit:
- The company_id field has a default value which is the user
current company id.
OPW-2083099
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
Forward-Port-Of: odoo/odoo#39125Start odoo-bin using a tier module (like `python3 -m pdb odoo-bin`), the odoo/addons __path__ contains the relative link to the modules instead of the absolute link like when directly started (`python3 odoo-bin`). This cause trouble importing modules because it reuses the relative path from within other directories. 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 r
Original PR description
Start odoo-bin using a tier module (like `python3 -m pdb odoo-bin`), the odoo/addons __path__ contains the relative link to the modules instead of the absolute link like when directly started (`python3 odoo-bin`). This cause trouble importing modules because it reuses the relative path from within other directories. 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 Forward-Port-Of: odoo/odoo#39164
Since commit https://github.com/odoo/odoo/commit/dba478332681dd21a39c4a183c002b1cf6e046d2, a survey can have questions with no section associated, which means 'page_ids' field will be empty. This prevents to display some questions of a survey, as we are still expecting a structure page/questions. To solve it, we first append questions with no sections, then all other questions. Description of the issue/feature this PR addresses: opw-2089932 Current behavior before PR: Desired beh
Original PR description
Since commit https://github.com/odoo/odoo/commit/dba478332681dd21a39c4a183c002b1cf6e046d2, a survey can have questions with no section associated, which means 'page_ids' field will be empty. This prevents to display some questions of a survey, as we are still expecting a structure page/questions. To solve it, we first append questions with no sections, then all other questions. Description of the issue/feature this PR addresses: opw-2089932 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 Forward-Port-Of: odoo/odoo#39064 Forward-Port-Of: odoo/odoo#39015
This fixes a regression introduced by 291a0e99d137142bd24addd1054c1357ddd7125a. Forward-Port-Of: odoo/odoo#39159
Original PR description
This fixes a regression introduced by 291a0e99d137142bd24addd1054c1357ddd7125a. Forward-Port-Of: odoo/odoo#39159
…le account With Anglo-Saxon accounting, invoices with stock_moves on a product having 'real_time' valuation cannot be validated: there is a user error when the interim account is not reconcilable. We modify _anglo_saxon_reconcile_valuation so that we do not try to reconcile when the account is not reconcilable. OPW-2080180 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed
Original PR description
…le account With Anglo-Saxon accounting, invoices with stock_moves on a product having 'real_time' valuation cannot be validated: there is a user error when the interim account is not reconcilable. We modify _anglo_saxon_reconcile_valuation so that we do not try to reconcile when the account is not reconcilable. OPW-2080180 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 Forward-Port-Of: odoo/odoo#38974 Forward-Port-Of: odoo/odoo#38867
Due to commit odoo/odoo@f4031c62f97fa170b74b0d13a0856b7d58ed4da6 it was not more possible to scroll in a grouped kanban. Steps to reproduce: * Go to project app * Select a project with a few numbers of task * Create as need new task to have more task than visible on the screen * Try to scroll (BUG) Note: we also fix the swipe in empty column opw-2080491 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39128 Forw
Original PR description
Due to commit odoo/odoo@f4031c62f97fa170b74b0d13a0856b7d58ed4da6 it was not more possible to scroll in a grouped kanban. Steps to reproduce: * Go to project app * Select a project with a few numbers of task * Create as need new task to have more task than visible on the screen * Try to scroll (BUG) Note: we also fix the swipe in empty column opw-2080491 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39128 Forward-Port-Of: odoo/odoo#39103
As we have 100k+ livechat sessions on odoo.com, loading records with the len() is very slow. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39151
Original PR description
As we have 100k+ livechat sessions on odoo.com, loading records with the len() is very slow. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39151
task: https://www.odoo.com/web#id=1952265&action=333&active_id=1691&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.9ffbbcecd07c57eb7f5c9178535645fb 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 Forward-Port-Of: odoo/odoo#38875
Original PR description
task: https://www.odoo.com/web#id=1952265&action=333&active_id=1691&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.9ffbbcecd07c57eb7f5c9178535645fb 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 Forward-Port-Of: odoo/odoo#38875
Description of the issue/feature this PR addresses: Time to load systray messaging menu is too slow. Current behavior before PR: Desired behavior after PR is merged: Now, we avoid to make query for each message. And for attachment's message, we check attachment access rules and search object only if the message has an attachment. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39063 Forward-Port-Of: odoo/odoo#348
Original PR description
Description of the issue/feature this PR addresses: Time to load systray messaging menu is too slow. Current behavior before PR: Desired behavior after PR is merged: Now, we avoid to make query for each message. And for attachment's message, we check attachment access rules and search object only if the message has an attachment. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39063 Forward-Port-Of: odoo/odoo#34863
preparation for cleaning of v13 task-2065018 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 Forward-Port-Of: odoo/odoo#38980 Forward-Port-Of: odoo/odoo#38511
Original PR description
preparation for cleaning of v13 task-2065018 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 Forward-Port-Of: odoo/odoo#38980 Forward-Port-Of: odoo/odoo#38511
Description of the issue/feature this PR addresses: TaskID: https://www.odoo.com/web?#id=2075232&action=327&model=project.task&view_type=form&menu_id=4720 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 Forward-Port-Of: odoo/odoo#38506
Original PR description
Description of the issue/feature this PR addresses: TaskID: https://www.odoo.com/web?#id=2075232&action=327&model=project.task&view_type=form&menu_id=4720 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 Forward-Port-Of: odoo/odoo#38506
The XML file homepage view record is not supposed to be deleted as it is used to bootstrap newly created website. If that view is deleted, everything's fine. But if that view's page is not found (m2o link broken somehow), then the code would crash. This would only appear if the user is playing in the backend in technical but it seems to happen more than it should. This commit will prevent the code to crash in such a case. Step to reproduce: 1. Go to settings > technical > views (
Original PR description
The XML file homepage view record is not supposed to be deleted as it is used to bootstrap newly created website. If that view is deleted, everything's fine. But if that view's page is not found (m2o link broken somehow), then the code would crash. This would only appear if the user is playing in the backend in technical but it seems to happen more than it should. This commit will prevent the code to crash in such a case. Step to reproduce: 1. Go to settings > technical > views (debug) 2. Find the xml homepage view (with xml_id) 3. Go to its website.page and break the m2o view_id 4. Try to create a new website, it will crash opw-2081894 Forward-Port-Of: odoo/odoo#38897
OPW [2083109](https://www.odoo.com/web#view_type=form&model=project.task&id=2083109&active_id=2083109&menu_id=) There are 2 fixes: * We can now sell an asset if the gross increases are closed and with a a zero amount * The closing entry (for sale or disposal) is now counted backwards because it should counter all the depreciations Forward-Port-Of: odoo/enterprise#6060
Original PR description
OPW [2083109](https://www.odoo.com/web#view_type=form&model=project.task&id=2083109&active_id=2083109&menu_id=) There are 2 fixes: * We can now sell an asset if the gross increases are closed and with a a zero amount * The closing entry (for sale or disposal) is now counted backwards because it should counter all the depreciations Forward-Port-Of: odoo/enterprise#6060
Forward-Port-Of: odoo/enterprise#6141
Original PR description
Forward-Port-Of: odoo/enterprise#6141
The OVERIGE KOSTEN is a cost, so it should be subtracted from the income. opw 2081204 Forward-Port-Of: odoo/enterprise#6043
Original PR description
The OVERIGE KOSTEN is a cost, so it should be subtracted from the income. opw 2081204 Forward-Port-Of: odoo/enterprise#6043
For some reason l10n_mx_edi loads several CSV files manually inside the database, without using ORM facilities nor automatic XML IDs. It then generates XML IDs manually inside the database for the loaded records, but without `noupdate` flag, e.g. [here](https://github.com/odoo/enterprise/blob/f80e05da90dc0076b2fd22d49e7d5daa5d7505a5/l10n_mx_edi/hooks.py#L225-L232). Because those XML IDs were never processed by the module loading system, it considers that they are obsolete and proceeds to clea
Original PR description
For some reason l10n_mx_edi loads several CSV files manually inside the database, without using ORM facilities nor automatic XML IDs. It then generates XML IDs manually inside the database for the…
For some reason l10n_mx_edi loads several CSV files manually inside the database, without using ORM facilities nor automatic XML IDs. It then generates XML IDs manually inside the database for the loaded records, but without `noupdate` flag, e.g. [here](https://github.com/odoo/enterprise/blob/f80e05da90dc0076b2fd22d49e7d5daa5d7505a5/l10n_mx_edi/hooks.py#L225-L232). Because those XML IDs were never processed by the module loading system, it considers that they are obsolete and proceeds to clean them up at the end of the module installation (`_process_end()`). This deletion process happens just after inserting the CSV data, which seems rather pointless. In addition, it takes more than 40 painful seconds of 1-by-1 record deletion. Even though this CSV loading code seems like it should be cleaned up, we can at least get rid of the 40s delay by forcing `noupdate=True` on those imported records. That's what this PR does. ---- @luistorresm @nim-odoo Could either of you shed some light on this weird CSV loading stuff, perhaps introduced in 11.0 in `l10n_mx_edi_external_trade` via #1997. Why don't we load normal CSV files? There's a comment about not being able to do *noupdate*, except the manual loading code did not even use it. And the data gets auto-deleted immediately, does that make sense? Together with the downloading of 8MB of XSD files from MX gov, installing the MX localization takes **more than 1 minute**, making it the slowest localization to install by far ;-) It's kind of a showstopper for free trials, as many people leave before the database installation is finished. By the way, are those XSD files required? It looks like the "cached" attachments were being auto-deleted with the rest, so were they even used? /cc @nhomar @jco-odoo Forward-Port-Of: odoo/enterprise#6286
preparation for cleaning of v13 task-2065018 Forward-Port-Of: odoo/enterprise#6226 Forward-Port-Of: odoo/enterprise#6120
Original PR description
preparation for cleaning of v13 task-2065018 Forward-Port-Of: odoo/enterprise#6226 Forward-Port-Of: odoo/enterprise#6120
Prevent the ocr to pick the validation from multiple boxes if there is multiple selected. Forward-Port-Of: odoo/enterprise#6304
Original PR description
Prevent the ocr to pick the validation from multiple boxes if there is multiple selected. Forward-Port-Of: odoo/enterprise#6304