Skip Navigation

[Resolved] Structure for a Directory Site

This support ticket is created 7 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 3 replies, has 2 voices.

Last updated by Minesh 7 years, 1 month ago.

Assisted by: Minesh.

Author
Posts
#495624


Dear Amir,

Sorry to bother you but still I need your genius brain to structure a national wide directory site not becuase I’m uncomfortable with Luo support but as you know, failure in planning means planning to fail so I seek for your kind assistance and guidance to accomplish properly with your help the following:

1. Setup a directory which will cover (ONE) country with (12) region and (70) main city.
2. The directory will include (TWO) languages.
3. Events for national wide.
4. Search for any listing with branches if found in (12) region or (70) main city .
5. Search for the related listing national wide (region – city – certain area).
6. A to Z Glossary (Hierarchical Taxonomy)
7. Displayed A to Z Glossary horizontally with ascending order like:
(ALL-0-9-ABCDEFGHIJKLMNOPQRSTUVWXYZ) These letters glossary will act like ( index page or tab or bar ) for many trems entry (Custom Post Type) each trem will have a title for its heading and the body text for list description.
8. Setup the main listing index page to the reflect dynamic listing for many category.
9. Chronological steps to setup the tree like GFS (Grandfather – Father – Son) which reflect the main structure for
( country – region – city) .
10- The best way to define correctly the (Hierarchical Taxonomy) from the categories so the directory work smoothly for our scenario especially the CMS between the index listing and all relevant geographical locations.

Please try your best to explain in detail the structure for the above requirements and we wish if you have a detailed case study video to show ALL Toolset functionally and capability with FULL setup to accommodate this requirement in form of video tutorial or PDF which we can follow to help us build this directory.

Thank you,

#495925

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Well - I strongly suggest that you should check each requirement feasibility with our plugins and divide all your requirement in small module and then try to implement it and start development.

I suggest you should use our test platform discover-wp.com and try to create test site and play with it and check each possible requirement.
=> https://toolset.com/faq/how-and-why-to-create-a-test-site-in-discover-wp/

1. Setup a directory which will cover (ONE) country with (12) region and (70) main city.
=> As you want to filter or dispaly like tree structure as you explained in point #9

9. Chronological steps to setup the tree like GFS (Grandfather – Father – Son) which reflect the main structure for
( country – region – city) .

I would suggest you should check this requirement with our state/city functionality. You need to create country, region and city as post types if you want to use in that manner.
=> hidden link
[Please check state/city example with above site]

2. The directory will include (TWO) languages.
To build multilingual site you need to use WPML plugin.
=> https://wpml.org/purchase/

See this website thats multilingual using English and French:
=> hidden link

Please check following Doc:
=> https://toolset.com/2015/08/how-to-develop-a-multilingual-real-estate-site-with-wordpress-and-no-php/
=> https://toolset.com/documentation/translating-sites-built-with-toolset/

3. Events for national wide.
You should check for any third party plugin like Event manager etc..etc.. or create Events post type and check it on your own whats best possible fit for you as per your requirement

4. Search for any listing with branches if found in (12) region or (70) main city .
For search we offer custom search with views:
=> https://toolset.com/documentation/user-guides/front-page-filters/

We have full views training course available as well:
=> https://toolset.com/documentation/toolset-training-course/

5. Search for the related listing national wide (region – city – certain area)
Again, it will be the same as per my answer of point #1. See state/city example.

6. A to Z Glossary (Hierarchical Taxonomy)
For A to Z Glossary please try to follow following steps:
=> https://toolset.com/forums/topic/abc-filter-with-taxonomie/page/3/#post-467960

7. Displayed A to Z Glossary horizontally with ascending order like:
(ALL-0-9-ABCDEFGHIJKLMNOPQRSTUVWXYZ) These letters glossary will act like ( index page or tab or bar ) for many trems entry (Custom Post Type) each trem will have a title for its heading and the body text for list description.
===>
As I explined you in point #6.

