Note:
The Marketplace is only available to existing customers and can no longer be reactivated.
General
The vehicle exchange is developed with the aim of allowing it to be readily integrated into a customer's website without functional or visually impaired it itself or the surrounding page. Due to the diverse possibilities for programming websites and the associated implications, this goal can only be achieved approximately. To enable optimal integration of the vehicle exchange into the customer's website, he must meet the following requirements.
Detailed information for embedding can be found on
This page.
To embed there is a
WordPress Pluginand a download option for a quick search script.
Embedding
To integrate the vehicle exchange into the customer's website, a script reference is integrated into the customer's website. All other resources and dependencies are automatically reloaded by this script.
The position of the vehicle exchange in the customer's website can be determined by the customer with an Html element VI preferably with a div element I with the id am-marketplace. No element of the page must be provided with this id for another purpose.
If the customer does not use such HTML element, the vehicle exchange itself generates one. In this case, the HTML element is placed in the customer's website where the script reference is located. If the script reference is in the head section, the element is inserted at the end of the body section due to lack of other possibilities as a new element
Isolation
The vehicle exchange reloads all Javascript libraries you require completely self-sufficient. This includes the jQuery library and plugins used, as well as the angular framework and associated packages. The goal is for these libraries to load these libraries so that, if necessary, instances present in the customer's surrounding website remain unaffected.
Styling
Styling instructions used in the vehicle exchange are consistently prefixed with the name #am-marketplace as prefix. This prevents the styling of the vehicle exchange styling to the customer's surrounding website.
Styling instructions of the customer's surrounding website can be applied in particular to elements of the vehicle exchange if the !important option is used in the styling instructions of the customer's surrounding website.
Demarcation
Due to the variety of possible combinations of Javascript and Css frameworks, specific constellation can lead to unexpected errors, in particular that the vehicle exchange does not load completely, does not start correctly or individual functions are not responsive. The customer's surrounding website may also be affected. Fully functional integration of the vehicle exchange into the customer's website is only for the Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge browsers in the current version of the respective manufacturer.
The following technologies in the customer's surrounding website do not affect the functionality:
Technology - Type
Bootstrap 3 - CSS
Bootstrap 4 - CSS
jQuery 1 - Java Script
jQuery 2 - Java Script
jQuery 3 - Java Script
Angular 1.3 - Java Script
Angular 1.4 - Java Script
Angular 1.5 - Java Script
Angular 1.6 - Java Script
Angular 1.7 - Java Script
UIKit - Java Script / CSS
Html 5 - html
Framework condition for operating the Marketplace Exchange.
The website on which the pixelconcept Marketplace is to be integrated must ensure that the browser sends a header value named Referer when requesting it. If this header is missing during loading, the Marketplace script rejects integration.
Usually there is no need for action here, as a browser usually sends this value along.
However, there are ways to modify the behavior. Some content management systems offer special setting options within the basic scope of the system, or via plugins. However, it can also be influenced via a global server settings, or directly in the HTML document of the respective page via special instructions.
Some WordPress plugins that allow it are listed below. Details on how to proceed can be found in the respective plugin documentation:
For Typo3 there are these instructions, among others:
Detailed information on the topic can be found here:
Policy values that should be used are:
origin
strict-origin
strict-origin-when-cross-origin
unsafe-url
Do not use:
no-referrer
no-referrer-when-downgrade
same-origin
Mandatory:
Integration of the app into its own website of the customer is only owed in compliance with the requirements in "Technical conditions and framework conditions for the integration of the AUTOMANAGER Marketplace (vehicle exchange).