[Resolved] I want to create and manage hundreds of custom post types, content templates.

[Author]

Posts

[Vane]

I want to create and manage hundreds or even some thousands of custom post types, content templates with Toolset Pack.
What is the Toolset Pack limit to do so?
Is there any special setting modification required (like max_input_vars etc.)?
How can I easily manage them in WP backend? Viewing, searching, filtering, displaying their relations etc.
Thanks!

[Christian Cox]

What is the Toolset Pack limit to do so?
There is no limit enforced by Toolset for the number of Custom Post Types or Content Templates, as far as I know, but working with a massive number of post types isn't going to be very practical in WordPress, even without Toolset. WordPress's wp-admin area isn't designed to be optimized for a massive number of custom post types. The main menus aren't easily managed or consolidated, and each of those 1000 post types will be created as main menu items. A 1000 item menu isn't really usable, you could spend minutes scrolling through the menus to find the item you want, and the browser performance of an HTML page with 1000s of items like this may be poor.

Another example, when you create a custom field group or custom taxonomy in Types, you will have the option to assign that group/taxonomy to one or more custom post types. This interface will have hundreds or thousands of checkboxes with no organization or filtering, and is better geared towards sites with fewer custom post types. Similarly, the dashboard at Toolset > Dashboard lists post types and provides information about their templates, fields and taxonomies. When the number of CPTs gets very high, this page may perform poorly. Site performance will always be affected by the amount of content in your database.

Is there any special setting modification required (like max_input_vars etc.)?
You will very likely need to increase your max_input_vars settings, as well as your memory limits.

How can I easily manage them in WP backend? Viewing, searching, filtering, displaying their relations etc.
Toolset doesn't provide many options for organizing or managing the menus in wp-admin, so each custom post type will be added to the main menu. If you want to consolidate or organize those menus, you'll need to look for another 3rd party system that provides that capability. Searching for custom posts in wp-admin is similar to searching for standard posts. You can go to the Dashboard for that CPT, where you have the ability to use a standard text search, date filters, sorting by title and date, and post status filters. With custom code, you can add other filters to these admin Dashboards.

To see information about post relationships in general, you can go to Toolset > Relationships.

Each post editor screen contains post relationships editors for each possible post relationship. If a custom post type has hundreds or thousands of relationships with various other post types, then the post editor screen will be difficult to use. It's not optimized for a massive number of post relationship editors, and these are not paginated or searchable.

[Vane]

Hi Christian,

I agree with you, but I don't think I have another option: I create a general, multi criteria rating website, with hundreds or even thousands of different entity types to be rated, like:
restaurants, hotels, soccer teams, music bands, TV shows, actresses, journalists etc., so it is obvious that their rating criterias are different.
That means for me I have to use different custom post types (CPT) for every each entity and also for their ratings
(like: restaurants, restaurant-ratings; etc.). Since I would have different content template (CT) for every each rating entity with their custom rating criterias, finally, so that means if I start with 200 entities (CPT; restaurant), I also should have 200 rating entities (child-CPT; restaurant-rating) and 200 entities (CT; restaurant-rating-content-template) and this 200 is just the beginning ?

My other strong business (not IT!) argument is that - for SEO purposes - I'd use schema.org schemas in my content, so the different CPTs would be marked up with different schemas (like Restaurant) and their properties.

So I either abandon this idea or try to solve it with Toolset.

basically I think modifying some Toolset admin pages (Dashboard, Post Types, Content Templates, ...) and their sections able to be paginated, searchable and filterable ( automatically, for example above 10, 20 or 50 elements to be listed and displayed ) would be a huge help for Toolser users like me.
And I think it is not an issue for a Toolset/Views developer ?
So pls. consider it as a feature request! 🙂

I think this admin page or section pagination option would improve admin area load times in my case.

Do you have a reference site with huge numbers of Toolset entities, just to test its performance?
How many Toolset entities does it have approximately?

Thank you!

[Shane]

Hi Vane,

Christian is currently on vacation so I will be handling this issue for you.

The feature request you will need to open a separate ticket for this and mark it as a feature request ticket.

Now to the issue at hand.

I was think that you will have multiple CPT over 100 or a 1000 i would assume which as christian mentioned is not entirely practical.

The way I would do it is to create a single cpt and use Taxonomies to separate them. This means that users would be able to search on the frontend by selecting the category of post that they want.

This is just a suggestion as an alternative. Your method can work but it will come with performance hits.

Finally we don't have a large demo site that you can have a look at per say but we do have a list of demo sites that you can have a look at .
https://discover-wp.com/site-templates/

Thanks,
Shane

[Vane]

Hi Shane,

you might missed some:
I can not use 1 CPT and custom taxonomy, because (like I wrote):

a) "That means for me I have to use different custom post types (CPT) for every each entity and also for their ratings
(like: restaurants, restaurant-ratings; etc.). Since I would have different content template (CT) for every each rating entity with their custom rating criterias, finally, so that means if I start with 200 entities (CPT; restaurant), I also should have 200 rating entities (child-CPT; restaurant-rating) and 200 entities (CT; restaurant-rating-content-template..."

So every each Rating CPTs has their own, custom rating criteria Content Templates ( eg. Restaurant Rating CT ), which would be used in the CPTs ( eg. Restaurant Rating CPT ), therefore they have to have distinct parent CPTs ( eg. Restaurant CPT )

b) "I'd use schema.org schemas in my content, so the different CPTs would be marked up with different schemas (like Restaurant)..."

If I'd use only one CPT, I would not be able to markup them with different schema markups...

Pls. note I've opened a feature request ticket about it.
I hope OnTheGoSystems takes it seriously! 🙂

Thanks!

[Shane]

Hi Vane,

Thank you for the clarity.

Yes then for your case multiple CPT's will be needed and as Christian mentioned you will eventually need to increase the "max_input_vars" variable for php once you start populating the site.

Thanks,
Shane