Hello does toolset types custom fields almost double the number of metadata saved in the postmeta table compared to regular WP custom fields?
Is toolset types only for small websites? Is it scalable for bigger projects? i.e.: what if I wanted to store all 3M + youtube channels (YouTube api) in my database?
Is there a way to store my meta data in custom database table?
I stumbled across this plugin hidden link and was wondering if this plugin could integrate with toolset? at the moment it's only integrated with ACF.
Is there a chance you guys can collaborate with the hookturn team since they already collabed with ACF?
Regards,
Nick
Hello does toolset types custom fields almost double the number of metadata saved in the postmeta table compared to regular WP custom fields?
1 Types custom field = 1 postmeta entry, per post, and repeating fields create an additional postmeta entry per repetition per post. Aside from custom fields, Toolset does save some other information in the postmeta table, like JavaScript associated with Views and Content Templates. Those hidden field entries can add to the overall postmeta table size, but aren't directly related to custom fields.
Is toolset types only for small websites? Is it scalable for bigger projects? i.e.: what if I wanted to store all 3M + youtube channels (YouTube api) in my database?
There's no simple answer, it really depends on what you want to accomplish and your measurements for success. Storing 3M posts in the database isn't a problem for Toolset any more than it's a problem for WordPress itself or MySQL in general. But anytime you add content, relational database queries will inherently take longer. If you have millions of posts in hundreds of many-to-many relationships with a dozen custom fields applied to the intermediary posts, complex filter queries can be resource-intensive and result in slower page loads. You can implement a caching system to help speed that up some but it won't help much on custom search forms that allow Users to add other filter criteria.
Nested Views can be resource-intensive, even on smaller sites. For example a View of posts that includes a nested taxonomy View filtered by the current post in the loop, and including custom fields for each term...results in a large number of queries that have to be performed to show the results, and can slow down page loads. Again, caching can help with this.
Is there a way to store my meta data in custom database table?
No, Toolset doesn't provide options for utilizing non-standard database tables.
I stumbled across this plugin hidden link and was wondering if this plugin could integrate with toolset?
If you'd like to see an integration with a 3rd-party system, I recommend creating a new ticket in the forum using the "Suggest an improvement" option. This will put your request in front of our developers, who will decide if it's something we can implement.
My issue is resolved now. Thank you!
