summaryrefslogtreecommitdiff
path: root/addons/payment/models/__init__.py
AgeCommit message (Collapse)Author
2019-07-09[FIX] payment: translated in frontendNicolas Lempereur
Same reason as: 4ba4d61903b Some messages from payment are displayed on the frontend (eg. when the transaction is being done on the ecommerce), but only translations of module matching a given domain (computed with the method of ir.http model: _get_translation_frontend_modules_domain) are made available on the frontend. With this changeset, payment is added in the domain (which can be done since payment depends on account, account on portal, and portal in http_routing that declares the method). opw-2033528 closes #34712 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>
2018-07-20[ADD] account: onboarding panel for invoicingeco-odoo
Add an onboarding panel for invoicing, it appears above the invoice list. After going through the steps the system should be all set to send real invoices. In the payment module, add a payment acquirer step and add it to the invoice onboarding panel. task: 60668
2018-05-23[REF] account,payment(_*),sale*: downgrade transactions into debug itemsqdp-odoo
It was very confusing for the user to distinct account.payment and payment.transaction. From now on, the transactions are technical objects and, in the backend, we only refer to it in log messages (Front end will be adapted in the same fashion later on). They are hidden in debug mode in accounting\configuration\payments as their purpose is now purely technical/log This commit also aims to reduce the gap between the accounting app and the transactions: account.payment objects are created/validated upon completion of transaction. To ease the capture/voiding of pending transactions, the related buttons are now displayed directly on the SO/invoice instead of the transactions. Was task: https://www.odoo.com/web#id=35857&view_type=form&model=project.task&action=333&active_id=967&menu_id=4720 Was PR #24043 [FIX] add domain based on journal to payment tokens Was opw: https://www.odoo.com/web?debug#id=1828206&view_type=form&model=project.task&menu_id=5200
2017-04-28[FIX] Various P3-related import changesxmo-odoo
* LDAP import: python-ldap is not python3-compatible, pyldap is Warning: only supported from debian Stretch (current testing)? https://packages.debian.org/search?searchon=names&keywords=pyldap * implicitly relative imports * imports of moved or removed stdlib modules issue #8530
2017-04-08[IMP] account: misc UX improvementsFabien Pinckaers
Allow to configure the bank statement import mode from kanban When doing a manual journal entry, don't show the maturity date Removing Issued total, using credit instead (less code, more useful to have due amounts, instead of overdue) Creating a bank, set a name 'BofA Current' and an account number (that way, the account.account is based on name) Settings Wizard & menus: better sentences Statement CSV Import: installed by default (it does not add any menu) remove use_in_payment: complex field, only used for a default value Small code cleanup [IMP] sale: moving order date to secondary tab (strange on a quotation)
2017-01-04[IMP] account,payment: account journal visibilityJérome Maes
Remove field 'display_on_footer' to stop displaying account journal on report documents. As the field is removed but also used in payment to generate default 'Thanks Message', put a new field on account.journal in payment module, to keep the role 'display_on_footer' had in payment.
2016-06-17[IMP] payment: add options to automatically confirm SO's through websiteJoren Van Onder
Introduces two new options: - confirm_so: to confirm the sale order on acquirer confirmation - generate_and_pay_invoice: confirm_so + generation of invoice and payment registration
2016-03-10[IMP] payment, payment_*: acquirers installationMartin Geubelle
The installation of a new acquirer was a bit complicated : from settings, check the acquirer, then apply (install the module) then list view of acquirer and finally edit it in form view. This needed to be simplified. The payment acquirers are pre-filled in payment. From the kanban view an `Install` button installs and redirects to the form field.
2015-06-15[IMP] payment: add support for server2server paymentsDamien Bouvy
This commit adds a new model, Payment Method, which stores a reference to the payment acquirer's database and a reference to a partner. Each payment module must have its own implementation. The implementation is completely abstract but may not suit every provider's way of implementing recurring payments.
2014-01-23[IMP] payment_acquirer_paypal: paypal account integration in payment_paypalThibault Delavallée
- added a call to _migrate_paypal_account in the payment_paypal data that does the migration from company.paypal_account (char field) to a payment.acquirer and company.paypal_account becoming a function field, with a getter / setter. This function field is company aware. - added an update of the res_config view of invoicing to link to the list of acquirers - added possibilty to install acquirers from invoicing (paypal / ogone / adyen are installable through config) bzr revid: tde@openerp.com-20140123150135-07b4pkbjade6vimq
2014-01-22[RENAME] payment_acquirer_* -> payment_ *Thibault Delavallée
bzr revid: tde@openerp.com-20140122175702-1h1e51z4njt4s70w