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
Using Post Types (in line w/ WP practices) | Event Espresso - Staging Server

Support

Home › Forums › Pre-Releases › Using Post Types (in line w/ WP practices)

Using Post Types (in line w/ WP practices)

Posted: August 5, 2013 at 5:03 pm

Viewing 2 reply threads


Adal Bermann

August 5, 2013 at 5:03 pm

This is not a bug report but rather a feature suggestion/question:

Does the EventEspresso team plan to rebuild the plugin at some point to use a more normal WP database structure by utilizing custom post types, taxonomies and custom fields instead of the custom database tables it currently uses?

Similarly to what WooCommerce is doing for example, it would make things easier for users/devs by tying into what we are already familiar with and provide nice tools like bulk editing (say I want to assign 50 events to a category after creating them…)


Josh

August 5, 2013 at 5:37 pm

Hi Adal,

They’re actually working on this now for Event Espresso 4.1. You can follow the progress and submit pull requests by signing up for access to Event Espresso’s Github account:

http://staging.eventespresso.com/developers/request-repo-access/


Adal Bermann

August 5, 2013 at 6:06 pm

Very cool, thanks for the response Josh!
Viewing 2 reply threads

The support post ‘Using Post Types (in line w/ WP practices)’ 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.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Adal Bermann 11 years, 6 months ago ago

Topic Tags

Tagged: ,

Notifications

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