Modify Tickera Orders Details Page
you want to customise what shows on the Tickera Order Details page (the one buyers see after a successful purchase, and the one you see in the WordPress admin under each order) — add custom-form responses, change the layout, add quick-action buttons, surface event-specific info. The catch: editing Tickera core files directly gets wiped on the next plugin update.
The right pattern: a small companion add-on
We maintain a small wrapper add-on that introduces a parallel shortcode ([tc_order_details_modified]) and an editable function (tc_get_order_details_front_modified) where you can make all your changes. Because the changes live in your own plugin folder — not Tickera core — they survive plugin updates indefinitely.
- Download: tc-order-details-changed-1.zip
- WordPress admin → Plugins → Add New → Upload Plugin, install, activate.
- Edit your Order Details page (the WordPress page where the order summary appears). Replace the shortcode
[tc_order_details]with[tc_order_details_modified]. - Open
/wp-content/plugins/tc-order-details-changed/index.phpin a code editor. - Find the function
tc_get_order_details_front_modified. Modify the markup, fields, or layout to taste. - Save the file. Refresh an order details page to see your changes.
Typical customisations
- Pull custom-form responses into the order summary so buyers see what they entered at checkout. See show Custom Forms data in order details.
- Add quick links — “Download all PDFs as ZIP”, “Add to calendar”, “Get directions to venue”.
- Reorganize the order — put event name first, then ticket list, then buyer info (instead of the default order).
- Hide fields you don’t want shown — internal reference codes, gateway transaction IDs.
- Brand-specific styling by adding inline classes that hook into your theme’s existing CSS.
Why use the add-on instead of a theme child file
You can put a function with the same name in your theme’s functions.php, but theme-level overrides break when you switch themes. The add-on approach keeps the customization tied to Tickera, independent of the theme — easier to migrate, easier to audit, easier to share with your developer.
For deeper changes
If you need behaviour changes (not just layout) — e.g., conditional content based on event type, real-time data fetched from another API — use the standard Tickera hooks and filters rather than this wrapper.
Related
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.