Merge lp:~openerp-dev/openobject-addons/7.0-opw-595521-rgo into lp:openobject-addons/7.0
Status: | Needs review |
---|---|
Proposed branch: | lp:~openerp-dev/openobject-addons/7.0-opw-595521-rgo |
Merge into: | lp:openobject-addons/7.0 |
Diff against target: |
42 lines (+9/-2) 1 file modified
anonymization/anonymization.py (+9/-2) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/7.0-opw-595521-rgo |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Naresh(OpenERP) | Pending | ||
Review via email: mp+184541@code.launchpad.net |
Description of the change
Hi,
If anonymization was done on few fields of any custom module, and at the time of reverse anonymization process, if that particular module isn't placed in addons directory(probably reason: the custom module code is not migrated and is not supported with current version yet), then the fields of such models will not going to be unanonymized. So, the state of such fields should not be changed from "Anonymized" to "Clear".
Currently, it changes the state of such fields to "Clear" state and shows the database in stable state, where in-fact, it isn't.
This branch fixes this issue, kindly review it.
Thanks.
Unmerged revisions
- 9423. By Ravi Gohil (OpenERP)
-
[FIX] anonymization: In the reverse anonymization process, the fields, which are still in anonymized state, are marked as Clear and wrongly shows the database in stable state. (Maintenance: 595521)