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
Community Add Ons | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Community Add Ons

Community Add Ons

Posted: March 22, 2013 at 10:23 am

Viewing 2 reply threads


Jason MacEntee

March 22, 2013 at 10:23 am

We have a client developing a new implementation of Espresso to replace a 3rd party system they are migrating from. Over the coming weeks, they are going to have us add a lot of functionality to Espresso including:

  1. Custom fields added to Events, editable in the admin tool.
  2. Breakout sessions.
  3. Event staffing with WordPress users (with custom public profiles).
  4. A more advanced sync with MailChimp (includes questions, event lists, custom profile fields, etc).

We have started down the road using the Custom Files Add On, but we realize each of these extensions may have value to others in the community.

I’ve search a couple of times, but I have not found guidance on developing Add Ons to share. Is there documentation on how to approach this?

Thanks,
Jason


Chris Reynolds

  • Support Staff

    •

March 22, 2013 at 1:46 pm

Hi Jason —

Not specifically, because our developer documentation is pretty…well, non-existant. My approach would be to build plugins for each of the main items, rather than doing what you’re trying to do with the custom files add-on. So the first step would probably be to crack open one of the add-ons to get an idea of how we’re doing it. Granted, most of the code for the add-ons are in core and, moving forward, we want to avoid that and pull functionality for specific add-ons out into the actual add-ons instead. You’re welcome to email us at support at this domain and we can get you in touch with the dev team if you have questions moving forward with custom add-ons.

~c


Jason MacEntee

March 22, 2013 at 1:54 pm

Chris, thank you for the fast reply. I should have mentioned we are building the MailChimp sync tool as an independent WordPress plug-in and just accessing Espresso data directly. It’s also not my favorite approach since it’s vulnerable to any schema updates you make. Likewise it appears to us any functions we override using Custom Folder we’ll need to DIFF any time there is an Espresso update to make sure we capture any additions you make to base code.

We’ll get “cracking” as you suggest. Thanks.
Viewing 2 reply threads

The support post ‘Community Add Ons’ 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.

The original Forum description...

Status: closed

Updated by Jason MacEntee 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not a support question
Event Espresso - Staging Server