Skip to main content

Propagate payment mode on SO in website

Beta License: AGPL-3 OCA/e-commerce Translate me on Weblate Try me on Runbot

When creating a SO directly from the website, the field payment mode is not filled with the value configured on the partner. This is a glue module when using account_payment_sale along with website_sale to circumvent this behavior.

Table of contents

Installation

This module is automatically installed if website_sale and account_payment_sale are installed

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Camptocamp

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/e-commerce project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo11-addon-website-sale-payment-mode 11.0.1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo11-addon-website-sale-payment-mode 11.0.1.0.1
File Interpreter ABI Platform Actions
odoo11_addon_website_sale_payment_mode-11.0.1.0.1-py2.py3-none-any.whl Python 3, Python 2 none any Details for odoo11_addon_website_sale_payment_mode-11.0.1.0.1-py2.py3-none-any.whl

Release files / odoo11_addon_website_sale_payment_mode-11.0.1.0.1-py2.py3-none-any.whl

Download URL odoo11_addon_website_sale_payment_mode-11.0.1.0.1-py2.py3-none-any.whl
Size 21.0 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
3244b54c2b456f244629a5ab66af64bbbe7769d62629ca61ced9df9ecfa67721
BLAKE2b-256 checksum
How to use checksums
cd8917d7da81b5824b4badf84bb93ae71a9d8ca6471f4eeda935af73f533b9fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3

Security for odoo11-addon-website-sale-payment-mode 11.0.1.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page