|
Nigel Woolcott
|
August 17, 2015 at 4:50 pm
I’m trying out EE3 as EE4 is giving Fatal Errors on my theme.
I am wanting to use the template UI to remove the ical icon on the registration page. The documentation says: With version 3.1.29 we have brought you iCal calendar integration for your events. You can enable this via the Template Settings.
I am running Event Espresso version 3.1.37.5.L and this option is not showing.
I can remove some things in custom css but would rather use the integrated switches.
Any ideas? Maybe this template switch is only available on the Pro version? I’m loathe to buy a plugin that I can’t test thoroughly first.
|
|
Jonathan Wilson
|
August 17, 2015 at 5:09 pm
Hello Nigel,
First off, what fatal error are you getting in your theme? I highly recommend getting that fixed. Honestly, ignoring that error is not the best way to approach this issue.
Secondly, yes, the iCal option is only available in our premium plugin for EE3.
I am happy to answer anymore questions you might have.
|
|
Nigel Woolcott
|
August 18, 2015 at 1:19 am
Hi Jonathan
Thank you very much for responding so quickly.
I have been testing numerous plugins trying to find one that will simply give me a simple registration form and payment structure. Event Expresso was virtually my last chance as I seem to be getting conflicts which i do not have the expertise (or time) to solve as I have a short deadline to get this sorted.
I am trying to replicate something similar to this:
http://www.npbtc.org.uk/#/online-show-entry-form/4570792572
As you can see it has a very simple structure and at the bottom has multiple registration payments.
If I could build something like this using Expresso then I would purchase, but I cannot seem to get all the functions – unless I purchase and then I don’t know if I will have all the tools.
As for the Fatal error – I was going to submit that, but though it was a conflict and it doesn’t happen in EE3 – I’m just up against getting this thing done.
|
|
Tony
|
August 18, 2015 at 4:17 am
As for the Fatal error – I was going to submit that, but though it was a conflict and it doesn’t happen in EE3 – I’m just up against getting this thing done.
EE4 is not simply an update to EE3 but a completely new system built from the ground up so issues with EE3 will often not effect EE4 and vice versa because they function in completely different ways.
However, fatal errors usually indicate a further problem and working around that often will just force the error to show elsewhere.
Can you provide further details on the error that was shown?
Both EE3 and EE4 can provide the registration form your looking for, however EE4 will be a better choice due to the pricing structure you have. Neither provide the same set up you currently have but it can be re-created easier with EE4 than EE3.
We do provide demo sites:
Test Drive Event Espresso
Test Drive Event Espresso 4
Which allows you to see the full functionality of both versions of the plugins.
|
|
Nigel Woolcott
|
August 18, 2015 at 8:29 am
I’ve had a look through the test drive on 4. It’s far too involved and complicated for the type of event registration I am looking for. Thanks for your help anyway.
|
|
Garth
|
August 18, 2015 at 3:56 pm
Any feedback about what seemed too involved or complicated? It literally only takes 20 seconds to setup an event.
|
|
Nigel Woolcott
|
August 18, 2015 at 4:31 pm
Hi Garth
I think that I’m up against too many deadlines to be able to get what I want quickly out of the the plugin. Yes, it is quick to set up an event, but not in the format that I require. There are too many ‘extra’ parameters that I don’t need and no visible way of disabling them.
As you can see from the example registration form, it’s fairly basic and i think I’m over-egging the problem by choosing a sophisticated plugin like Expresso.
|
|
Dean
|
August 19, 2015 at 5:15 am
Hi Nigel,
Thanks for your feedback, it’s really helpful to learn what stumbling blocks new users may face.
There are some settings in the Event Espresso > Events > Template tab page that can remove some of the elements from the events on the front end.
|
