Sets the extensions that contain login handlers
ExtensionDirectory[]= extension_name1 ExtensionDirectory[]= extension_name2 ...
It is possible to provide custom login handlers using the extension system. This setting specifies the extensions that contain a login handler. Exponential will look for the handlers in the path:
extension/ extension_name/login_handler/
This documentation stores what it needs to work: a session cookie when you sign in or keep a setting such as the help menu shown or hidden, the design you chose (Classic or Modern) and your language. Only if you agree, it also uses Google Analytics (through Google Tag Manager) to count visits; until then nothing is loaded from Google. Your choice is kept in a cookie for 6 months, and you can change it at any time under "Cookie settings" at the foot of every page. Details are in our Cookie Policy.
The session cookie for signing in and for forms, the cookies that keep your design and language, and the cookie that keeps this choice. They stay on because the website needs them; you can delete them in your browser settings at any time.
Google Analytics, loaded through Google Tag Manager (GTM-MPGWKTQV), counts visits and shows us which pages are read: the pages you open, the page you came from, your browser, device and screen size, and your approximate location derived from your IP address. Google processes the data for us and may transfer it to the USA. It sets the cookies _ga and _ga_* for up to 2 years. Off until you turn it on; when you turn it off again, Google is no longer loaded and these cookies are deleted.
Comments (1 historical)
Written by readers of the earlier documentation sites, kept as they were.
Login handler usage
WassimBHS ·
Anyone could give me a detailed example about the usage of a login handler (configuration with files ) ?