Technical documenation
This documentation is the interesting part for administrators and developers and should explain how lux can be installed, configured and how does it work. In addition we want to give you some hints how to extend lux with your own workflow triggers or workflow actions.
Introduction
Lux is build to use asynchronical techniques and without the need of any USER_INT function to also use lux together with staticfilecache extension for high performance on your TYPO3 websites.
There is no need to use a JS framework like jQuery - Lux just uses vanilla JS - also for the lightbox implementation.
But TYPO3 should run in composer mode to allow the loading of additional packages (see Installation for more details).
Tracking and doing workflow stuff in frontend needs JavaScript to be enabled in the visitors browser. Some functions are disabled if the visitor is also logged in into backend at the same time (to avoid misleading data). It's possible for visitors to opt out (with the opt-out plugin) or to use the do not track settings in their browser. Lux will respect this settings in every case.
Every visitor gets an individual identificator, which is used to recognize the visitor in future visits. Per default this is a random string, saved to the localstorage of the browser. Alternatively LUX can work cookieless with an anonymous hash (fingerprint), based on the visitors hard- and software - see Fingerprints vs. local storage.
There are some settings - saved to localstorage in browser which are:
luxIdthe identificator of the visitor (only in localstorage mode - the default)luxDisableEmail4Linkto disable email4link popups if a visitor is already identifiedluxTrackingfor a tracking opt out or opt in
See more information in the chapters: