integration_documentation:navigation
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
integration_documentation:navigation [2019/11/13 12:59] amil |
integration_documentation:navigation [2020/01/23 16:21] florian removed |
||
---|---|---|---|
Line 5: | Line 5: | ||
---- | ---- | ||
- | ==== Integration ==== | ||
- | <note>This section deals with how to integrate FINDOLOGIC Navigation in shop software that is not yet supported from a technical perspective. To integrate FINDOLOGIC in a system that is already supported, please refer to the documentation on embedding FINDOLOGIC in your shop system.</note> | ||
- | The call to Navigation is made as usual via the FINDOLOGIC interface in the two variants of HTML and XML: | ||
- | |||
- | * HTML: | ||
- | |||
- | <code> | ||
- | http://<ServiceURL>/selector.php?shopkey=<SHOPKEY> | ||
- | </code> | ||
- | |||
- | * XML: | ||
- | |||
- | <code> | ||
- | http://<ServiceURL>/ps/xml_2.0/selector.php?shopkey=<SHOPKEY> | ||
- | </code> | ||
- | |||
- | For the available request parameters, please refer to the [[https://docs.findologic.com/doku.php?id=integration_documentation:request|documentation of search parameters]]. In addition, filters can be preselected so they cannot be deselected by the customer. In this way, Navigation can start directly in a desired category (via the category navigation in the shop) or for a vendor. For this purpose, replace attrib with selected, otherwise this parameter will function exactly like attrib. | ||
- | |||
- | |||
- | ====Procedure==== | ||
- | |||
- | **Query of filters** | ||
- | In the first step, the available filters are queried and the preselected category is submitted via the selected parameter. | ||
- | |||
- | <note important>At this point, the results are generated not by FINDOLOGIC but by the shop, since FINDOLOGIC does not yet offer any benefit; therefore, query with count=0 | ||
- | </note> | ||
- | |||
- | Example of a call in the "Fashion" category: | ||
- | <code>http://<Service-URL>/selector.php?shopkey=ABCD&selected[cat][]=Mode&count=0 | ||
- | </code> | ||
- | |||
- | The structure of requests to FINDOLOGIC is documented in detail here. Please ensure that you also provide the FINDOLOGIC required parameters with each call. | ||
- | |||
- | <note important>Especially ensure that the IP of the requesting end customer is also supplied so that queries can be recognised by bots. | ||
- | </note> | ||
- | |||
- | **Output of filters** | ||
- | |||
- | The filters are output in the shop at the corresponding location. The output is executed in the module in the shop. | ||
- | |||
- | The customer can now select a FINDOLOGIC filter with which the FINDOLOGIC results can be obtained in the next step. | ||
- | |||
- | **Query of results** | ||
- | |||
- | The customer has selected a filter. This is now transmitted to FINDOLOGIC | ||
- | |||
- | Example of preselected category "Fashion" and attribute "Color=blue": | ||
- | <code>http://<Service-URL>/selector.php?shopkey=ABCD&selected[cat][]=Mode&attrib[Color][]=blue | ||
- | </code> | ||
- | |||
- | ====Excluding search engines==== | ||
- | |||
- | This cannot be executed via robots.txt since otherwise the first call of the crawler would still call the FINDOLOGIC service. It must therefore be determined whether a call is being made by a crawler and in this case whether the delivery of the filters was prevented. | ||
- | ---- | ||
==== Use the navigation in your shop ==== | ==== Use the navigation in your shop ==== | ||