Attendee Form Erased When Changing Payment Gateways In WooCommerce
your buyer fills in the attendee fields at checkout, then switches the payment gateway (e.g. from Stripe to PayPal), and the attendee fields get blanked — they have to retype everything. This is the fix.
The fix in one line
Add this constant to your wp-config.php file:
define('TC_WOO_DISABLE_FRAGMENTS_UPDATE', true);Place it anywhere above the line that says /* That's all, stop editing! Happy publishing. */. Save the file. Done.
Why this happens
WooCommerce uses “checkout fragments” — small AJAX updates that re-render parts of the checkout page when the buyer changes the payment gateway. The fragment refresh is supposed to update gateway-specific UI (Stripe Elements form, PayPal button, etc.) without a full page reload.
Tickera adds attendee-info fields to the checkout via its own JavaScript. When WooCommerce refreshes the checkout fragments, it re-renders the whole checkout form area — including Tickera’s attendee fields — which gets re-rendered as empty because the form values aren’t part of the fragment payload.
The constant above tells Tickera to disable the fragments-update behaviour that’s responsible for this. Buyer types attendee info, switches gateway, attendee info stays.
Trade-off
With the constant on, the WooCommerce checkout still works — payments still process, orders still complete — but the checkout no longer does its little AJAX refresh on gateway switch. Most users never notice the difference; the cost is purely cosmetic.
If editing wp-config.php scares you
You can also add the same constant via your child theme’s functions.php:
if ( ! defined( 'TC_WOO_DISABLE_FRAGMENTS_UPDATE' ) ) {
define( 'TC_WOO_DISABLE_FRAGMENTS_UPDATE', true );
}Either location works — wp-config.php is the canonical place, but functions.php is fine for users who’d rather not touch wp-config.
Related
- Configuring WooCommerce settings
- Custom Forms add-on
- Bridge for WooCommerce add-on
- Checkout modifications
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.