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
How can we help with 3.2? | Event Espresso - Staging Server

Support

Home Forums Pre-Releases How can we help with 3.2?

How can we help with 3.2?

Posted: December 6, 2012 at 1:15 pm

Viewing 3 reply threads


sboisvert

December 6, 2012 at 1:15 pm

Hi there, I was wondering how we could help with 3.2. We’ve run into a few bugs and ods are you’re aware of them (and some of them are probably addressed already). Since we want to help I’d like to know what is the best way we could do this. How can we contribute to alpha 2?

Thanks!


Josh

December 6, 2012 at 2:04 pm

Hi there,

Thanks for the offer. I’ll check with the dev team to see what we can do to make this happen.


Garth

  • Support Staff

January 3, 2013 at 3:15 pm

Hi sboisvert, Please fill out this form to request access to our 3.2 GitHub repo: http://staging.eventespresso.com/developers/request-repo-access/ https://github.com/eventespresso/event-espresso-core


Josh

February 10, 2014 at 12:33 pm

Hi there,

I wanted to let you know that Event Espresso 4.1 beta (which supersedes 3.2) is officially released. Please see our announcement for more information:

http://staging.eventespresso.com/2014/02/event-espresso-4-beta-officially-released/

Viewing 3 reply threads

The support post ‘How can we help with 3.2?’ 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