WooCommerce Clover (ex FirstData Payeezy Gateway) Changelog
Todas las versiones registradas, de la más nueva a la más antigua, con lo que cambió en cada una.
Última 5.5.215 versiones
Sin fecha · 15 versiones
5.5.2
Última
3 correcciones
Corregido
Clarify the partial capture setting description
Improve masking of sensitive data in debug logs
Only allow a customer to delete their own saved card when removing a subscription-tied payment method
5.5.1
1 corrección1 cambio
Corregido
Address an issue in some installs where saved card migration to Clover stopped after the first batch; stalled migrations resume automatically after updating
Cambios
Misc - Explain when no saved cards could be migrated because the Clover account is not set up to convert them, instead of a generic failure notice
5.5.0
1 nuevo1 corrección
Nuevo
Migrate saved cards from the retired Payeezy gateways to Clover, so customers keep their saved cards and subscription renewals
Corregido
Prevent a declined card from blocking further payment attempts in the block-based checkout
5.4.1
1 cambio
Cambios
Misc - Warn merchants on legacy First Data gateways (Payeezy, Payeezy Gateway, Global Gateway) to switch to Clover before they are retired
5.4.0
2 mejoras2 correcciones3 cambios
Mejora
Pass the WooCommerce customer ID to Clover when creating a charge
Add a filter to pass the customer billing name, email, phone to Clover charges so they appear in the transactions list
Corregido
Subscription renewals should not fail with a missing payment token when the original subscription is purchased through the Blocks checkout
Replace deprecated `wc_enqueue_js` with `wp_add_inline_script` to address some WooCommerce deprecation notices
Cambios
Misc - Improve compatibility with more recent PHP versions
Misc - Update the SkyVerge Plugin Framework to v6.2.0
Misc - Require WordPress 6.3 or newer
5.3.3
1 mejora1 cambio
Mejora
Trim whitespaces from postcodes at checkout to minimize AVS postal code mismatch errors in some cases
Cambios
Misc - Strip sourcemap comments from minified JS and CSS files in release builds to prevent browser console warnings
5.3.2
1 mejora1 corrección
Mejora
Improve error messaging when API credentials are invalid or unavailable
Corregido
Do not bundle JavaScript .map files in the release to avoid console errors
5.3.1
1 corrección
Corregido
Ensure the checkout works properly with the WooCommerce shortcode checkout
5.3.0
2 correcciones1 cambio
Corregido
Ensure the card holder name is shown on the checkout block fields when enabled
Address WordPress deprecation notices concerning translations loading too early
Cambios
Misc - Update SkyVerge Plugin Framework to v5.15.12 (along with various security and bugfix updates)
5.2.9
1 corrección
Corregido
Bump the framework version constant to the correct version
5.2.8
4 correcciones1 cambio
Corregido
If a customer deletes their payment method directly by following an email response from Clover, ensure that it can be manually removed in WooCommerce as well
If a customer is deleted in Clover, ensure that payment methods can be deleted in WooCommerce without error
Ensure the "Capture Charge" bulk action is not shown on screens other than orders
Account for Subscriptions Core library when checking for Subscriptions
Cambios
Misc - Update SkyVerge Plugin Framework to 5.15.2
5.2.7
1 nuevo
Nuevo
Add setting to enable AVS Cardholder name field on checkout
5.2.6
1 mejora
Mejora
Allow changing payment method on subscriptions that aren't active when Clover is the set payment method
5.2.5
1 corrección
Corregido
Do not show non-configured gateway notes in the admin area if the merchant has switched over another configured gateway
5.2.4
1 corrección
Corregido
When adding a payment method from the My Account area, a pending draft order should not be created
Changelog publicado por el desarrollador, en su idioma original.
