Title: Pods using – WP Posts vs CustomContentType Last modified: April 17, 2021 --- # Pods using – WP Posts vs CustomContentType * Resolved [johnynla](https://wordpress.org/support/users/johnynla/) * (@johnynla) * [5 years ago](https://wordpress.org/support/topic/pods-using-wp-posts-vs-customcontenttype/) * Hello, * I need to store at DB about 100 custom data fields (different specifications) about 100’000 Cars (thus it’s a real big-data). All custom fields must be stored at standalone DB table. Also I need to arrange Cars by categories for example: sedan, hatchback, station wagon, coupe, SUV, tractor, etc. Also I want to give to users ability to comment each Car. * I want to use your very powerful Pods, but I still don’t really understand which advantages/disadvantages will bring each of 3 methods of Pods using: 1) Add custom fields to standard WP Posts, arrange Cars types by WP Posts Categories. 2) Create custom post type with new custom fields, arrange by Pods custom “Cars categories” Taxonomy. 3) Create AdvancedContentType with new custom fields and later link it to correspond WP Posts or WooC Products by shortcodes etc which arrange by WP Posts Categories or WC Products Categories. * Which differences they have? Which and why method do you recommend? - This topic was modified 5 years ago by [johnynla](https://wordpress.org/support/users/johnynla/). - This topic was modified 5 years ago by [johnynla](https://wordpress.org/support/users/johnynla/). Viewing 3 replies - 1 through 3 (of 3 total) * Thread Starter [johnynla](https://wordpress.org/support/users/johnynla/) * (@johnynla) * [5 years ago](https://wordpress.org/support/topic/pods-using-wp-posts-vs-customcontenttype/#post-14330698) * Small update: each “Cars category” as: coupe, sedan, hatchback, station wagon, SUV, tracks, etc. – must have different/individual Pods custom fields set. For example: “station wagon and SUV” must have additional fields about baggage compartment; tracks must have additional fields about carrying capacity; etc. * 1) But it seems that Pods does NOT allow to set different Pods (different custom fields sets) to 1 post type (WP Posts) by Taxonomy (per WP Post Category)? It’s obvious shortcoming but as is. 2) Does Pods allow such individual Pods (custom fields sets) for 1 NewPostType variate via Pods Taxonomy? Seems also NO? * Then here is only 2 actual ways for my project: A) Create many new custom post types with new custom fields – 1 Pods (custom fields set) per 1 post type. But at frontend navigation it will NOT work comfortable as “one WooC Shop catalog”– because for top category changing it will require to change the site page/section. B) Create many new AdvancedContentTypes with new custom fields and later link each manually to correspond WP Posts or WooC Products by shortcodes etc which arrange by WP Posts Categories or WC Products Categories. * Which differences they have? Which and why method do you recommend? * PS Even ACF have option to “add different custom fields sets based on current WP Post Category”. :\ * Plugin Author [Jory Hogeveen](https://wordpress.org/support/users/keraweb/) * (@keraweb) * [5 years ago](https://wordpress.org/support/topic/pods-using-wp-posts-vs-customcontenttype/#post-14337416) * Hi [@johnynla](https://wordpress.org/support/users/johnynla/) * From what I read this is more a consulting question than a practical question. For that reason I’m inclined to forward you to the following page: [https://docs.pods.io/faqs/what-can-you-build-with-pods/](https://docs.pods.io/faqs/what-can-you-build-with-pods/) * I’ll try to give you a short answer from where you can continue your decision making for your project. * First of all, I would never recommend extending WP core’s posts for a feature like this. These are meant for blog posts etc. * Then the question CPT or ACT. Personally I favor CPT. The advantage of CPT ( custom post types) is that it nicely integrates with WordPress core and other plugins. While doing this you can still add your custom fields as table based and this have the advantages of table based storage! * Replying on your second comment. What you are mentioning is something we are building as we speak for Pods 2.8 which is currently in beta. [https://pods.io/2021/02/11/pods-2-8-beta-1-released-and-the-field-guide-to-pods-2-8/](https://pods.io/2021/02/11/pods-2-8-beta-1-released-and-the-field-guide-to-pods-2-8/) * Cheers, Jory * Thread Starter [johnynla](https://wordpress.org/support/users/johnynla/) * (@johnynla) * [5 years ago](https://wordpress.org/support/topic/pods-using-wp-posts-vs-customcontenttype/#post-14338308) * Hi, * Thanks for answer! * Pods 2.8 update looks very nice! * Please, read my last message at: [https://wordpress.org/support/topic/advanced-content-type-with-custom-fields/#post-14331624](https://wordpress.org/support/topic/advanced-content-type-with-custom-fields/#post-14331624) It can make your 2.8 update EVEN MUCH MORE nice! - This reply was modified 5 years ago by [johnynla](https://wordpress.org/support/users/johnynla/). Viewing 3 replies - 1 through 3 (of 3 total) The topic ‘Pods using – WP Posts vs CustomContentType’ is closed to new replies. * ![](https://ps.w.org/pods/assets/icon.svg?rev=3286397) * [Pods - Custom Content Types and Fields](https://wordpress.org/plugins/pods/) * [Frequently Asked Questions](https://wordpress.org/plugins/pods/#faq) * [Support Threads](https://wordpress.org/support/plugin/pods/) * [Active Topics](https://wordpress.org/support/plugin/pods/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/pods/unresolved/) * [Reviews](https://wordpress.org/support/plugin/pods/reviews/) ## Tags * [custom fields](https://wordpress.org/support/topic-tag/custom-fields/) * [method](https://wordpress.org/support/topic-tag/method/) * 3 replies * 2 participants * Last reply from: [johnynla](https://wordpress.org/support/users/johnynla/) * Last activity: [5 years ago](https://wordpress.org/support/topic/pods-using-wp-posts-vs-customcontenttype/#post-14338308) * Status: resolved