Skip Navigation

[Resolved] building a theatre cms

The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 6 years, 7 months ago.

Assisted by: Christian Cox.

Author
Posts
#562402

I'm trying to build a cms were the client can add production and activities (2 separate things). Each production can have multiple performances. The basic information (like actors, content, image, ...) is the same for all the performances, but each performances can have it's own location, hour and ticketing.

I would like to be able to sell tickets for each performance and for each activity.

What's the best way to set it up? If it is even possible with Toolset?

Thanks.

#562511

Hi, thanks for looking into Toolset. I'll try to help. This is a general overview, but more details are available if you need additional information. You can create separate tickets for each question to get the most helpful support.

I'm trying to build a cms were the client can add production and activities (2 separate things).
CRED can be used to set up forms where your clients can create content from the front-end of your site, and can be used to create content in multiple post types. More information about CRED here:
https://toolset.com/documentation/user-guides/cred-training-course/

Each production can have multiple performances. The basic information (like actors, content, image, ...) is the same for all the performances, but each performances can have it's own location, hour and ticketing.
Okay so it sounds like Production will be a post type, and Performances will be another post type. Performances will be children of a Production. The basic information that is shared across all Performances in a Production can be stored as custom fields on the Production post. Then you can create many Performance posts that have their own custom fields for location, hour and so on.
More information about parent / child relationships:
https://toolset.com/documentation/toolset-training-course/part-8-one-to-many-relationships-in-toolset/
More information about custom fields:
https://toolset.com/documentation/user-guides/using-custom-fields/

Ticketing is something we would need to discuss in more detail to determine the best approach. I assume it will be accomplished with WooCommerce. I assume you will create separate products for each Performance, representing tickets. If you want the product creation process to be automated, so that any time a Performance is added a new Product is automatically created for its tickets, this will require some custom code. The cred_save_data hook will be useful here:
https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data

If you intend to create the ticket Product manually every time a Performance is added, then you can skip the cred_save_data hook.

I assume that your visitors will be able to see a "Add to cart" button appear on each product page, which adds the related ticket product into their shopping cart. This can be accomplished with CRED Commerce and the custom fields from each Performance.
More information about CRED Commerce here:
https://toolset.com/documentation/user-guides/using-cred-commerce-to-add-payments-to-forms/

The forum ‘Types Community Support’ is closed to new topics and replies.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.