Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Suggestions/Ideas for future | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Suggestions/Ideas for future

Suggestions/Ideas for future

Posted: December 4, 2012 at 2:26 pm

Viewing 0 reply threads


culpdesign

December 4, 2012 at 2:26 pm

Have been using EE since the summer, and for our first event it worked pretty good. I set up our event with 4 different event option listings, 1 for each of 4 different prices/options. Was not too bad as long as folks registered under the correct option link. So we used it again for a Christmas event, and we made only 1 event with a Free Registration/$25.00 ticket option. We had lots of missed or incorrect registrations this time, and I think it comes down to the front end user interface (UI/UX). I think the front end could be better designed to make things clearer. If over 1/3 of our registrants couldn’t figure out a ticket choice pull down there may be something to look into. I had asked previously, and yes I could edit the CSS, but I’ll be honest, I’m a decent designer, but not that great at adjusting WordPress to that extent. And I could not find much about interface stuff in the Search.

So not sure what you may have on deck for v3.2 that is coming up soon. If this has not been addressed, perhaps it could be. You have a nice product and your support is always very helpful. Thanks for listening.

Viewing 0 reply threads

The support post ‘Suggestions/Ideas for future’ 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.

Event Espresso - Staging Server