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
Resolve 3.1 issues or try 3.2.a? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Resolve 3.1 issues or try 3.2.a?

Resolve 3.1 issues or try 3.2.a?

Posted: December 12, 2012 at 12:40 am

Viewing 1 reply thread


Umit Gokce

December 12, 2012 at 12:40 am

I’m helping develop a registration system for a local youth sports program’s signup in January. I’ve been doing UX design work for many years, and I see your plugin as a polished admin tool with really flawed front-end UX.

I’ve compiled a list of issues in trying to setup the system but wonder if your 3.2 release will resolve most of the problems. From the looks of your alpha 1 screenshots, I’d say it could.

Instead of rolling out my list and trying to resolve each issue, do you have an update on when 3.2 will be code complete? Or at least in beta? It’s been alpha 1 since early July, right?

Thanks


Dean

  • Support Staff

December 12, 2012 at 12:57 am

Hi Umit,

We are still trying not to put a forecasted date on beta or final release of 3.2, as it has been pushed back so many times already.

However I can advise that as of now we are limiting other workloads and putting as much focus on 3.2 as possible.

If your events are starting in January I would focus on using the latest 3.1.X as I know 3.2 wont be available by that point.

If you have tested the Alpha version then we would love your feedback.

Viewing 1 reply thread

The support post ‘Resolve 3.1 issues or try 3.2.a?’ 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