The `payment` module introduces a certain amount of payment acquirers, each one corresponding to a `payment_` module. When a `payment_` module is installed, this data is updated so that payments done with the corresponding acquirer change in behaviour using the provider installed by the `payment_` module. When a `payment_` module is uninstalled, this data should be reset to default, more especifically the `view_template_id` and the `provider` fields of `payment.acquirer`. This was not possible before this commit, and more importantly it would make the uninstallation of such `payment_` module impossible as the `view_template_id` is a required m2o ondelete='set null', which will make the registry crash. Even if the former wasn't a problem, the provider field would remain set to a non-existing selection option, which would make the registry crash (eventually, when checking a record with such a selection option). With this commit, we reset these fields to their default value upon module uninstall. In 13, the issue with `view_template_id` should be fixed, as required m2o that are ondelete='set null' are no longer possible. As for the provider Selection field, a fix should arrive in master soon. opw-2225333 closes odoo/odoo#48916 X-original-commit: 4f0c1c1bfd71dd1ff6793d0a91b49984c54d1351 Signed-off-by: Raphael Collet (rco) <rco@openerp.com> Signed-off-by: Adrian Torres (adt) <adt@odoo.com>
20 lines
579 B
Python
20 lines
579 B
Python
# -*- coding: utf-8 -*-
|
|
|
|
{
|
|
'name': 'Transfer Payment Acquirer',
|
|
'category': 'Accounting/Payment Acquirers',
|
|
'summary': 'Payment Acquirer: Transfer Implementation',
|
|
'version': '1.0',
|
|
'description': """Transfer Payment Acquirer""",
|
|
'depends': ['payment'],
|
|
'data': [
|
|
'views/payment_views.xml',
|
|
'views/payment_transfer_templates.xml',
|
|
'data/payment_acquirer_data.xml',
|
|
],
|
|
'installable': True,
|
|
'auto_install': True,
|
|
'post_init_hook': 'create_missing_journal_for_acquirers',
|
|
'uninstall_hook': 'uninstall_hook',
|
|
}
|