8. Setup the main listing index page to the reflect dynamic listing for many category.
=> You can use views here or layout as per your need.

9. Chronological steps to setup the tree like GFS (Grandfather – Father – Son) which reflect the main structure for
( country – region – city) .
==> You can use views again see point #1 reply

10- The best way to define correctly the (Hierarchical Taxonomy) from the categories so the directory work smoothly for our scenario especially the CMS between the index listing and all relevant geographical locations.
==> Depends upon your structure I can better explain you when you have structure with you.

Again, the best way for you to use our test platform and create as many test sites as you want and check each requirement feasibility.

#496020

Thanks Minesh for your input as to elaborate a little bit more for (8,9,10) what really I meant is:

8. How to structure and setup correctly the categories for many dynamic listings to build an A to Z Glossary for so many categories…what is the the right way to structure the (Hierarchical Taxonomy) for example is the following structure correct for (region – city – certain area) listing if NOT how we do it correctly:
–a
—-a1 city
—-a2 city
—-a3 city
–b
—-b1 city
—-b2 city
—-b3 city

9.What is the steps to setup the tree structure for A to Z Glossary which reflect ( country – region -city) to support multi (Hierarchical Taxonomy) say from root to branchs.

10.How link and define placecs categories and listings properly (Hierarchical Taxonomy) so the directory work smoothly and the linking between the A to Z Glossary and all relevant geographical locations in sync and accurate.

The main help we need is to give us your BEST advice on how to structure the Toolset with ( one country -12 region – 70 main city) as we need the Toolset structure to accommodate the the following:
– Manage payment orders.
– Geo Location.
– Multi-location support.
– Claim Listings.
– MultiRatings and Reviews.
– The events national wide.
– Search for any listing with branches if found.
– Search for the related listing national wide or (region – city – certain area).

Thanks,

#496473

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

8. How to structure and setup correctly the categories for many dynamic listings to build an A to Z Glossary for so many categories…what is the the right way to structure the (Hierarchical Taxonomy) for example is the following structure correct for (region – city – certain area) listing if NOT how we do it correctly:
–a
—-a1 city
—-a2 city
—-a3 city
–b
—-b1 city
—-b2 city
—-b3 city
=========>
Well - to display such content in hierarchical structure, you can always us views inside view.
=> https://toolset.com/documentation/user-guides/using-a-child-view-in-a-taxonomy-view-layout/

9.What is the steps to setup the tree structure for A to Z Glossary which reflect ( country – region -city) to support multi (Hierarchical Taxonomy) say from root to branchs.
=========>
Again, I can not say anything or commit until we have a setup and there is always possibility that based on whatever structure you decide to follow needs some custom programming and that is out of the scope of our support policy.

10.How link and define placecs categories and listings properly (Hierarchical Taxonomy) so the directory work smoothly and the linking between the A to Z Glossary and all relevant geographical locations in sync and accurate.

The main help we need is to give us your BEST advice on how to structure the Toolset with ( one country -12 region – 70 main city) as we need the Toolset structure to accommodate the the following:
– Manage payment orders.
– Geo Location.
– Multi-location support.
– Claim Listings.
– MultiRatings and Reviews.
– The events national wide.
– Search for any listing with branches if found.
– Search for the related listing national wide or (region – city – certain area).
==========>
Most of above queries excluding search will need custom programming or you need to find third party plugin that best suits your requirement.

See this ticket that may help you to understand star rating:
=> https://toolset.com/forums/topic/searching-book-review-child-cpt-and-book-parent-cpt-by-star-ratings/

The best way again I suggest you use our test platform discover-wp.com and try to check feasibility with your each required functionality and if its not supported by Toolset plugins completely then you need to find alternatives that mean other third party plugins or if it supported partially then you may need custom programming and that is again out of the scope of our support policy.

We can not just imagine how you setup the structure but we will be able to offer you actual solution when you present us actual data structure and how your site is setup with all data such as CPT, taxonomies, post type relationship etc..etc..

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.