Tuesday, March 5, 2024
2 changes · saas-17.1
Enhancements to existing features
This update enhances the visual clarity of website slides by increasing the boldness of the section headings. The change adds a priority style to ensure sections stand out more effectively from the surrounding content. This improves the overall user experience and makes it easier for visitors to quickly understand the slide's key points.
Original PR description
Purpose ======= Increase the bold of the sections in back end to better differentiate them from the content. Specifications ============== Adding !important next to the css bold style (value = 700) applied on the sections to make sure it takes the priority over the default list view sections "fw-bold" class (value = 500). Task-3759152 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#154990
This update adds README files to all payment acquirer modules, clarifying the technical details of each implementation. This improves understanding of how payment integrations work and addresses the rapid changes in the online payments landscape, ensuring smoother maintenance and updates.
Original PR description
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is…
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is even implemented as a 'direct payment' flow through an iframe; one payment acquirer could support webhooks while another does not and relies on another mechanism to fetch payment status updates... It can be tricky to guess where to look in the code to determine how a payment acquirer is implemented. On top of that, the online payments ecosystem evolves at a fast pace due to competition, buyouts, and legislation enforcement. Acquirers are thus frequently migrated to new APIs that might differ in implementation from the previous API. To help figure out the *which*, *why*, *how*, and *when* of payment API implementations, a README.md file is added to the main directory of all payment acquirer modules. They can be browsed in human-readable format on GitHub. task-2374916 See also: - https://github.com/odoo/enterprise/pull/56182 Forward-Port-Of: odoo/odoo#156084 Forward-Port-Of: odoo/odoo#153016