Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[12.0] Issue when installing payment_stripe after account_usability #115

Open
hparfr opened this issue Apr 15, 2020 · 1 comment · Fixed by #116
Open

[12.0] Issue when installing payment_stripe after account_usability #115

hparfr opened this issue Apr 15, 2020 · 1 comment · Fixed by #116

Comments

@hparfr
Copy link
Member

hparfr commented Apr 15, 2020

When installing payment_stripe (Odoo SA), the hook create_missing_journal_for_acquirers is called.

It sets default_debit_account_id here https://github.com/odoo/odoo/blob/12.0/addons/payment/models/payment_acquirer.py#L258
with defaults values here: https://github.com/odoo/odoo/blob/12.0/addons/account/models/chart_template.py#L153

Then the check will stop the installation of the module here : https://github.com/akretion/odoo-usability/blob/12.0/account_usability/account.py#L238

@alexis-via any clues how we can solve this issue ?

ping @PierrickBrun

@alexis-via
Copy link
Member

Moi, je trouve que c une connerie de créer le compte avec un type "current asset"... après ça peut poser des pb si on utilise l'interface de travail des relevés bancaires, on n'a plus les lignes en bleu (je crois), etc... ; ils feraient mieux de le créer avec un type liquidity. Donc on pourrait hériter cette méthode https://github.com/odoo/odoo/blob/12.0/addons/account/models/chart_template.py#L130 dans account_usability pour lui mettre le bon type. @sebastienbeau tu en penses quoi ?
Sinon, on vire la contrainte dans odoo-usability...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants