|
ardiaful
|
March 19, 2018 at 4:17 am
I plan to create a custom post type (i.e. courses) and I wonder if there is a way to make full use of the EE functionality, not only copying shortcodes (i.e. ticket selector), but to work with CPT the same way as if it were a EE event (using descriptions, venues, and people) and with the same EE admin editing template. Any chance to do this?
|
|
Tony
|
March 19, 2018 at 7:33 am
Hi there,
No, this isn’t possible, or at least not without completely re-writing a large amount of the EE codebase.
EE events are custom post types themselves so if you just want to use the courses slug you can do that within Event Espresso -> Event -> Templates -> Events slug.
If you change that value you will need to flush your permalinks by visiting Dashboard -> Settings -> Permalinks.
If not can I ask what it is you are trying to do with the above?
|
|
ardiaful
|
March 19, 2018 at 12:50 pm
My question is not about changing the slug, but using different CPTs at the same time, i.e. events, courses, …. all of them sharing the same EE functionality, but keeping the admin side separately.
|
|
Josh
|
March 19, 2018 at 1:02 pm
That’s not actually possible, at least not without completely re-writing a large amount of the Event Espresso codebase.
|
|
ardiaful
|
March 19, 2018 at 1:32 pm
In summary, if we are to have two different CPTs (ie. Events and Courses) working at the same time, we would have these two options:
1- Manage both CPTs content separately and use EE shortcodes (i.e. ticket selector, categories,…) to manage the bookingsworkflow. In this case, registrations, contacts, transactions, messages, people, venues….would remain integrated for all CPTs
2- Manage Events with EE, and manage Courses with a different course management plugin (other than EE). In this case the booking workflow would remain fully separated from one another.
Do you agree with these management scenarios, or am I missing something?
|
|
Josh
|
March 19, 2018 at 2:35 pm
If you’re asking my opinion, I don’t agree with either. Why not use a custom taxonomy to separate out courses from regular events?
|
|
ardiaful
|
March 19, 2018 at 2:56 pm
I didn’t think about custom taxonimies indeed. With custom taxonomies your EE slug will stay the same regardless of the taxonomy (i.e. /event/event_name, or /event/course_name). Besides, how do you manage the different fields that you need for each taxonomy (different fields for events and courses), maybe using a plugin like Elliot Condon’s Advanced Custom Fields?
|
|
Josh
|
March 19, 2018 at 3:32 pm
If you need to manage different fields than what’s already there for events, then I’m afraid that’s not the same as what you were asking earlier in the topic.
|
|
Tony
|
March 19, 2018 at 3:52 pm
Would using something like LearnDash + Event Espresso not work better here?
There’s not really enough info above to know the specifics, just that you want EE’s functionality to apply to another CPT but as mentioned, doing so is going to require significant customization
Could you not use LearnDash to manage your ‘courses’, Event Espresso to manage your ‘events’ and the EE LearnDash add-on to link events to courses so that if you register onto an event, you also register onto the course for that event?
|
|
ardiaful
|
March 19, 2018 at 5:25 pm
Courses are not online but clasroom courses for which the customer must buy a ticket, just like an event, therefore LearnDash is not of great help here. Some fields in courses differ from events, such as trainers, syllabus, etc, that’s why I thought maybe with custom taxonomies and custom fields, courses and events could be managed altogether within the EE functionality. Am I wrong?
|
|
Josh
|
March 21, 2018 at 6:33 am
You’re not wrong. You can use the built-in custom fields or add custom custom fields via a plugin like Advanced custom fields.
|
