This support ticket is created Il y a 5 années et 9 mois. 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.
Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.
First of all the Url is: lien caché
* Its a multi site system
We have built a search engine for our customer catalog, here is the details:
Post types:
- Catalog (Parent cpt)
Fields:
Motorad number
D1 [mm]
D2 [mm]
H [mm] T°[C]
Seal/gasket
Jiggle Pin
Type
Text – post content
Photo
Taxonomy:
Category of item
- Vehicle (Child CPT of catalog)
Fields:
cc (L)
Year start
Year end
Model – text field
Taxonomy:
- Brand
- Years
- OEM (Child CPT of catalog)
Fields:
OEM Number field
Manufacture
For now the search engine showing the right result but we have 2 speed issues:
1. Because of the relationships once you are trying to search its take too many time to get the result,
We are calling to the Childs CPT (OEM & Vehicle) and showing The Parent CPT (Catalog)
* The search engine appearing at the header all over the site
2. At The catalog Page (for example: lien caché)
We are showing the catalog CPT field and we have TABS Section the showing the childs details (OEM & Vehicle) -
All the single Catalog page are loading too slow
We wiil be more then happy to get some solution for this 2 speed issue's, We considered to develop it again by full custom code because we tried many method to solve it and we didnt found any solution. You are our last chance to solve it without changing from toolset to a custom code.
So essentially it is quite heavy, the link you sent is also loading up 13 different views.
I'm not seeing in the debug information where caching plugin is installed. I would highly recommend caching since the problem here seems the caused by multiple requests from the database.