Hi
Just chasing some quick tips on initial architecture for a dealership site. I'm starting with the new car setup, but there will be specials and used cars for this Kia dealership.
Car brand eg Kia
...has models
... models have range (eg S pack)
... Ranges have specific options (which maybe a potential option for any models for that brand)
Should I generally be using relationships? What confuses me is when editing custom fields there are the repeating field groups and also post reference (which sounds the same as a relationships to me?)
I read on one of your posts the field groups are being replaced by relationships. https://toolset.com/2016/08/how-post-relationship-replaces-post-reference-and-repeating-fields/ Is this the case? why are the fields in the uI then?
Thanks guys. This is great fun!
Hello and thank you for contacting the Toolset support.
I'll, first, try to answer your questions then I'll comment on the website use case.
Should I generally be using relationships? What confuses me is when editing custom fields there are the repeating field groups and also post reference (which sounds the same as a relationships to me?)
You are right, post references and repeatable group fields are "hidden" one-to-many relationships.
Well, should you generally be using relationships? will depend on the feature that you want to offer on the website. Toolset is a powerful tool but has also some limitations. For example, Toolset Views can't, currently, filter posts by multiple relationships. Only one relationship is allowed to be used in the search. And in the case of multiple one-to-many relationships, we can filter by ancestors. For example, Countries have multiple regions, and regions have multiple cities. We can filter cities by country and region.
Is this the case? why are the fields in the uI then?
I am not sure to understand this question. But I'd like to note that Post references and Repeatable Field Groups are still supported.
Regarding the website case, I'll suggest considering custom taxonomies. Toolset Views and archive templates allow filtering using multiple taxonomies. Taxonomies can be hierarchical, so you may have models and ranges in the same taxonomy. Options can be a different taxonomy or a taxonomy for each option that you will be using. It may also be used as a custom field.
So, basically, depending on your use case, a different approach may be taken. I'll suggest that you list the filters that you would be using in your search pages or on the archives before deciding what to do.
Consider checking our reference sites and our tutorials about creating complete websites, I am sure they will help in a way or in another.
- Reference sites: https://discover-wp.com/site-templates/
- Tutorials: https://toolset.com/documentation/
I hope this helps. Let me know if you have any questions.
Sorry for the delay. Thanks for the response,
