Historically, when Merac have developed customer ticketing sites to be inline with the customer's general website, we have referenced the customer's own Cascading Style Sheets (CSS) files, hosted on their own servers. This brought benefits such as customers being able to control their stylesheets, which will downstream to our ticketing site...
B U T
The Merac site depends on certain CSS content being in a certain format, which means that customers can, inadvertently, break their ticketing site when making changes to their main website. This causes a huge amount of pain for all involved with potential loss of ticketing revenue for K3's customers, and recently these issues have become more frequent.
Policy to eliminate ticketing downtime from website styling changes
Merac will host a copy of the customer's CSS on our site (as well as customers hosting their own copy on their main website)
Impact
The ticketing website will not be broken by main website styling changes.
Any changes customers want to do to their own website will need to be sent to K3 to be applied to the ticketing site as well
This means that, if customers want to make changes to their website styling, you will need to raise a change request through your CSM or Support. We will take a copy of your CSS, apply it, test it, and deploy it with your signoff. This will be a small chargeable consulting project.
This policy change will be rolled out as and when required unless you would like to request it's done now. If any of the following apply, this is the point when we will switch from referring to the main website CSS to hosting a copy on the ticketing website:
- Website Reskin.
- Mini website reskin where navigation and or simple styling changes are done.
- Upgrading website technology (to the newer "bootstrap" version).
This is a simple, proactive solution to prevent ticket purchases being unavailable due to an unexpected change to the main website styling.