RaCar Checkout Manager for Brazilian Stores

0.6.0 – 2026-05-15

• WooCommerce REST API: exposes Brazilian checkout fields on orders and customers (billing.cpf, billing.cnpj, billing.number, billing.neighborhood, persontype as F/J, etc.) for Bling and similar integrations — no new public endpoints; uses existing WC REST permission checks.
• Order persistence: mirrors extra field meta as _billing_* / _shipping_* alongside existing keys for compatibility with legacy Brazilian Market data.

0.5.1 – 2026-05-15

• Checkout account field validation: fixed required checks for account_username and account_password to use WooCommerce account keys (instead of legacy billing_* prefixes), preventing false “required field” errors when those fields are filled on checkout.
• CEP autofill (classic checkout): while “searching” or “not found” feedback is shown, the next field row reflows as a full line below the postcode field (Storefront-like behavior) via a temporary row-break element — no changes to form-row-first / form-row-last / form-row-wide classes.
• CEP autofill: initial lookup on page load waits until checkout layout is ready (updated_checkout or window load) to avoid a brief broken layout flash.
• CEP autofill: manual address lookup runs as soon as 8 numeric digits are entered (input event); non-digits (e.g. hyphen from mask or manual typing) are ignored — lookup no longer waits for leaving the postcode field (blur).

0.5.0 – 2026-05-13

