Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:syces:selfserviceportal:custom_templates [2014/06/03 11:47] co |
en:syces:selfserviceportal:custom_templates [2016/09/27 13:00] (current) co |
||
---|---|---|---|
Line 5: | Line 5: | ||
- | There are 2 types of custom templates: | + | There are 4 types of custom templates: |
- | * those that use the normal Template (hotspot.tpl) and its functionalities, | + | |
- | * those that may provide even more flexibility and also supply the complete functionality for the sending of the required forms | + | |
- | Whereas the first type can be used for all kinds of walled garden registration methods, the second | + | * **index.html**: |
+ | * **hotspot.tpl**: | ||
+ | * **custom_anonym.tpl**: | ||
+ | |||
+ | Whereas the hotspot.tpl | ||
* custom_oneclick.tpl | * custom_oneclick.tpl | ||
* custom_paypal.tpl | * custom_paypal.tpl | ||
Line 16: | Line 18: | ||
At the moment we only support custom_anonym.tpl. | At the moment we only support custom_anonym.tpl. | ||
+ | |||
+ | * **custom_token.tpl**: | ||
+ | |||
===== Process for the installing of custom templates ===== | ===== Process for the installing of custom templates ===== | ||
Line 41: | Line 46: | ||
{LOGINTITLE}: | {LOGINTITLE}: | ||
{REGISTERTITLE} title for registration form\\ | {REGISTERTITLE} title for registration form\\ | ||
+ | {AGB}: link to agb.html, a file containing your Terms and Conditions; you may have agb.html files for different locations and different languages. Please check what the [[en: | ||
Any files you use (images, CSS etc.) should have a {TPLDIR} as a prefix to get the right path to your template folder, e.g. <img src=" | Any files you use (images, CSS etc.) should have a {TPLDIR} as a prefix to get the right path to your template folder, e.g. <img src=" | ||
- | If you want to offer templates in several languages you must create one subfolder for each language and place the templates in the subfolders: {TPLDIR}< | + | If you want to offer templates in several languages you must create one subfolder for each language and place the templates in the subfolders: {TPLDIR}< |
- | Send a zip file containing all required | + | For uploading your files please use the [[en: |
- | + | ||
- | Synergysystems then does some basic security and functionality checks, renames the template if necessary (either hotspot.tpl or custom_anonym.tpl) and uploads them in the appropriate custom directory. | + | |
To finally activate the custom template you have to choose " | To finally activate the custom template you have to choose " | ||
Line 112: | Line 116: | ||
===== custom_anonym.tpl (minimum requirements) | ===== custom_anonym.tpl (minimum requirements) | ||
- | This template can be used for the most flexible custom layout. You need to provide a form with a field named " | + | This template can be used for the most flexible custom layout. You need to provide a form with a field named " |
< | < | ||
< | < | ||
Line 133: | Line 136: | ||
</ | </ | ||
<!-- END BODY --> | <!-- END BODY --> | ||
+ | </ | ||
+ | </ | ||
+ | Please be aware that any template variables need to be placed within either the head or the body section. The example above needs at least one more template variable e.g. {DATE} within the body section in order to get the body section displayed. | ||
+ | Else use the following code if you only have the {LOGIN} variable: | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <!-- BEGIN HEAD --> | ||
+ | < | ||
+ | {SCRIPTS} | ||
+ | </ | ||
+ | <!-- END HEAD --> | ||
+ | |||
+ | <body onload=" | ||
+ | |||
+ | < | ||
+ | {LOGIN} | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | </ | ||
+ | |||
</ | </ | ||
</ | </ | ||
Line 196: | Line 226: | ||
- | ===== How to install user provided custom templates (done by Synergysystems) ===== | + | ===== How to install user provided custom templates (done by Synergy Systems GmbH) ===== |
- | Please log in for more information. | + | You need to be logged |
< | < | ||
We should always test on our development system before installing on the live system. When everything is okay we can copy the whole testfolder contents to the custom folder on the live system. This is either | We should always test on our development system before installing on the live system. When everything is okay we can copy the whole testfolder contents to the custom folder on the live system. This is either |