I am implementing EE4 for the first time and I prefer to have the ticket information page and the ticket selector as one page. After reading some posts on this forum, I have managed to accomplish this and have hosted a POC at this URL. Be sure to click on the ‘Buy Now’ button.
Basically, I’m seeking validation on whether I have done the customization correctly or not. The way I have done this is as follows:
Customize the ticket selector page as much as possible from the ‘Templates’ section of Event Espresso.
After customization use the form and its elements (including hidden tags and exact element id’s and attributes) from the ticket selector page generated by EE4 (In my case it is this URL) and design my own HTML form around it.
Functionally, it seems to work and after selecting tickets and submitting, it does navigate to the registration page. I am quite happy with this.
I would appreciate if the experts on this forum could do a quick review and let me know of any pros and cons of this method of customization or if I have missed out on anything.
I’m afraid we generally do not assist with customization projects. The reason being is because if we did, then there could be an expectation that we’ll also support those customizations long term.
I can advise that you will likely need to maintain these customizations going forward. For example, if in the future the Ticket Selector changes so that it passes a new input to the form, your customizations will also need to be updated when updating to the new version. So a good strategy will be to set up a staging server that has the customizations, and test there before deploying to the live site.
The support post ‘Implementing a custom Ticket Selector Form’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.