• Checkout Fields (Tab 1): optional Preserve two-column row layout on small screens (default off) for classic checkout — under max-width: 768px, scoped inline CSS restores form-row-first / form-row-last and three-column helper classes when themes stack fields full width; form-row-wide stays full width; form-row-first uses clear: both (with wide / three-col exclusions); checkout labels use font-size: 70% in that mode to reduce row misalignment; block checkout unaffected; FAQ entry added
• When plugin Select2 is disabled: SelectWoo/select2 removal is limited to checkout, My Account, and cart by default so third-party Select2 (theme filters, variations, etc.) keeps working site-wide
• Developer filter rbsmhao_force_legacy_global_selectwoo_strip (returns bool, receives settings array): return true to restore the previous site-wide strip behavior on stores that depended on it
• Checkout Fields (Tab 1) dimensions: when select height is set, inline CSS aligns text-only country rows (themes/filters that remove the country select and leave markup inside #billing_country_field / #shipping_country_field .woocommerce-input-wrapper) using scoped display:flex, min-height, and optional select line-height — not a global span.woocommerce-input-wrapper rule (avoids breaking other fields)
• Same dimension block: checkout select.country_to_state / select.country_select and My Account select.country_to_state get native height rules even when the theme drops rbsmhao-select-field on the country row
• Checkout frontend CSS: scoped clear: both on .woocommerce-checkout .woocommerce-shipping-fields so “Ship to a different address?” is not pulled beside floated billing rows (e.g. some Woodmart layouts)
• Birthdate: stored and validated as d/m/Y (Brazilian); legacy Y-m-d values in customer meta are normalized on checkout default; input mask treats ISO Y-m-d prefill before applying dd/mm/aaaa

0.4.1 – 2026-05-06

• Checkout Fields (Tab 1): added optional field dimension controls for classic checkout (separate height/line-height for all checkout selects and for text inputs); empty values inherit theme defaults
• Checkout frontend: unified select sizing model for native WooCommerce selects and Select2-rendered selects using the same checkout-scoped selectors/tokens (.woocommerce-checkout, rbsmhao-select-field) to reduce cross-theme mismatch
• Select2 frontend CSS: removed broad global overrides and reduced reliance on !important; styles are now scoped to checkout/plugin context to lower risk of theme conflicts
• Checkout layout compatibility: added optional Classic Checkout Layout (Float Compatibility) toggle (default off) with scoped clear: both behavior for form-row-first plus exclusions for wide rows and plugin three-column helper classes
• Documentation: expanded FAQ/troubleshooting with root-cause notes for float layouts (PF/PJ visibility changes, WooCommerce country_to_state row-class changes, and postcode class restore flow)
• Checkout locale integration: added support for WooCommerce woocommerce_get_country_locale_base and woocommerce_get_country_locale_default hooks (priority 20) in addition to woocommerce_get_country_locale
• Locale formatter internals: split callbacks by payload type (full locale map vs base/default locale fields) and introduced a shared merge helper to avoid duplicate logic
• Locale field classes: country field class enrichment is now idempotent (update_totals_on_change is appended only when missing), preventing duplicate classes in repeated locale passes
• My Account: billing/shipping Edit address (woocommerce_billing_fields / woocommerce_shipping_fields, priority 20) now includes Brazilian extras Number and Neighborhood when enabled in Checkout Fields settings (same visibility rules as checkout via get_active_fields())
• My Account: Checkout Fields dimension settings (select/input height and line-height) and baseline plugin CSS now apply under .woocommerce-account as well as .woocommerce-checkout (registration, edit-address, etc.); Classic Checkout Layout (Float Compatibility) remains checkout-only

0.4.0 – 2026-05-04

• Checkout Fields (Tab 1): optional Classic Checkout Layout (Float Compatibility) toggle (default off) applies a scoped clear: both on form-row-first inside .woocommerce-checkout form.checkout, excluding form-row-wide and three-column helper classes; documented FAQ on PF/PJ visibility, country_to_state, and postcode row class restore
• Registration Form Fields (Tab 4): rff toggles for account_username and account_password follow WooCommerce Account & Privacy (manual username/password), are read-only in the admin UI with notice + link to WC settings, and are forced on sanitize; updated_option / woocommerce_update_options_account keep rff aligned when those WC options change
• Registration: user meta for optional account username/password from the extended registration form now uses WooCommerce keys account_username / account_password (not billing_*)
• Checkout Fields (Tab 1): WooCommerce-synced account username/password (account_username, account_password) — default settings and the checkout reset action now persist enabled/required from WooCommerce Account & Privacy (woocommerce_registration_generate_username, woocommerce_registration_generate_password); first-install activation uses the same default merge base instead of schema-only enabled => false
• When WooCommerce Account settings change, stored checkout field flags are reconciled if enabled/required for those account fields diverge (hooks: woocommerce_update_options_account, updated_option on the two registration options above)
• One Account Per CPF/CNPJ (Tab 3): “Use CPF or CNPJ as login username” (cpf_login) is available only when WooCommerce Generate account login is enabled; otherwise the toggle is off, read-only, with notice + link to WooCommerce → Settings → Account & Privacy, hidden input forces cpf_login off on save, and sanitization blocks forged POST values
• When WooCommerce disables generated account login (woocommerce_registration_generate_username → no), cpf_login is persisted off (woocommerce_update_options_account, updated_option); turning WC generation back on unlocks the toggle without auto-enabling the plugin option
• ROAPC: cpf_as_username and duplicate-login checks honour the same WooCommerce rule; CNPJ path now respects cpf_login instead of the non-existent cnpj_login key

0.3.5 – 2026-05-02

• Uninstall: records an informational entry in WooCommerce → Status → Logs (log source racar-checkout-manager-uninstall) with the user performing the uninstall (when available) and which plugin options were deleted; requires WooCommerce active and WC logging enabled per store settings
• Uninstall: fires the rbsmhao_plugin_uninstalled action so developers can persist an audit trail elsewhere (payload: user_id, user_login, uninstalled_at, options_deleted)

0.3.4 – 2026-05-01

• Checkout: added RBSMHAO-checkout-frontend-style.css (order notes / additional fields full-width when shipping row float layout breaks)
• Restored ViaCEP as a fallback CEP lookup when BrasilAPI fails or returns no valid address (same REST proxy racar/v1/cep/{cep})
• Documented BrasilAPI + ViaCEP behaviour under External Services for WordPress.org transparency

0.3.2 – 2026-04-30

• Restructure of the RBSMHAO_Checkout_Fields class into smaller files, optmizing the load
  • Refactored checkout responsibilities into dedicated modules (schema, settings normalizer, sanitizer, validators, persistence, address formatter, and field filter)
• Standardized boolean operators in PHP codebase (AND/OR replaced by &&/||)
• Fixed One CPF/CNPJ registration validation flow that could allow duplicate CPF/CNPJ registration in some scenarios
• Fixed registration data persistence for first and last names on account creation flows
• Added order_comments management in Checkout Fields Tab with controls for enable/disable, label, placeholder, and required
• Improved first-activation migration to import existing WooCommerce field settings from billing, shipping, and order sections (including order notes)
• Registration Form Fields (Tab 4) now lists only billing fields, preventing shipping/order fields from appearing there
• Added safe key handling for ROAPC rff reads in Tab 4 to avoid PHP Undefined array key warnings on partial/legacy settings arrays
• Added synchronization between Checkout Tab (Tab 1) and ROAPC settings so rff follows persontype, CPF/CNPJ toggles, and company_as_name
• Added PF-only guard: when persontype is PF and Billing Company is disabled, company_as_name is automatically turned off and rbsmhao_one_cpf_settings[rff][company] is forced to 0 on save
• Added Tab 4 blocked-field behavior and contextual tooltips for:
  • first_name/last_name when PJ-only + Company as Name is enabled
  • company when PF-only + Billing Company is disabled
• Improved Tab 4 accessibility by associating text labels with their form controls via matching for/id attributes (fixes DevTools warning: “A <label> isn’t associated with a form field”)
• Stopped loading unused Select2 admin stylesheet (RBSMHAO-select2.css); Select2 styling remains only on the storefront when the option is enabled
• Checkout frontend script (RBSMHAO-checkout-fields-frontend-script.js): when #billing_persontype is absent (e.g. PF-only/PJ-only checkout), initialization returns immediately so no MutationObserver is attached (this was the main performance fix; previously every DOM childList mutation still invoked the toggle path and spammed the console). When the field exists, childList updates are coalesced with requestAnimationFrame, and the old debug console.log was removed
• Fixed wp_register_script URL for the checkout frontend script to use the correct filename casing (RBSMHAO-checkout-fields-frontend-script.js) so the asset loads on case-sensitive hosts (separate from the observer/console issue above)
• Improved and standardized the save settings button in all tabs.
• Admin: sticky save bar on every settings tab (checkout fields, autofill, One CPF tabs) so the save row stays visible while scrolling long forms.
• Checkout: Brazilian extra shipping fields are validated only when “Ship to a different address?” is checked (and the cart needs a shipping address), aligned with WooCommerce so empty shipping extras do not block checkout when billing address is used for shipping.
• Checkout Fields (Tab 1): added WooCommerce account username and password as billing-managed fields (account_username, account_password), relocated from the account fieldset into the billing block for layout; visibility follows WooCommerce Account & Privacy settings (manual username/password); admin toggles for enable/required are locked with a link to WC settings; label, placeholder, priority, and CSS classes remain editable.
• Checkout: account username/password use server-side required when registration is mandatory (no guest checkout); when guest checkout is optional they stay optional until “Create an account?” is checked; companion script syncs visibility and required markers (asterisk / validate-required) so users are not shown “optional” for fields that must be filled.
• Checkout validation: registration-required orders rely on WooCommerce required-field checks for empty username/password; plugin avoids duplicate notices and keeps username format validation when relevant.

0.3.1 – 2026-04-26

• Removed ViaCEP because of lack of documentation/terms of use

0.3.0 – 2026-04-23

• Added option to save Company as Name
• Added option to register CPF/CNPJ as username One CPF tab
• Added registration form fields Manager
• Added option to make all fields wide on registration form
• Fixed several nonces throughout the plugin
• Removed function RBSMHAO_Checkout_Fields::render_user_profile_fields()

• Removed function RBSMHAO_Checkout_Fields::save_user_profile_fields()

• Tested on latest and greatest: PHP8.4, WP6.9, WC10.6

0.2.3 – 2026-04-19

• Fixed persontype field (was person_type)
• Fixed the validation logic based on admin settings
• Added funcionality: At activation, it gets data (priority, label, placeholder, required) from actual checkout fields in order to maintain compatibility
• Added the default WooCommerce fields to allow edition by user
• Fixed address display on orders
• Altered plugin slug from racar-brazilian-stores-must-have-add-on to racar-checkout-manager-for-brazilian-stores as per wp.org rules
• Updated translation to pt-BR.
• Tested on latest and greatest: PHP8.4, WP6.9, WC10.6

0.1.0 – 2026-03-15

• Initial release.
• Added CPF, CNPJ, RG, and other essential checkout fields.
• Integrated address autofill using CEP with BrasilAPI and ViaCEP.
• Added input masks for CPF, CNPJ, and cellphone fields.
• Fully compatible with WooCommerce HPOS.
• Translation-ready.