This document helps you to integrate the FACT-Finder® Web Components SDK into your Oxid Shop. In addition, it gives a concise overview of its primary functions. The first chapter Installation walks you through the suggested installation process. The second chapter Backend Configuration explains the customisation options in the Oxid backend. The final chapter Web Component Integration describes how the web components interact with the shop system and how to customise them.
Our Oxid plugin offers a basic working integration for default Oxid Apex theme. Most projects may require modifications in order to fit their needs. For more advanced features please check our official WebComponnents documentation.
- Requirements
- Installation
- Activating the Module
- Backend Configuration
- Export Methods
- Tracking
- Contribute
- License
- OXID eShop 7.0 or higher
- PHP version 8.1 or higher
Note: For Oxid eShop 6.x and PHP 7, please use SDK version 4.x
To install the module, open your terminal and run the command:
composer require omikron/oxid-factfinder
From the root of your Oxid installation, clear the cache with:
rm -rf source/tmp/*
Check in the Oxid backend "Extensions -> Modules" if the module output is activated.
Note: Sometimes you need also install module from command line. Please execute from project root:
vendor/bin/oe-console oe:module:install vendor/omikron/oxid-factfinder
Note: If after installation process you have problems with permissions, you have to set correct permissions for you project (chown and chmod command ). Check official docs
Once the module is activated, you can find the configurations page under "Extensions → Modules → FACT-Finder® Web Components | Omikron Data Quality GmbH -> Settings". All sections will be covered in the following paragraphs.
This section contains a critical configuration, which is required in order for the module to work. All fields are self-explained. Configuration set here is used by both Web Components and during the server side communication with FACT-Finder® instance. Credentials you will be given should be placed here.
- Server URL - FACT-Finder® instance url
Note: Server URL should contain a used protocol: (e.g.https://) and should end withfact-finder(e.g.https://my-domain.fact-finder.de/fact-finder) - Channel - Channel you want to serve data from
Note The number of channel fields is adjusted to the number of active languages used in application. Please make sure you set a correct channel for a given language. - Username for the FACT-Finder Import - your username in FACT-Finder account (necessary if you want to automatically execute import data in FACT-Finder).
- Password for the FACT-Finder Import - your password in FACT-Finder account
- FACT-Finder API key - for fetching data from FF (necessary to use Web Components integration)
This functionality allows you to update field roles if you have changed them in FACT-Finder.
The field roles are by default configured accordingly to the columns exported by the module.
If you are about change one of the column name that serves as a role e.g. Master or ProductNumber, that holds the Master article number and Product number roles respectively, please remember to update the field roles with that functionality
It is a one of possible ways of exporting feed. You can find more details in section Admin Panel Export
By clicking the Test Connection button you can check if your FACT-Finder API key is correct and SDK could connect with FACT-Finder API successfully.
This functionality uses form data, so there is no need to save first.
Note: This functionality uses de channel input value.
This functionality allows you to test if your shop can successfully connect to configured FTP/SFTP server. It uses parameters passed down with the request so there is no need to save the configuration before.
By clicking the Test Push Import button you can check if your FACT-Finder username and password is correct.
This functionality uses form data, so there is no need to save first.
Note: This functionality uses de channel input value.
Anonymize User ID?- check this option if you want to send user id with tracking requests in anonymized form. By default the regular id field from user table is sent.How to count single click on "Add to cart" button?- select how would you like to count single click on "Add to cart" buttonSend the SID as userId when user not logged in?
Use FACT-Finder® for category pages?- check this option to use Web Components in category pages. More information in separate paragraph.Category Path field name- by default, the module uses a field namedCategoryPath(default category field name for FactFinder instance). If in your FactFinder instance configuration you have a different field name for Category field then you must set this name here.- Campaigns - enables
ff-campaign-producton product page andff-campaign-feedbacktext,ff-campaign-shopping-carton cart page - Recommendations - enables
ff-recommendationon product page - Similar products - enables
ff-similar-productson product page - Pushed products - enables
ff-campaign-pushed-products>on cart page
Module in order to preserve categories URLs and hence SEO get use of standard Oxid routing with the combination of FACT-Finder® availability to pass custom parameters to search request. Once user lands on category page search event is emitted immediately.
This section allows setting attributes to export.
If you want to export the attribute to separate column, choose it from the select input and set Multi-Attribute column value to No.
if Multi-Attribute is set to Yes, the attribute is placed in an aggregate column FilterAttributes
Note: Selection attributes are always placed in FilterAttributes automatically.
Use following fields if you want to export feed file to your FTP server, where it could be then imported by FACT-Finder®.
- FTP host
- FTP port
- FTP user
- FTP password
Additional:
- SSL-enabled - check this option, if your FTP server requires connection using secure protocol
- Automatic import of product - enables import executed by FACT-Finder® after uploading
Note: This option will not work if you have no FTP server configured - Import Data - triggers Data (search database)
- Import Suggest - triggers Suggest database
- Import Recommendation - triggers Recommendation database
- Basic Auth user for HTTP export
- Basic Auth password for HTTP export
Note: Basic Auth is used to secure HTTP based export, you can read more about in the next section. - Log path - path to log file where export log will be saved
- Proceed with export when error occurred
This method uses a specific URL under which the feed will be available. You can set FACT-Finder® to download the feed directly from this location:
[YOUR_SHOP_URL]?cl=http_article_feed&fnc=export
For category export:
[YOUR_SHOP_URL]?cl=http_category_feed&fnc=export
For suggest category export:
[YOUR_SHOP_URL]?cl=http_suggest_category_feed&fnc=export
Note: Please keep in mind that the feed file is not directly available under the location. There is an export mechanism that does it on demand, so the whole process may take some time.
Using Export Settings you can secure the HTTP export by setting up a Basic Authentication. Please remember that in this case you will need to include credentials in the URL, otherwise FACT-Finder® will not be able to download the feed file. You can include Basic Authentication credentials in URL using following syntax:
https://[username]:[password]@[REST_OF_URL]
With this approach, the exported feed file is uploaded to a specific FTP/SFTP server. Once the feed file is uploaded, FACT-Finder® is requested to begin an import based on uploaded file (optional). All settings related to this exporting method are found in Export Settings. Fields Key and Key Passphrase are dedicated only to the SFTP. Field SSL Enabled is dedicated only to FTP.
Note: Used FTP/SFTP server should be also accessible to FACT-Finder®.
Export Feed button located in module configuration, could be used to manually trigger an export.
By clicking this button, you trigger the whole export process, including upload to FTP server and triggering a FACT-Finder® import (if enabled).
Note: This method does not download the feed file to your local file system. If you need to view it, please use the HTTP Export
Note: Category export is not available here as clicking button start import on channel but category feed is supposed to be an enrichment for main article feed
There are two console commands located in the module bin directory, available for use.
Simply run them using the installed PHP CLI.
php [MODULE_LOCATION]/bin/[COMMAND_NAME].php
feed-write.php- only saves the feed file on local file systemfeed-upload.php- run full integration (just like clicking theExport Feedbutton in admin panel)
If you are using Oxid Enterprise and its multishop feature, you can specify the shop ID by using the -s parameter, e.g.
php source/modules/ff/ffwebcomponents/bin/feed-write.php -s1
If your shop supports multiple languages, enter the language identifier of the language you want to export by adding -l parameter to the command (e.g. php bin/feed-write.php -l 1).
You can check the language identifiers at "Master Settings -> Languages".
You can specify the type of the feed with the -t option. Default value is product. In order to switch for category, please use -t category
Here you can find a full Tracking Guide. This module follows that guide in order to provide tracking of following events:
This event is tracked automatically by SDK.
This event is tracked automatically by the ff-record element bindings. Note: for this to work a directive data-redirect has to be added
We offer a registerAddToCartListener function which helps to register click events on form submit buttons. Note: Example usage can be found in views/twig/extensions/themes/default/page/details/inc/productmain.html.twig
This event is tracked by the ff-checkout-tracking element which is implemented on order confirmation page
For more information, click here
You can also open a new issue if You spot a bug or just have an idea for module improvement To check currently opened issues here.
FACT-Finder® Web Components License. For more information see the LICENSE file.