integration_documentation:direct_integration

integration_documentation:direct_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
integration_documentation:direct_integration [2019/05/22 12:36]
fe80:6838:8204:7241:6aa9:419b:de43:27ef ↷ Links adapted because of a move operation
integration_documentation:direct_integration [2019/06/11 14:42] (current)
sarah [Overview]
Line 3: Line 3:
 ==== Overview ==== ==== Overview ====
  
-The FINDOLOGIC-scripts are binding events on the searchfield ​of the shop. When a user submits the form of the searchfield, the request gets sent via AJAX directly to the FINDOLOGIC servers. This offers a massive speed boost and lowers the load on the shop side, because it is not necessary that the request is being sent to the shop-server first. ​+The FINDOLOGIC-scripts are binding events on the search field of the shop. When a user submits the form of the search field, the request gets sent via AJAX directly to the FINDOLOGIC servers. This offers a massive speed boost and lowers the load on the shop side, because it is not necessary that the request is being sent to the shop'​s ​server first. ​
  
-FINDOLOGIC loads the entire search result as defined in the [[customer_account:​template_manager|template manager]] and delivers the rendered HTML to the shop. The HTML in this response will be placed in a container of the shop. This container must have **unique selectors**. As a customer of FINDOLOGIC you have to provide these containers ​in your shop.+FINDOLOGIC loads the entire search result as defined in the [[customer_account:​template_manager|template manager]] and delivers the rendered HTML to the shop. The HTML in this response will be placed in a container of the shop. This container must have **unique selectors**. As a customer of FINDOLOGIC you have to add the given classes to the existing main container ​in your shop.
  
 ------ ------
Line 11: Line 11:
 === Search result container === === Search result container ===
  
-This container has to be available **on every shop page** in order to ensure that the search works on every single page. The container must have the class ''​fl-result''​. For the search result pages, the HTML-response of FINDOLOGIC contains both all found product and the available filters.+To ensure proper functionality,​ the FINDOLOGIC Direct Integration must have access to the main container ​of the shop. To do so, it is necessary to add the class ''​fl-result''​ to the corresponding,​ pre-existing container. 
 +This class has to be available **on every shop page** in order to ensure that the search works on every single page. For the search result pages, the HTML-response of FINDOLOGIC contains both all found product and the available filters.
  
 {{ :​integration_documentation:​fl-result.png |}} {{ :​integration_documentation:​fl-result.png |}}
Line 20: Line 21:
  
 For using FINDOLOGIC on category pages you have to provide the ''​cat_url''​s in a valid manner. [[xml_export_documentation:​xml_format#​cat_url_examples|See our documentation about ''​cat_urls''​]] for more information. For using FINDOLOGIC on category pages you have to provide the ''​cat_url''​s in a valid manner. [[xml_export_documentation:​xml_format#​cat_url_examples|See our documentation about ''​cat_urls''​]] for more information.
-This container has to be available **on every category page** ​of the shop. The container must have the class ''​fl-navigation-result''​. For the category pages, the HTML-response of FINDOLOGIC contains both all found products and available filters for this category.+To ensure proper functionality,​ the FINDOLOGIC Direct Integration must have access ​to the main container ​of the shop. To do so, it is necessary to add the class ''​fl-navigation-result'' ​to the corresponding,​ pre-existing container. 
 +This class has to be available **on every category page** of the shop. For the category pages, the HTML-response of FINDOLOGIC contains both all found products and available filters for this category.
  
 {{ :​integration_documentation:​fl-navigation-result.png |}} {{ :​integration_documentation:​fl-navigation-result.png |}}