Ticketshop 1.5 Migration Guideline
1. Activate TS1.5
Go to Backoffice → Institution → Sales Channels → Point of Sales.
Open Internet theme → General structure → Graphical theme.
Choose “Evolution”.
2. Test plan after activation
Follow the OLA Service Hub guideline:
2.1 Functional test
Run a full purchase flow:
Home page → Product → Calendar/Timeslot → Seat map → Cart → Checkout → Payment → Confirmation.Make sure the buying process works fine.
2.2 UI/UX test
Check light customization setup:
Background, header, footer colors.
Text and label colors.
Labels from Backoffice show correctly.
Check disabled buttons, warning messages, and step bar colors.
2.3 Cross-browser test
Test on Chrome, Firefox, Safari, Edge.
Test both desktop and mobile (responsive).
2.4 Regression test
Check that default functions are not broken (example: modify seats for normal events, add product link).
Test multi-language if supported.
2.5 Validation before go-live
Run at least 1 Ticketshop in Preprod before applying to all shops.
Migration to Production only if checklist = 100% pass.
3. Special test for Ticketshops with existing customizations
3.1 Review custom code
Download the zip with custom.css and custom.js.
List all existing custom work (hide/show buttons, popup, style, flow changes).
3.2 Collect customer cases
Get list of Ticketshops with custom work from past Service Cases.
Contact customer tkeep or remove.
3.3 Decide before migration
Remove/disable unused custom.
Keep only confirmed ones and mark them for test.
3.4 Backward compatibility test
Check that old custom is still working in TS.15.
Run full checkout with custom active.
Verify documents and email templates keep the custom.
3.5 Customer sign-off
Share test results with customer.
Ask for confirmation that all required custom works fine.
Go-live Checklist
✅ TS.15 version published
✅ General test (flow + UI/UX + regression) passed
✅ Custom Ticketshops test passed
✅ Customer confirmed which custom to keep/remove
✅ Payment flow full test OK
✅ Rollback plan ready