Nested taxonomy
-
Hi,
Can Pod help me to create online shop with many different products?
1) At our world each product type have it’s own parameters (taxonomy: Attributes and Attributes Terms), but at WooCommerce there only one list of a Products Attributes without any separation for a different products types. Can Pods help to split WooC Products Attributes to a groups? Or add possibility to assign some Products Attributes to a some Products Categories? etc?
(Suppose if I will start to create new Post type for each Product type – it will break WooC Shop variables+stock+discounts+purchase+delivery functionality, because WooC works with Post type “Product”.)
2) Some Products have variable parameters which have sub-parameters, for example one car can have up to 5 engines and each engine type petrol/diesel/gas/electric have different parameters. So for some WooC Products Attributes I need a nested Sub-Attributes with their own Sub-Attributes Terms.
3) Also I need to add to a WooC Products Attributes and their Terms some additional custom fields-parameters.So, can Pods help with #1 or #2 or #3?
-
Hello @johnynla
Please see this page: https://docs.pods.io/faqs/what-can-you-build-with-pods/
As for actual answers.
1) I believe Woo has already built-in differentiation for product attributes depending on what attributes have values for a product.
2) This would simply be a separate taxonomy/attribute “Engine type”. No need to create a “sub” category for that.
3) This can be done with Pods. Once you’ve created the attributes you can extend them with Pods.Cheers, Jory
Hello, thanks for an answers, but please, add some clarifications.
1) Please, explain/sample? Still is it possible what I asking at #1 previously with Pods or not? If yes how it will be reflected at WooC Product creating/editing form? At right side there are Products Categories, at center at Attributes tab there are a dynamic list of Products Attributes. Is it possible to show at Attributes list only that Attributes which previously was assign to a chosen Category at right? Will Pods also add at WooC Product Attributes list a filter by a Product Categories, etc? Is it possible somehow with your Pods? How assign functionality will look like, do you have a sample video or screenshot?
2) Seems that you don’t understand. I need this possibility to add to a ONE product (one car) – MANY totally different variable attributes blocks (as engines) and each of which must have it’s own totally different variable attributes (engines parameters – a nested attributes (for example petrol engine must have attributes as cylinders and fuel, when electric engine must have a different attributes as battery and placement) maybe even with a variable product possibility). All must act via standard WooC forms and displaying at frontend at single product detailed specifications table. WooC by default does not have such functionality. Is it possible somehow with Pods?
3) Samples? does it needs any coding?
I don’t need to show aт Attributes Terms custom fields at WooC Product creating/editing form, need to show them only at frontend. For example I want to add to a WooC Products Attributes Terms an icons by Pods. Does Pods support a custom icon field for a terms? Does those icons will appear at frontend WooC Single Product “detailed specifications attributes&terms table”? Or which widgets can help to show “all WooC Attributes&Terms table with custom icons?4) Is it possible with Pods to calculate sum of likes of 3 different plugins – comments, ULike, BuddyPress from different db tables an metakeys?
5) Is it possible with Pods to display all of them at Elementor?
6) If some of those functions are possible with Pods – does it needs any parts of a custom coding?
Pretty much everything you posted will require us to build your solution to answer your questions. We’re not going to do that.
Please put in the work and come to us with specific questions based on what you find. Something like this isn’t going to be easy because you’re digging deep into WooCommerce and expecting Elementor to work with it is pure fantasy. You’re going to have to code anything this complex.
We do not (as our FAQ mentioned), recommend extending very complex ecosystems like WooCommerce and their variable products and custom taxonomies unless you know what you’re doing and since we’ve not built anything like that, we don’t have samples or tutorials to show you. You really, honestly, should start with the WooCommerce developers codex because they have very specific methods for getting and setting attributes and extending them.
- The topic ‘Nested taxonomy’ is closed to new replies.
