Contao Community Documentation - User contributions [en]

Bot Statistic

2023-12-21T10:58:33Z

BugBuster:

Bot Statistics counts the requests (visits, pages) of the bots. 
To identify the bots, the module is used [[Bot Detection|Bot Detection]] (necessary dependence).

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion=1.1.0
| Version=ab 5.2
| TLVersion=no
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=https://packagist.org/packages/bugbuster/contao-botstatistics-bundle
| DonateLink=http://www.amazon.de/wishlist/26HHEJOU03G76
| TrackerLink=https://github.com/BugBuster1701/contao-botstatistics-bundle/issues
| Comment=
}}

[[de:Bot_Statistik]]
[[Category:Extensions]]

After installation, create a front end module of type "Bot Statistics" and install this in the layout, best in the footer. The module only returns a HTML comment, and therefore does not affect the layout.

In the backend, there is in "System" the new item "Bot Statistics".

Stardate

2019-05-11T22:11:42Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Module_stardate_all.jpg|right|Stardate]]The module generates over insert-tags, the Star Trek® Stardate.
With insert tags you can choose, according to which method of calculation and whether the return should take place as text or an image. 
The image at right shows all types of calculation than image, at 2010-02-17 03:30 PM.

{{Hint|This page is no longer updated by the developer.
The current manual for the extension Stardate (Contao 4) can be found here: [http://docs.contao.ninja/en/stardate.html docs.contao.ninja]}}

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=0.1.0
| Version=from 2.9
| TLVersion=2.8.0 - 2.8.4
| Depending=[[GraphicalText|GraphicalText]] (optional)
| ERLink=http://www.contao.org/extension-list/view/stardate.html
| DonateLink=Cappuccino
| TrackerLink=http://dev.typolight-forge.org/projects/stardate/issues
| Comment=German demo on [http://www.ncc1969.de/Sternzeit.html www.ncc1969.de]
}}
[[de:Stardate]]
[[Category:Extensions]]

=Forum=
Questions about the Stardate module will be answered in forum: [http://www.typolight-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [http://dev.typolight-forge.org/projects/stardate/issues Issue Tracker].

 

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/stardate.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/stardate". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

=Use in the frontend=
The module used insert-tags. It can be selected the type (text / image), whether the generated values into the page cache (if activated) or newly generated each time. Both are controlled by corresponding parameters.

=Insert-Tag Overview=
The names have been formed on the source or the series.

 
==Stardate Today==
[[File:Module_stardate_today.jpg|left|Stardate]]Source: trekguide.com Output as a positive number for today.
Output in the form: YYMM.DD, YY is YYYY-1900 
Text: 
<source lang="text">
{{stardate::TODAY}}
{{cache_stardate::TODAY}}
</source>
Image: 
<source lang="text">
{{stardate::TODAYGT}}
{{stardate::TODAYGT::gttagname}}
{{cache_stardate::TODAYGT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 
==Fictional Stardate Today==
[[File:Module_stardate_fs.jpg|left|Stardate]]Source: trekguide.com Output as a positive number for today. Stardate 00000.0 begins on 7/14/1946 6:00 PM 
Text: 
<source lang="text">
{{stardate::FS}}
{{cache_stardate::FS}}
</source>
Image: 
<source lang="text">
{{stardate::FSGT}}
{{stardate::FSGT::gttagname}}
{{cache_stardate::FSGT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 
==Fictional Stardate TK==
[[File:Module_stardate_tk.jpg|left|Stardate]]Source: TrekConnection.com Output as a positive number for today. 
Text: 
<source lang="text">
{{stardate::TK}}
{{cache_stardate::TK}}
</source>
Image: 
<source lang="text">
{{stardate::TKGT}}
{{stardate::TKGT::gttagname}}
{{cache_stardate::TKGT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 
==Stardate of Star Trek XI==
[[File:Module_stardate_stxi.jpg|left|Stardate]]Source: trekguide.com Output as a positive number for today. Output in the form: YYYY.xx , YYYY is the current year, xx the 100th Part of the year. 
Text:
<source lang="text">
{{stardate::XI}}
{{cache_stardate::XI}}
</source>
Image:
<source lang="text">
{{stardate::XIGT}}
{{stardate::XIGT::gttagname}}
{{cache_stardate::XIGT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 

==Stardate TNG (1)==
[[File:Module_stardate_tng1.jpg|left|Stardate]]Source: lcars.org.uk Output as a negative number for today. Stardate 00000.0 begins on 0/01/2323 00:00 AM 
Text:
<source lang="text">
{{stardate::TNG2323}}
{{cache_stardate::TNG2323}}
</source>
Image:
<source lang="text">
{{stardate::TNG2323GT}}
{{stardate::TNG2323GT::gttagname}}
{{cache_stardate::TNG2323GT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 

==Stardate TNG (2)==
[[File:Module_stardate_tng2.jpg|left|Stardate]]Source: trekguide.com Output as a negative number for today. Stardate 00000.0 begins on 05/25/2322 00:00 AM 
Text:
<source lang="text">
{{stardate::TNG2322}}
{{cache_stardate::TNG2322}}
</source>
Image:
<source lang="text">
{{stardate::TNG2322GT}}
{{stardate::TNG2322GT::gttagname}}
{{cache_stardate::TNG2322GT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 

==Stardate TOS==
[[File:Module_stardate_tos.jpg|left|Stardate]]Source: trekguide.com Output as a negative number for today. Stardate 00000.0 begins on 05/01/2265 00:00 AM 
Text:
<source lang="text">
{{stardate::TOS}}
{{cache_stardate::TOS}}
</source>
Image:
<source lang="text">
{{stardate::TOSGT}}
{{stardate::TOSGT::gttagname}}
{{cache_stardate::TOSGT::gttagname}}
</source>
Where "[[Stardate#Determination_the_.22gttagname.22|gttagname]]" the name chosen in [[GraphicalText]] module. If no declaration, "Stardate" used as the default.
 

=Determination the "gttagname"=
The "gttagname" is the "Tag" name as it was created in the back end module in the graphical text. The overview is the name in the first column in edit mode the field "Tag". 
[[File:Module_stardate_gttagname.jpg|gttagname]]
 
----
--[[User:BugBuster|BugBuster]] 00:38, 26 September 2010 (CEST)

Dlstats

2016-06-19T19:23:48Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Counts the number of file downloads

* Download statistics for the standard content elements Download and Downloads
* Count number of downloads per file plus latest download timestamp
* Optionally log every single download with timestamp, IP and username.
* Insert-Tag for number of downloads in the frontend (from 2.1.0)
* Ignore certain IPs (define itself, from 2.1.0)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion=2.4.1 / 3.4.0
| Version=from 2.9
| TLVersion=2.7.6 - 2.8.4
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=http://www.contao.org/extension-list/view/dlstats.en.html
| TrackerLink=https://github.com/BugBuster1701/dlstats/issues
}}
[[de:dlstats]]
[[Category:Extensions]]

==Installation==
The installation of the module occurs about the extension Repository in back end of Contao. On manual installation, call /contao/install.php - Perform Update Database. 
'''''For manual installation, please note that the module "[[Bot Detection|Bot Detection]]" must be installed.'''''

==Using==
Go to the Contao Settings and switch on the logging, either only counting the number of downloads per file, or optionally also log each download with timestamp and IP. 
'''For dlstats 2.1.x:''' In the settings you can be deactivated the Anonymize IP function, it must be the admin. 
'''From dlstats 2.2.0:''' IP addresses anonymous: "yes/no" is now controlled by Contao itself. 
(System - Settings - Privacy settings - Anonymize IP addresses) 
Use the content element File Download or File Downloads for all downloaded files you want to have counted. 
After downloading a file you will find the statistics under Content - Download Stats.

==Using Insert-Tag==
The Insert-Tag "cache_dlstats::total downloads::..." supports both, the source of the file (relative path + file name), as well as in connection with the article alias and how it generates for ce_download and ce_downloads. Therefore, the use is well used in the templates of the two CEs, see examples. Return is only the number of downloads as a number.
<source lang="php">
{{cache_dlstats::totaldownloads::tl_files/cdc2010.pdf}}
{{cache_dlstats::totaldownloads::CDC_2010.html?file=tl_files/cdc2010.pdf}}

// in ce_download template:
{{cache_dlstats::totaldownloads::<?php echo $this->href; ?>}}

// in ce_downloads template:
{{cache_dlstats::totaldownloads::<?php echo $file['href']; ?>}}
</source>

==Ignore certain IPs==
If any downloads from certain IP addresses should not be counted, this can be defined in the localconfig.php as follows:
<source lang="php">
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.1.2';
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.0.0/24';
//respectively
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Notice==
* Simple links to files will not be counted as downloads!
* If you are logged in the backend, your download is not counted. (from 2.1.0)

----
--[[User:BugBuster|BugBuster]] 20:07, 1 April 2013 (CEST)

Enhanced error.log

2016-05-12T15:08:52Z

BugBuster: Created page with ""Enhanced error.log" generate the Contao error.log with complete relative file paths. {{ExtInfo | Dev=Glen Langer (BugBuster) | DevSite=https://contao.ninj..."

"Enhanced error.log" generate the Contao error.log with complete relative file paths.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=https://contao.ninja
| ExtVersion=1.0.0
| Version=from 3.5
| ERLink=https://contao.org/en/extension-list/view/errorlog_enhanced.en.html
| TrackerLink=https://github.com/BugBuster1701/errorlog_enhanced/issues
| VCSLink=https://github.com/BugBuster1701/errorlog_enhanced
| Comment=Version for Contao 3.5 online
}}
[[de:Enhanced_error.log]]
[[Category:Extensions]]

{{Hint|This page is no longer updated by the developer.
The current manual for the extension "Enhanced error.log" can be found here: [https://docs.contao.ninja/en/enhanced-error-log.html docs.contao.ninja]}}

Xing

2016-03-26T20:15:46Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
[[File:Mod_xing_team.tpl.jpg|right|Xing Team]]Normally, you need not a module, because it is just a linked image. 
But my aim was:
*to select the image
*to determine the position
*several of them on one side, or distributed on several domains.
 
First, categories are created, in these categories then the XING profile(s). With the XING-Lister, you can select the category that are used. Each front-end module can be assigned their own template. Three different templates are included. (see "[[Xing#Using|Using]]")
 
Thus, it is then possible, the categories to distribute on several layouts or several domains. Are there more than one profile in a category, all profiles will be shown from this category. Thus it would be e.g. possible to show the profiles of a whole team.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion= C3 3.1.0 / C4 1.0.0
| Version=from 2.9
| ERLink=http://www.contao.org/extension-list/view/gl_xing.html / https://github.com/BugBuster1701/contao-xing-bundle
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/contao_xing/issues / https://github.com/BugBuster1701/contao-xing-bundle/issues
| Comment=Version for Contao 3 and Contao 4 are online
}}
[[de:Xing]]
[[Category:Extensions]]

=Forum=
Questions about the Xing module will be answered in forum: 
English: [https://community.contao.org/en/forumdisplay.php?15 Forum] 
German: [https://community.contao.org/de/forumdisplay.php?119 Forum] 
 
Errors and requests can be reported in the Issue Tracker. (Links see above.)

=Installation in Contao 3=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [https://contao.org/en/extension-list/view/gl_xing.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/gl_xing". 
Then call /contao/install.php - Perform Update Database. 

=Installation in Contao 4=
Installation is performed using Composer. Details see [https://github.com/BugBuster1701/contao-xing-bundle/blob/master/README.md Readme on GitHub].

==Contao 3: Xing Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Xing_Update_v1_to_v2|'''Xing Update Version 1 to Version 2''']]
 

=Overview=
The Xing module contains a back end and a front end module. 
In the back end, there are "Xing", for the front end "Xing list".

==Back end==

===Xing===
[[File:Xing_en_backend.jpg|Xing Module Backend]]
 

==Frontend==
For the front end module, a CSS file is included as an example:
*mod_xing_fe.css for a normal, line-by-line output.

===Xing Banner===
The simplest variant, only the linked image: 
[[File:Module_Xing_List.tpl.jpg|Xing Banner]]
 
The more complex variant, several Xing banner of a team, with team name and names of team members. 
[[File:Module_Xing_Team.jpg|Xing Team]]
 

=Using=
First, create a new category. In the category create the Xing profile(s). 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Xing#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Xing'. In the main area click on the button 'New category'. 
[[File:Xing_en_backend_category.jpg|Xing - New category]] 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create Xing Profile==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New profile' and then the arrow icon, or click the plus in the head of the category: 
[[File:Xing_en_backend_profile_new.jpg|Xing - neues Profil]] 
Now, some information are needed:
* XING Profile, e.g.: John_Doe, explanations are provided in the help. (Help Wizard)
* XING Layout , explanations are provided in the help. (Help Wizard)
* activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> (Front end) Modules -> Add module (Contao 2.9 and newer)
 
At first, enter the title, and only then select in "Module type": 'Xing' - 'Xing list'. It changes the form fields. 
In 'Xing Category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, is provided a CSS file for presentation. 
For the first tests you should copy the file mod_xing_fe.css from '''/system/modules/gl_xing''' to '''/tl_files''' / '''/files'''. 
Then import them over the back end and activate it in the layout. 

=Technical Details=
Technical details are inside of the category and in the constructed front end module feasible / adjustable.

==Technical Details inside of the category==
===Team Profile===
In the category, you can create multiple Xing profiles. 
Use would be for example an overview of all team members. 
Depending on the template selection in front-end module, the category name is the team name. 
See the next section, as it could look like then.

==Technical Details in the front end module definition==
===XING Template===
Is defined in the category only one Xing profile, the following two templates are useful:
* mod_xing_list, it shows only the linked graphic [[File:Module_Xing_List.tpl.jpg‎|mod_xing_list]]
* mod_xing_list_profile, it shows the linked graphic, including the profile name (underscore is removed) [[File:Module_Xing_Profile.tpl.jpg‎|mod_xing_profile]]

 
If several Xing profiles defined in the category to represent a team, the following two templates are useful:
* mod_xing_list_profile, it displays the graphics linked with each other, each including the profile name (underscore is removed) [[File:Module_Xing_Profile-2.tpl.jpg‎|mod_xing_profile]]
* mod_xing_list_team, as mod_xing_list_profile, in addition displays above the first graphic the team name (category name) [[File:Module_Xing_Team.jpg‎|mod_xing_team]]
 
You can save your own templates in the folder /templates or in the template folder of the used theme. 
Template names must begin with '''''mod_xing_list''''' and must have the suffix '''''.tpl''''' / '''''.xhtml''''' / '''''.html5'''''. ( e.g.: '''''mod_xing_list_club66.xhtml''''' )
 
===Company Template===
For a company profile, XING has a different destination URL. Therefore it was created a custom template.
Please select the template "mod_xing_list_company" for a company profile.

===Show to guests only===
Hide the module if a member is logged in.

===Protect module===
Show the module to certain member groups only.

Visitors

2015-08-25T19:06:29Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{Hint|This page is no longer updated by the developer.
The current manual for the extension Visitors can be found here: [http://docs.contao.ninja/en/visitors.html docs.contao.ninja]}}

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.2 / 3.2.1
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.2 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-visitors/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".html5" or ".xhtml".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Banner

2015-08-25T19:04:28Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
A banner advertisement module with a simple form of weighting. 
In Backend you can see banner view and banner click statistics. (System Menu) 
 
IP-based ReClick blocker was integrated (5 minutes). Forwarding functioned, but isn't counted. 
Similarly, the views within a period not re-counted if the same banner displayed. (10 minutes) 
The amount of time to block the view count can be changed. 
 
By using the module "[[Bot Detection |Bot Detection]]" requests from bots and search engines are not counted. 
 
In the module directory is located in the file '''mod_banner_fe.css''' some CSS sample data. These can be included in the layout or you can import the file and activate this in the layout.

{{Hint|This page is no longer updated by the developer.
The current manual for the extension Banner can be found here: [http://docs.contao.ninja/en/banner.html docs.contao.ninja]}}

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion=3.5.0
| Version=from 2.9
| TLVersion=2.6.2 - 2.8.4 (see installations notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/banner.en.html
| TrackerLink=https://github.com/BugBuster1701/banner/issues
| VCSLink=https://github.com/BugBuster1701/banner
| Comment=Version for Contao 3.4 online
}}
[[de:Banner]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/banner/issues Issue Tracker].
 

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-banner/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/banner.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/banner". 
Then call /contao/install.php - Perform Update Database. 
 
'''''The module Banner is dependent on the modules "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Banner Module Version 1.11.2 ([http://www.contao.org/extension-list/view/banner.10110029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Banner Module Version 1.9.2 ([http://www.contao.org/extension-list/view/banner.10090029.en.html Direct Link])
===TYPOlight 2.6===
Users of TYPOlight 2.6.x, please use Banner Module Version 1.6.5 ([http://www.contao.org/extension-list/view/banner.10060059.en.html Direct Link])
 

=Installation as an update=
An update is identical to the installation. 
'''Notice when updating from < 1.10.0 to the latest version:''' 
The CSS file "mod_banner_fe.css" which is included as an example, the uppercase / lowercase letters changed in a class. 
Anyone who has imported this file or the design itself has to produce, the class ".mod_Banner" must change in ".mod_banner". 

==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Banner_Update_v1_to_v2|'''Banner Update Version 1 to Version 2''']]
 

=Overview=
The Banner Module contains two back end and one front end module. 
In the back end, there are "Banner" and "Banner Statistic", for the front end "Banner".

==Back end==

===Banner===
[[File:Banner_en_backend_banner.jpg|Back end module Banner]]

===Banner Statistic===
[[File:Banner_en_backend_bannerstatistic.jpg|Back end module Banner Statistic]]

==Front end==

===Display a banner===
[[File:Banner_en_frontend_one_banner.jpg|Front end module Banner]]
# Module Headline
# Banner Image
# Banner Comment
# Banner Name

More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".

===Display all Banner===
With 'all Banner' is meant here, all banners in the selected category. 
[[File:Banner_en_frontend_all_banner.jpg|Front end all banner|left]]
In this example, 3 banners have been defined, 
* Graphic Banner
* Flash Banner
* Text Banner 
More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".
 

=Using=
The first one creates a new banner category via the menu item "banner". In this then the banners.
Then, create a front end module and build it into the layout of the page.
Here are the steps, each with the default values. [[Banner#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Banner'. In the main area click on the button 'New category'.
[[File:Banner_en_backend_category_new.jpg|New Banner Category]]

There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create the banners==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New Banner' and then the arrow icon, or click the plus in the head of the category: 
[[File:Banner_en_backend_banner_new.jpg|New Banner]]

First they must select the banner source:
* internal Banner (Graphic / Flash files is stored on server)
* external Banner (Graphic / Flash files are integrated via URL)
* Text Banner
 
After selecting it appear the appropriate form fields.

===Graphic Banners===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template appears below the banner graphic.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the banner graphic. The input must include "http://".
#* Optional field.
#* Without a URL, the banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
#* '''CAUTION''': Animated GIFs are for size definitions through the GD recalculation unfortunately to still images.
# Banner Comment
#* The first line will be installed and displayed as a "title" tag in the HTML source code if you move the cursor over the banner graphic.
# Published
#* If this option is not selected, this banner is not displayed.

===Flash Banner===
# Banner Name
#* The banner name will be displayed only in the Banner overview.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the Flash Banner. The input must include "http://".
#* Optional field.
#* Without a URL, the Flash Banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
# Banner Comment
#* Input is not necessary, is not used in the front end
# Published
#* If this option is not selected, this banner is not displayed.

A flash fallback to an image file is available, see the section [[Banner#Flash_Fallback_Image|Technical Details]]

===Text Banner===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template as a headline that is linked simultaneously with the target URL.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking. The input must include "http://".
#* Optional field.
#* Without a URL, the Text Banner will be displayed without a link.
#* in provided template only the domain is shown as a short form. (Third row, see picture above)
# Banner Comment
#* This is the text line. (Second row, see picture above)
# Published
#* If this option is not selected, this banner is not displayed.

==Front end module==
A new front-end module is create with: 
* Layout -> Themes -> Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
Be sure to '''first enter the title''', then selecting for module type:''Miscellaneous -> Banner''.
Now the form fields change accordingly. 
In 'Banner Categories' select the previously created category, then 'Save and Close'. 
 
Now, the front end module must be included in the layout: 
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)
Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
For the first tests you should copy the provided file mod_banner_fe.css from /system/modules/banner to /tl_files . Then import them over the back end and activate it in the layout.

=Technical Details=
Technical details are inside of the category, in the banner denifinition and in the constructed front end module feasible / adjustable.

==Technical Details in the Category Definition==
===Number of banners===
* Show all banners
If you choose this option, all active banners will be showed in front end. 
In addition, you can choose:
* Limiting the number of banners
Here, the number can be limited. Default is 0: show all banners, otherwise maximum number of banners that will be showed.
* Random order
If you choose this option, the banners will shown in a random order.
* Protect the statistic
Show the banner statistic for this category to certain user groups only. Administrators have unlimited access to all banner statistics.

==Technical Details in the Banner Definition==
===Flash Fallback Image===
If a browser does not support Flash or JavaScript is disabled, an image can be displayed instead (since version 2.2.0). At a local (internal) flash file, in the same path is searched for an image file with the same name but with the ending jpg, png or gif. 
Example: for "myflash.swf" would be a fallback image: "myflash.jpg" 
Was found a replacement image, the image is displayed. If necessary, the image is converted to the dimensions of the flash file.

===Display limitation by Start / Stop dates and times===
* Show from
** If you enter a date and time value here the current banner will not be shown on the website before this moment.
* Show until
** If you enter a date and time value here the current banner will not be shown on the website after this moment.

===Limiting the number of Views and Clicks===
* Limiting the number of Views and Clicks
If you select this option, you can define a maximum number of views and/or maximum number of clicks.
* Limiting the number of Views
** By entering a number, the current banner is no longer displayed after this number of views. The "Limiting the number of Views and Clicks" has enabled it to stay.
* Limiting the number of Clicks
** By entering a number, the current banner is no longer displayed after this number of clicks. The "Limiting the number of Views and Clicks" has enabled it to stay.

===Filter Domain===
If you enter a domain name, this banner is used only for this domain.If you leave the field empty, this banner is used for all domains. Example: '''yourdomain.com''' 
 
The banner will be displayed, if matches the domain. But also in partial match starting from the right. So also with access via "'''sub.yourdomain.com'''" .An entry in "Site structure" - "Domain Name" is not required for the filtering.

==Technical Details in the Front end Module Definition==

===First banner for new visitor===
For each new visitor, at first is displayed the first published banner in the category. The choice is then returned to random mode. Thus, a kind of recognition can be achieved.

===Templates===
Each module can be assigned its own Template. Two different templates are included. 
* mod_banner_list_all
** All fields are included.
* mod_banner_list_min
** The headline and name were removed. It will only display the banner itself.

Both templates also support text banners. 
For own Templates, the template files must start with "mod_banner_list_" and end with ".xhtml" / ".html5".
Example: "mod_banner_list_special.html5"

{{Note|In Banner Version 1.x this selection is located in the banner category.}}
 

===Prevention of counting their own requests===
You can set a custom UserAgent String in your browser and in the banner modul configuration.
 
Via:
* Layout -> Themes -> Modules -> Modul Name (Contao 2.9 and newer)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the applied banners module in the new field "No counting for this HTTP_USER_AGENT partial identifier" , a string is entered, it should be unique. 
Example: CTISOK 
Save it. 
Several strings are also possible, then enter them separated by commas. 
So you can change the User Agent String of Mozilla Firefox: 
 
# use Add-on: User Agent Switcher
# insert your own user agent string and change then the string
# Add her "CTISOK" separated by space, e.g. "Firefox/35.0.1 CTISOK".

=Specific feature=
==Bot Detection off==
Who wants to count the hits from bots and search engines on the banners can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_bot_check'] = false;
</source>

 

==Change Banner Block Time for Views==
As written in the beginning, when a banner is displayed multiple times within 10 minutes (C3: 5 minutes), this banner is only counted once. 
With an entry in the localconfig.php can change that. The values be there in minutes, the number must be> 0, otherwise will be automatically taken back to the default value (10).
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after ### INSTALL SCRIPT STOP ### ) causes a change to 5 minutes: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_block_time'] = 5;
</source>
 

==Exception: No active banners defined and no default banner defined==
If, in this case, "Hide if empty" is not activated, until now was an empty image tag generated, what was presented by the IE as Broken Image. From version 1.11.2 now a DIV tag with class = "banner_empty" is generated:
<source lang="html4strict">
<div class="mod_banner">
<div class="banner_empty">

</div>
</div>
</source>
With CSS can now be reached that is maintained (in this example) the amount and thus the layout of the site will not change:
<source lang="css">
.mod_banner .banner_empty {
height:90px;
}
</source>
The resultant text can be overridden to enforce in langconfig.php, here is an example of an empty text:
<source lang="php">
$GLOBALS['TL_LANG']['MSC']['tl_banner']['noBanner'] = '';
</source>

 
==Special case: Multiple Banner modules on one page==
Here are some hints and tips for well-known application scenarios and their characteristics.

===One category - Two front end modules on one page===
In the current version it is possible to display all the banners from one category. 
The old version's multiple banners on a Web page was to be able to create multiple front end modules and integrating them into the website. The module is prevented that a banner will not appear more than once. 
Well, it was assumed that all displayed below each other, so it made sense, the module title to display only once. 
If you want to leave now for all the title's banner front-end modules, because they are distributed on the page, must be made for this purpose a small modification to the template. Create a copy on the back end of the template "mod_banner_list_all" and renames it here, for example, in "mod_banner_list_special.tpl. 
There, now you change the third line as follows: 
Original: 
<source lang="php">
<?php if (($this->headline) && (!$this->headline_stop)): ?>
</source>
Special: 
<source lang="php">
<?php if ($this->headline) : ?>
</source>
Now edit the banner front end modules and select the new template. 
Done.
 
This is also true for more than two front end modules.
 

===Two categories - Two front end modules on one page===
In this case, each front end module its own category. Again, only on the first module, the heading will appear for the same reason as in the previous section. 
If you want to display in this scenario all module headers, the solution is the same. 
This is also true for more than two front end modules.
 
 

----
--[[User:BugBuster|BugBuster]] ([[User talk:BugBuster|talk]]) 00:31, 17 February 2015 (CET)

Add Language To Url

2015-07-12T19:09:59Z

BugBuster: Created page with "Add Language To Url" add language to URL, but only for individual domains. Therefore, only useful for multi-domain installations. Domains must be defined by name via backend s..."

Add Language To Url" add language to URL, but only for individual domains. Therefore, only useful for multi-domain installations. Domains must be defined by name via backend settings. In Contao itself there is this possibility only per installation. 
It will be also individually adapted the sitemaps and the search index. 

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion=1.0.3
| Version=from 3.4.0
| ERLink=https://packagist.org/packages/bugbuster/contao-lang_to_url
| TrackerLink=https://github.com/BugBuster1701/contao-lang_to_url/issues
| VCSLink=https://github.com/BugBuster1701/contao-lang_to_url
| Comment=not published in ER2
}}
[[de:Add_Language_To_Url]]
[[Category:Extensions]]

=Forum=
Questions about this extension will be answered in forum: [https://community.contao.org/en/forumdisplay.php?143 Contao Forum]

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-lang_to_url/ Transifex]

=User Guide=
The user guide is published on [http://docs.contao.ninja/en/add-language-to-url.html docs.contao.ninja].

----
--[[User:BugBuster|BugBuster]] ([[User talk:BugBuster|talk]]) 21:09, 12 July 2015 (CEST)

Bot Detection

2015-02-16T23:39:23Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:Bot_detection.jpg|right|No Bots!]]Bot Detection is a helper class for other extensions (Frontend) the need to detect whether the access is human or machine. 
(Detection of Search Engines, Spider, Crawler, Bots, Harvester, ...)
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.7.2 / 3.4.0
| Version=from 2.9
| TLVersion=2.8
| ERLink=http://www.contao.org/extension-list/view/botdetection.en.html
| TrackerLink=https://github.com/BugBuster1701/botdetection/issues
| DonateLink=Cappuccino
| Comment=Now on GitHub
}}

[[de:Bot_Detection]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/botdetection/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/botdetection/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/botdetection.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/botdetection". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations )

=Using=
The module Bot Detection provides three methods for detection. 
A reliable detection is not possible. 
It is to use two methods to detect this: 
* User Agent
* IP adress (IPv4, IPv6 from version 1.4.0)

The modul includes a method for the agent [[Bot_Detection#Method_BD_CheckBotAgent|BD_CheckBotAgent]] and one for the IP detection [[Bot_Detection#Method_BD_CheckBotIP|BD_CheckBotIP]]. 
These two methods return only "true" or "false" and are only a rough search on strings and substrings to identify the most important bots. 
Another method [[Bot_Detection#Method_BD_CheckBotAgentAdvanced|BD_CheckBotAgentAdvanced]] comes with an external configuration file for the user agent detection. As a result, it returns the short name of the bots or "false".

==Method BD_CheckBotAgent==
The method BD_CheckBotAgent "searches in two steps to be completed as quickly as possible. 
Step 1 searches for substrings that appear in most search engines / bots in the name: 
<source lang="text">
'bot'
'spider'
'spyder'
'crawl'
'slurp'
'robo'
'yahoo'
</source>

Step 2 then looks for other strings that usually follow the name of the search engine, such as: 
<source lang="text">
'altavista'
'archiver'
'inktomi'
'twiceler'
...
</source>
The result is "true" or "false". ("true" = search engine / bot found)

==Method BD_CheckBotIP==
The bot from Google, MSN / Bing looking sometimes with the user agent from a browser. 
To uncover these "undercover" search engines, you must be filtered by IP address. 
 
There is also configuration files in the ''config'' directory of the module: '''''bot-ip-list.txt''''' and '''''bot-ip-list-ipv6.txt''''' 
Current content knows an IP address of a spider from Israel as well as network addresses for Google and MSN / Bing. 
Additional IP addresses or networks can be entered in this file, but they are not then upgrade secure. 
Therefore, it is better to post them in the localconfig.php as follows: 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.1.2';
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.0.0/24';
</source>
For IPv6 on this way:
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Method BD_CheckBotAgentAdvanced==
The method BD_CheckBotAgentAdvanced "is controlled by an external configuration file to detect the user agent. 
The result is the short name of the bots or "false". 
 
The external configuration file is generated from known user agent information from search engines / bots and regularly renewed. 
'''Note''' 
This external DB differentiates between different types of search engines from a manufacturer. 
For example, the return is not "Google", but "Googlebot" or "Googlebot-Image" or "Googlebot-Mobile" and so on, depending on what was recognized. 
These multiple name of a search engine are also available from other producers such as MSN, Yahoo, and so on.
 
Own or unknown user agent identifiers can be entered in the file '''/system/config/localconfig.php''': 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("unitbot","UniBot from FHTW");
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("myprivat","My privat bot");
</source>
The parameters are: short name in lower case, description.

=Demo Modules=
Module Bot Detection has 2 frontend demo modules as a demo for the implementation in your own modules. 
The using in the demo class is made by import.
<source lang="php">
$this->import('ModuleBotDetection');
</source>

==Frontend Demo 1==
Demo 1 tests with all three methods, the current IP and User Agent identifier and displays the results. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_1.html Demo 1].

==Frontend Demo 2==
Demo 2 makes available a form to check whether a user agent identifier from the module would be recognized as a bot. 
These are called the two agent methods and displays the result. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_2.html Demo 2].
 

----
--[[User:BugBuster|BugBuster]] 21:42, 1 July 2011 (CEST)

Banner

2015-02-16T23:31:58Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
A banner advertisement module with a simple form of weighting. 
In Backend you can see banner view and banner click statistics. (System Menu) 
 
IP-based ReClick blocker was integrated (5 minutes). Forwarding functioned, but isn't counted. 
Similarly, the views within a period not re-counted if the same banner displayed. (10 minutes) 
The amount of time to block the view count can be changed. 
 
By using the module "[[Bot Detection |Bot Detection]]" requests from bots and search engines are not counted. 
 
In the module directory is located in the file '''mod_banner_fe.css''' some CSS sample data. These can be included in the layout or you can import the file and activate this in the layout.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.ninja
| ExtVersion=3.5.0
| Version=from 2.9
| TLVersion=2.6.2 - 2.8.4 (see installations notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/banner.en.html
| TrackerLink=https://github.com/BugBuster1701/banner/issues
| VCSLink=https://github.com/BugBuster1701/banner
| Comment=Version for Contao 3.4 online
}}
[[de:Banner]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/banner/issues Issue Tracker].
 

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-banner/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/banner.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/banner". 
Then call /contao/install.php - Perform Update Database. 
 
'''''The module Banner is dependent on the modules "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Banner Module Version 1.11.2 ([http://www.contao.org/extension-list/view/banner.10110029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Banner Module Version 1.9.2 ([http://www.contao.org/extension-list/view/banner.10090029.en.html Direct Link])
===TYPOlight 2.6===
Users of TYPOlight 2.6.x, please use Banner Module Version 1.6.5 ([http://www.contao.org/extension-list/view/banner.10060059.en.html Direct Link])
 

=Installation as an update=
An update is identical to the installation. 
'''Notice when updating from < 1.10.0 to the latest version:''' 
The CSS file "mod_banner_fe.css" which is included as an example, the uppercase / lowercase letters changed in a class. 
Anyone who has imported this file or the design itself has to produce, the class ".mod_Banner" must change in ".mod_banner". 

==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Banner_Update_v1_to_v2|'''Banner Update Version 1 to Version 2''']]
 

=Overview=
The Banner Module contains two back end and one front end module. 
In the back end, there are "Banner" and "Banner Statistic", for the front end "Banner".

==Back end==

===Banner===
[[File:Banner_en_backend_banner.jpg|Back end module Banner]]

===Banner Statistic===
[[File:Banner_en_backend_bannerstatistic.jpg|Back end module Banner Statistic]]

==Front end==

===Display a banner===
[[File:Banner_en_frontend_one_banner.jpg|Front end module Banner]]
# Module Headline
# Banner Image
# Banner Comment
# Banner Name

More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".

===Display all Banner===
With 'all Banner' is meant here, all banners in the selected category. 
[[File:Banner_en_frontend_all_banner.jpg|Front end all banner|left]]
In this example, 3 banners have been defined, 
* Graphic Banner
* Flash Banner
* Text Banner 
More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".
 

=Using=
The first one creates a new banner category via the menu item "banner". In this then the banners.
Then, create a front end module and build it into the layout of the page.
Here are the steps, each with the default values. [[Banner#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Banner'. In the main area click on the button 'New category'.
[[File:Banner_en_backend_category_new.jpg|New Banner Category]]

There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create the banners==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New Banner' and then the arrow icon, or click the plus in the head of the category: 
[[File:Banner_en_backend_banner_new.jpg|New Banner]]

First they must select the banner source:
* internal Banner (Graphic / Flash files is stored on server)
* external Banner (Graphic / Flash files are integrated via URL)
* Text Banner
 
After selecting it appear the appropriate form fields.

===Graphic Banners===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template appears below the banner graphic.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the banner graphic. The input must include "http://".
#* Optional field.
#* Without a URL, the banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
#* '''CAUTION''': Animated GIFs are for size definitions through the GD recalculation unfortunately to still images.
# Banner Comment
#* The first line will be installed and displayed as a "title" tag in the HTML source code if you move the cursor over the banner graphic.
# Published
#* If this option is not selected, this banner is not displayed.

===Flash Banner===
# Banner Name
#* The banner name will be displayed only in the Banner overview.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the Flash Banner. The input must include "http://".
#* Optional field.
#* Without a URL, the Flash Banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
# Banner Comment
#* Input is not necessary, is not used in the front end
# Published
#* If this option is not selected, this banner is not displayed.

A flash fallback to an image file is available, see the section [[Banner#Flash_Fallback_Image|Technical Details]]

===Text Banner===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template as a headline that is linked simultaneously with the target URL.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking. The input must include "http://".
#* Optional field.
#* Without a URL, the Text Banner will be displayed without a link.
#* in provided template only the domain is shown as a short form. (Third row, see picture above)
# Banner Comment
#* This is the text line. (Second row, see picture above)
# Published
#* If this option is not selected, this banner is not displayed.

==Front end module==
A new front-end module is create with: 
* Layout -> Themes -> Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
Be sure to '''first enter the title''', then selecting for module type:''Miscellaneous -> Banner''.
Now the form fields change accordingly. 
In 'Banner Categories' select the previously created category, then 'Save and Close'. 
 
Now, the front end module must be included in the layout: 
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)
Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
For the first tests you should copy the provided file mod_banner_fe.css from /system/modules/banner to /tl_files . Then import them over the back end and activate it in the layout.

=Technical Details=
Technical details are inside of the category, in the banner denifinition and in the constructed front end module feasible / adjustable.

==Technical Details in the Category Definition==
===Number of banners===
* Show all banners
If you choose this option, all active banners will be showed in front end. 
In addition, you can choose:
* Limiting the number of banners
Here, the number can be limited. Default is 0: show all banners, otherwise maximum number of banners that will be showed.
* Random order
If you choose this option, the banners will shown in a random order.
* Protect the statistic
Show the banner statistic for this category to certain user groups only. Administrators have unlimited access to all banner statistics.

==Technical Details in the Banner Definition==
===Flash Fallback Image===
If a browser does not support Flash or JavaScript is disabled, an image can be displayed instead (since version 2.2.0). At a local (internal) flash file, in the same path is searched for an image file with the same name but with the ending jpg, png or gif. 
Example: for "myflash.swf" would be a fallback image: "myflash.jpg" 
Was found a replacement image, the image is displayed. If necessary, the image is converted to the dimensions of the flash file.

===Display limitation by Start / Stop dates and times===
* Show from
** If you enter a date and time value here the current banner will not be shown on the website before this moment.
* Show until
** If you enter a date and time value here the current banner will not be shown on the website after this moment.

===Limiting the number of Views and Clicks===
* Limiting the number of Views and Clicks
If you select this option, you can define a maximum number of views and/or maximum number of clicks.
* Limiting the number of Views
** By entering a number, the current banner is no longer displayed after this number of views. The "Limiting the number of Views and Clicks" has enabled it to stay.
* Limiting the number of Clicks
** By entering a number, the current banner is no longer displayed after this number of clicks. The "Limiting the number of Views and Clicks" has enabled it to stay.

===Filter Domain===
If you enter a domain name, this banner is used only for this domain.If you leave the field empty, this banner is used for all domains. Example: '''yourdomain.com''' 
 
The banner will be displayed, if matches the domain. But also in partial match starting from the right. So also with access via "'''sub.yourdomain.com'''" .An entry in "Site structure" - "Domain Name" is not required for the filtering.

==Technical Details in the Front end Module Definition==

===First banner for new visitor===
For each new visitor, at first is displayed the first published banner in the category. The choice is then returned to random mode. Thus, a kind of recognition can be achieved.

===Templates===
Each module can be assigned its own Template. Two different templates are included. 
* mod_banner_list_all
** All fields are included.
* mod_banner_list_min
** The headline and name were removed. It will only display the banner itself.

Both templates also support text banners. 
For own Templates, the template files must start with "mod_banner_list_" and end with ".xhtml" / ".html5".
Example: "mod_banner_list_special.html5"

{{Note|In Banner Version 1.x this selection is located in the banner category.}}
 

===Prevention of counting their own requests===
You can set a custom UserAgent String in your browser and in the banner modul configuration.
 
Via:
* Layout -> Themes -> Modules -> Modul Name (Contao 2.9 and newer)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the applied banners module in the new field "No counting for this HTTP_USER_AGENT partial identifier" , a string is entered, it should be unique. 
Example: CTISOK 
Save it. 
Several strings are also possible, then enter them separated by commas. 
So you can change the User Agent String of Mozilla Firefox: 
 
# use Add-on: User Agent Switcher
# insert your own user agent string and change then the string
# Add her "CTISOK" separated by space, e.g. "Firefox/35.0.1 CTISOK".

=Specific feature=
==Bot Detection off==
Who wants to count the hits from bots and search engines on the banners can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_bot_check'] = false;
</source>

 

==Change Banner Block Time for Views==
As written in the beginning, when a banner is displayed multiple times within 10 minutes (C3: 5 minutes), this banner is only counted once. 
With an entry in the localconfig.php can change that. The values be there in minutes, the number must be> 0, otherwise will be automatically taken back to the default value (10).
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after ### INSTALL SCRIPT STOP ### ) causes a change to 5 minutes: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_block_time'] = 5;
</source>
 

==Exception: No active banners defined and no default banner defined==
If, in this case, "Hide if empty" is not activated, until now was an empty image tag generated, what was presented by the IE as Broken Image. From version 1.11.2 now a DIV tag with class = "banner_empty" is generated:
<source lang="html4strict">
<div class="mod_banner">
<div class="banner_empty">

</div>
</div>
</source>
With CSS can now be reached that is maintained (in this example) the amount and thus the layout of the site will not change:
<source lang="css">
.mod_banner .banner_empty {
height:90px;
}
</source>
The resultant text can be overridden to enforce in langconfig.php, here is an example of an empty text:
<source lang="php">
$GLOBALS['TL_LANG']['MSC']['tl_banner']['noBanner'] = '';
</source>

 
==Special case: Multiple Banner modules on one page==
Here are some hints and tips for well-known application scenarios and their characteristics.

===One category - Two front end modules on one page===
In the current version it is possible to display all the banners from one category. 
The old version's multiple banners on a Web page was to be able to create multiple front end modules and integrating them into the website. The module is prevented that a banner will not appear more than once. 
Well, it was assumed that all displayed below each other, so it made sense, the module title to display only once. 
If you want to leave now for all the title's banner front-end modules, because they are distributed on the page, must be made for this purpose a small modification to the template. Create a copy on the back end of the template "mod_banner_list_all" and renames it here, for example, in "mod_banner_list_special.tpl. 
There, now you change the third line as follows: 
Original: 
<source lang="php">
<?php if (($this->headline) && (!$this->headline_stop)): ?>
</source>
Special: 
<source lang="php">
<?php if ($this->headline) : ?>
</source>
Now edit the banner front end modules and select the new template. 
Done.
 
This is also true for more than two front end modules.
 

===Two categories - Two front end modules on one page===
In this case, each front end module its own category. Again, only on the first module, the heading will appear for the same reason as in the previous section. 
If you want to display in this scenario all module headers, the solution is the same. 
This is also true for more than two front end modules.
 
 

----
--[[User:BugBuster|BugBuster]] ([[User talk:BugBuster|talk]]) 00:31, 17 February 2015 (CET)

Visitors

2014-08-11T21:20:03Z

BugBuster: /* Templates */

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.2 / 3.2.1
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.2 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-visitors/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".html5" or ".xhtml".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Integrity Check

2014-07-27T16:31:08Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.10 / 3.4.0
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-integrity_check/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php
* .htaccess (from version 3.1.0)

Special warning tests:
* Check for new Contao versions (from version 3.4.0)
* Check for install tool locking (from version 3.4.0)

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] ([[User talk:BugBuster|talk]]) 18:31, 27 July 2014 (CEST)

File:Check overview en.jpg

2014-07-27T16:27:33Z

BugBuster: BugBuster uploaded a new version of "File:Check overview en.jpg"

Ceck Overview

File:Check plan en.jpg

2014-07-27T16:23:57Z

BugBuster: BugBuster uploaded a new version of "File:Check plan en.jpg"

Check Plan

Visitors

2014-06-30T22:38:23Z

BugBuster: /* Forum */

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.2 / 3.2.1
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.2 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-visitors/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible.tpl
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".tpl".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Integrity Check

2014-06-30T12:00:41Z

BugBuster: /* Forum */

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.10 / 3.3.9
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-integrity_check/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php
* .htaccess (from version 3.1.0)

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 00:46, 27 June 2013 (CEST)

Banner

2014-06-30T11:57:15Z

BugBuster: /* Forum */

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
A banner advertisement module with a simple form of weighting. 
In Backend you can see banner view and banner click statistics. (System Menu) 
 
IP-based ReClick blocker was integrated (5 minutes). Forwarding functioned, but isn't counted. 
Similarly, the views within a period not re-counted if the same banner displayed. (10 minutes) 
The amount of time to block the view count can be changed. 
 
By using the module "[[Bot Detection |Bot Detection]]" requests from bots and search engines are not counted. 
 
In the module directory is located in the file '''mod_banner_fe.css''' some CSS sample data. These can be included in the layout or you can import the file and activate this in the layout.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.4.4 / 3.2.0
| Version=from 2.9
| TLVersion=2.6.2 - 2.8.4 (see installations notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/banner.en.html
| TrackerLink=https://github.com/BugBuster1701/banner/issues
| VCSLink=https://github.com/BugBuster1701/banner
| Comment=Version for Contao 3.2 online
}}
[[de:Banner]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/banner/issues Issue Tracker].
 

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/contao-banner/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/banner.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/banner". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Banner is dependent on the modules "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Banner Module Version 1.11.2 ([http://www.contao.org/extension-list/view/banner.10110029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Banner Module Version 1.9.2 ([http://www.contao.org/extension-list/view/banner.10090029.en.html Direct Link])
===TYPOlight 2.6===
Users of TYPOlight 2.6.x, please use Banner Module Version 1.6.5 ([http://www.contao.org/extension-list/view/banner.10060059.en.html Direct Link])
 

=Installation as an update=
An update is identical to the installation. 
'''Notice when updating from < 1.10.0 to the latest version:''' 
The CSS file "mod_banner_fe.css" which is included as an example, the uppercase / lowercase letters changed in a class. 
Anyone who has imported this file or the design itself has to produce, the class ".mod_Banner" must change in ".mod_banner". 

==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Banner_Update_v1_to_v2|'''Banner Update Version 1 to Version 2''']]
 

=Overview=
The Banner Module contains two back end and one front end module. 
In the back end, there are "Banner" and "Banner Statistic", for the front end "Banner".

==Back end==

===Banner===
[[File:Banner_en_backend_banner.jpg|Back end module Banner]]

===Banner Statistic===
[[File:Banner_en_backend_bannerstatistic.jpg|Back end module Banner Statistic]]

==Front end==

===Display a banner===
[[File:Banner_en_frontend_one_banner.jpg|Front end module Banner]]
# Module Headline
# Banner Image
# Banner Comment
# Banner Name

More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".

===Display all Banner===
With 'all Banner' is meant here, all banners in the selected category. 
[[File:Banner_en_frontend_all_banner.jpg|Front end all banner|left]]
In this example, 3 banners have been defined, 
* Graphic Banner
* Flash Banner
* Text Banner 
More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".
 

=Using=
The first one creates a new banner category via the menu item "banner". In this then the banners.
Then, create a front end module and build it into the layout of the page.
Here are the steps, each with the default values. [[Banner#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Banner'. In the main area click on the button 'New category'.
[[File:Banner_en_backend_category_new.jpg|New Banner Category]]

There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create the banners==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New Banner' and then the arrow icon, or click the plus in the head of the category: 
[[File:Banner_en_backend_banner_new.jpg|New Banner]]

First they must select the banner source:
* internal Banner (Graphic / Flash files is stored on server)
* external Banner (Graphic / Flash files are integrated via URL)
* Text Banner
 
After selecting it appear the appropriate form fields.

===Graphic Banners===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template appears below the banner graphic.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the banner graphic. The input must include "http://".
#* Optional field.
#* Without a URL, the banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
#* '''CAUTION''': Animated GIFs are for size definitions through the GD recalculation unfortunately to still images.
# Banner Comment
#* The first line will be installed and displayed as a "title" tag in the HTML source code if you move the cursor over the banner graphic.
# Published
#* If this option is not selected, this banner is not displayed.

===Flash Banner===
# Banner Name
#* The banner name will be displayed only in the Banner overview.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the Flash Banner. The input must include "http://".
#* Optional field.
#* Without a URL, the Flash Banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
# Banner Comment
#* Input is not necessary, is not used in the front end
# Published
#* If this option is not selected, this banner is not displayed.

A flash fallback to an image file is available, see the section [[Banner#Flash_Fallback_Image|Technical Details]]

===Text Banner===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template as a headline that is linked simultaneously with the target URL.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking. The input must include "http://".
#* Optional field.
#* Without a URL, the Text Banner will be displayed without a link.
#* in provided template only the domain is shown as a short form. (Third row, see picture above)
# Banner Comment
#* This is the text line. (Second row, see picture above)
# Published
#* If this option is not selected, this banner is not displayed.

==Front end module==
A new front-end module is create with: 
* Layout -> Themes -> Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
Be sure to '''first enter the title''', then selecting for module type:''Miscellaneous -> Banner''.
Now the form fields change accordingly. 
In 'Banner Categories' select the previously created category, then 'Save and Close'. 
 
Now, the front end module must be included in the layout: 
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)
Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
For the first tests you should copy the provided file mod_banner_fe.css from /system/modules/banner to /tl_files . Then import them over the back end and activate it in the layout.

=Technical Details=
Technical details are inside of the category, in the banner denifinition and in the constructed front end module feasible / adjustable.

==Technical Details in the Category Definition==
===Number of banners===
* Show all banners
If you choose this option, all active banners will be showed in front end. 
In addition, you can choose:
* Limiting the number of banners
Here, the number can be limited. Default is 0: show all banners, otherwise maximum number of banners that will be showed.
* Random order
If you choose this option, the banners will shown in a random order.

==Technical Details in the Banner Definition==
===Flash Fallback Image===
If a browser does not support Flash or JavaScript is disabled, an image can be displayed instead (since version 2.2.0). At a local (internal) flash file, in the same path is searched for an image file with the same name but with the ending jpg, png or gif. 
Example: for "myflash.swf" would be a fallback image: "myflash.jpg" 
Was found a replacement image, the image is displayed. If necessary, the image is converted to the dimensions of the flash file.

===Display limitation by Start / Stop dates and times===
* Show from
** If you enter a date and time value here the current banner will not be shown on the website before this moment.
* Show until
** If you enter a date and time value here the current banner will not be shown on the website after this moment.

===Limiting the number of Views and Clicks===
* Limiting the number of Views and Clicks
If you select this option, you can define a maximum number of views and/or maximum number of clicks.
* Limiting the number of Views
** By entering a number, the current banner is no longer displayed after this number of views. The "Limiting the number of Views and Clicks" has enabled it to stay.
* Limiting the number of Clicks
** By entering a number, the current banner is no longer displayed after this number of clicks. The "Limiting the number of Views and Clicks" has enabled it to stay.

===Filter Domain===
If you enter a domain name, this banner is used only for this domain.If you leave the field empty, this banner is used for all domains. Example: '''yourdomain.com''' 
 
The banner will be displayed, if matches the domain. But also in partial match starting from the right. So also with access via "'''sub.yourdomain.com'''" .An entry in "Site structure" - "Domain Name" is not required for the filtering.

==Technical Details in the Front end Module Definition==

===First banner for new visitor===
For each new visitor, at first is displayed the first published banner in the category. The choice is then returned to random mode. Thus, a kind of recognition can be achieved.

===Templates===
Each module can be assigned its own Template. Two different templates are included. 
* mod_banner_list_all
** All fields are included.
* mod_banner_list_min
** The headline and name were removed. It will only display the banner itself.

Both templates also support text banners. 
For own Templates, the template files must start with "mod_banner_list_" and end with ".tpl".
Example: "mod_banner_list_special.tpl"

{{Note|In Banner Version 1.x this selection is located in the banner category.}}
 

===Prevention of counting their own requests===
You can set a custom UserAgent String in your browser and in the banner modul configuration.
 
Via:
* Layout -> Themes -> Modules -> Modul Name (Contao 2.9 and newer)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the applied banners module in the new field "No counting for this HTTP_USER_AGENT partial identifier" , a string is entered, it should be unique. 
Example: CTISOK 
Save it. 
Several strings are also possible, then enter them separated by commas. 
so you can change the User Agent String of Mozilla Firefox: 
 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER
# Type '''general.useragent.extra.firefox''' in the Filter bar
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.6.3 CTISOK".

 
You can check your new User Agent String , type '''about:''' in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]

=Specific feature=
==Bot Detection off==
Who wants to count the hits from bots and search engines on the banners can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_bot_check'] = false;
</source>

 

==Change Banner Block Time for Views==
As written in the beginning, when a banner is displayed multiple times within 10 minutes (C3: 5 minutes), this banner is only counted once. 
With an entry in the localconfig.php can change that. The values be there in minutes, the number must be> 0, otherwise will be automatically taken back to the default value (10).
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after ### INSTALL SCRIPT STOP ### ) causes a change to 5 minutes: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_block_time'] = 5;
</source>
 

==Exception: No active banners defined and no default banner defined==
If, in this case, "Hide if empty" is not activated, until now was an empty image tag generated, what was presented by the IE as Broken Image. From version 1.11.2 now a DIV tag with class = "banner_empty" is generated:
<source lang="html4strict">
<div class="mod_banner">
<div class="banner_empty">

</div>
</div>
</source>
With CSS can now be reached that is maintained (in this example) the amount and thus the layout of the site will not change:
<source lang="css">
.mod_banner .banner_empty {
height:90px;
}
</source>
The resultant text can be overridden to enforce in langconfig.php, here is an example of an empty text:
<source lang="php">
$GLOBALS['TL_LANG']['MSC']['tl_banner']['noBanner'] = '';
</source>

 
==Special case: Multiple Banner modules on one page==
Here are some hints and tips for well-known application scenarios and their characteristics.

===One category - Two front end modules on one page===
In the current version it is possible to display all the banners from one category. 
The old version's multiple banners on a Web page was to be able to create multiple front end modules and integrating them into the website. The module is prevented that a banner will not appear more than once. 
Well, it was assumed that all displayed below each other, so it made sense, the module title to display only once. 
If you want to leave now for all the title's banner front-end modules, because they are distributed on the page, must be made for this purpose a small modification to the template. Create a copy on the back end of the template "mod_banner_list_all" and renames it here, for example, in "mod_banner_list_special.tpl. 
There, now you change the third line as follows: 
Original: 
<source lang="php">
<?php if (($this->headline) && (!$this->headline_stop)): ?>
</source>
Special: 
<source lang="php">
<?php if ($this->headline) : ?>
</source>
Now edit the banner front end modules and select the new template. 
Done.
 
This is also true for more than two front end modules.
 

===Two categories - Two front end modules on one page===
In this case, each front end module its own category. Again, only on the first module, the heading will appear for the same reason as in the previous section. 
If you want to display in this scenario all module headers, the solution is the same. 
This is also true for more than two front end modules.
 
 

----
--[[User:BugBuster|BugBuster]] 16:27, 10 July 2011 (CEST)

Bot Detection

2014-06-28T19:54:35Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:Bot_detection.jpg|right|No Bots!]]Bot Detection is a helper class for other extensions (Frontend) the need to detect whether the access is human or machine. 
(Detection of Search Engines, Spider, Crawler, Bots, Harvester, ...)
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.7.2 / 3.3.0
| Version=from 2.9
| TLVersion=2.8
| ERLink=http://www.contao.org/extension-list/view/botdetection.en.html
| TrackerLink=https://github.com/BugBuster1701/botdetection/issues
| DonateLink=Cappuccino
| Comment=Now on GitHub
}}

[[de:Bot_Detection]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/botdetection/issues Issue Tracker].

=Translations=
Translations can be performed on [https://www.transifex.com/projects/p/botdetection/ Transifex]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/botdetection.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/botdetection". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations )

=Using=
The module Bot Detection provides three methods for detection. 
A reliable detection is not possible. 
It is to use two methods to detect this: 
* User Agent
* IP adress (IPv4, IPv6 from version 1.4.0)

The modul includes a method for the agent [[Bot_Detection#Method_BD_CheckBotAgent|BD_CheckBotAgent]] and one for the IP detection [[Bot_Detection#Method_BD_CheckBotIP|BD_CheckBotIP]]. 
These two methods return only "true" or "false" and are only a rough search on strings and substrings to identify the most important bots. 
Another method [[Bot_Detection#Method_BD_CheckBotAgentAdvanced|BD_CheckBotAgentAdvanced]] comes with an external configuration file for the user agent detection. As a result, it returns the short name of the bots or "false".

==Method BD_CheckBotAgent==
The method BD_CheckBotAgent "searches in two steps to be completed as quickly as possible. 
Step 1 searches for substrings that appear in most search engines / bots in the name: 
<source lang="text">
'bot'
'spider'
'spyder'
'crawl'
'slurp'
'robo'
'yahoo'
</source>

Step 2 then looks for other strings that usually follow the name of the search engine, such as: 
<source lang="text">
'altavista'
'archiver'
'inktomi'
'twiceler'
...
</source>
The result is "true" or "false". ("true" = search engine / bot found)

==Method BD_CheckBotIP==
The bot from Google, MSN / Bing looking sometimes with the user agent from a browser. 
To uncover these "undercover" search engines, you must be filtered by IP address. 
 
There is also configuration files in the ''config'' directory of the module: '''''bot-ip-list.txt''''' and '''''bot-ip-list-ipv6.txt''''' 
Current content knows an IP address of a spider from Israel as well as network addresses for Google and MSN / Bing. 
Additional IP addresses or networks can be entered in this file, but they are not then upgrade secure. 
Therefore, it is better to post them in the localconfig.php as follows: 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.1.2';
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.0.0/24';
</source>
For IPv6 on this way:
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Method BD_CheckBotAgentAdvanced==
The method BD_CheckBotAgentAdvanced "is controlled by an external configuration file to detect the user agent. 
The result is the short name of the bots or "false". 
 
The external configuration file is generated from known user agent information from search engines / bots and regularly renewed. 
'''Note''' 
This external DB differentiates between different types of search engines from a manufacturer. 
For example, the return is not "Google", but "Googlebot" or "Googlebot-Image" or "Googlebot-Mobile" and so on, depending on what was recognized. 
These multiple name of a search engine are also available from other producers such as MSN, Yahoo, and so on.
 
Own or unknown user agent identifiers can be entered in the file '''/system/config/localconfig.php''': 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("unitbot","UniBot from FHTW");
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("myprivat","My privat bot");
</source>
The parameters are: short name in lower case, description.

=Demo Modules=
Module Bot Detection has 2 frontend demo modules as a demo for the implementation in your own modules. 
The using in the demo class is made by import.
<source lang="php">
$this->import('ModuleBotDetection');
</source>

==Frontend Demo 1==
Demo 1 tests with all three methods, the current IP and User Agent identifier and displays the results. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_1.html Demo 1].

==Frontend Demo 2==
Demo 2 makes available a form to check whether a user agent identifier from the module would be recognized as a bot. 
These are called the two agent methods and displays the result. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_2.html Demo 2].
 

----
--[[User:BugBuster|BugBuster]] 21:42, 1 July 2011 (CEST)

Integrity Check

2014-06-07T23:16:51Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.10 / 3.3.9
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php
* .htaccess (from version 3.1.0)

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 00:46, 27 June 2013 (CEST)

Integrity Check

2014-06-07T23:15:02Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.10 / 3.3.2
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php
* .htaccess (from version 3.1.0)

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 00:46, 27 June 2013 (CEST)

Bot Detection

2013-12-08T23:09:45Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:Bot_detection.jpg|right|No Bots!]]Bot Detection is a helper class for other extensions (Frontend) the need to detect whether the access is human or machine. 
(Detection of Search Engines, Spider, Crawler, Bots, Harvester, ...)
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.7.2 / 3.2.1
| Version=from 2.9
| TLVersion=2.8
| ERLink=http://www.contao.org/extension-list/view/botdetection.en.html
| TrackerLink=https://github.com/BugBuster1701/botdetection/issues
| DonateLink=Cappuccino
| Comment=Now on GitHub
}}

[[de:Bot_Detection]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/botdetection/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/botdetection.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/botdetection". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations )

=Using=
The module Bot Detection provides three methods for detection. 
A reliable detection is not possible. 
It is to use two methods to detect this: 
* User Agent
* IP adress (IPv4, IPv6 from version 1.4.0)

The modul includes a method for the agent [[Bot_Detection#Method_BD_CheckBotAgent|BD_CheckBotAgent]] and one for the IP detection [[Bot_Detection#Method_BD_CheckBotIP|BD_CheckBotIP]]. 
These two methods return only "true" or "false" and are only a rough search on strings and substrings to identify the most important bots. 
Another method [[Bot_Detection#Method_BD_CheckBotAgentAdvanced|BD_CheckBotAgentAdvanced]] comes with an external configuration file for the user agent detection. As a result, it returns the short name of the bots or "false".

==Method BD_CheckBotAgent==
The method BD_CheckBotAgent "searches in two steps to be completed as quickly as possible. 
Step 1 searches for substrings that appear in most search engines / bots in the name: 
<source lang="text">
'bot'
'spider'
'spyder'
'crawl'
'slurp'
'robo'
'yahoo'
</source>

Step 2 then looks for other strings that usually follow the name of the search engine, such as: 
<source lang="text">
'altavista'
'archiver'
'inktomi'
'twiceler'
...
</source>
The result is "true" or "false". ("true" = search engine / bot found)

==Method BD_CheckBotIP==
The bot from Google, MSN / Bing looking sometimes with the user agent from a browser. 
To uncover these "undercover" search engines, you must be filtered by IP address. 
 
There is also configuration files in the ''config'' directory of the module: '''''bot-ip-list.txt''''' and '''''bot-ip-list-ipv6.txt''''' 
Current content knows an IP address of a spider from Israel as well as network addresses for Google and MSN / Bing. 
Additional IP addresses or networks can be entered in this file, but they are not then upgrade secure. 
Therefore, it is better to post them in the localconfig.php as follows: 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.1.2';
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.0.0/24';
</source>
For IPv6 on this way:
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Method BD_CheckBotAgentAdvanced==
The method BD_CheckBotAgentAdvanced "is controlled by an external configuration file to detect the user agent. 
The result is the short name of the bots or "false". 
 
The external configuration file is generated from known user agent information from search engines / bots and regularly renewed. 
'''Note''' 
This external DB differentiates between different types of search engines from a manufacturer. 
For example, the return is not "Google", but "Googlebot" or "Googlebot-Image" or "Googlebot-Mobile" and so on, depending on what was recognized. 
These multiple name of a search engine are also available from other producers such as MSN, Yahoo, and so on.
 
Own or unknown user agent identifiers can be entered in the file '''/system/config/localconfig.php''': 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("unitbot","UniBot from FHTW");
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("myprivat","My privat bot");
</source>
The parameters are: short name in lower case, description.

=Demo Modules=
Module Bot Detection has 2 frontend demo modules as a demo for the implementation in your own modules. 
The using in the demo class is made by import.
<source lang="php">
$this->import('ModuleBotDetection');
</source>

==Frontend Demo 1==
Demo 1 tests with all three methods, the current IP and User Agent identifier and displays the results. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_1.html Demo 1].

==Frontend Demo 2==
Demo 2 makes available a form to check whether a user agent identifier from the module would be recognized as a bot. 
These are called the two agent methods and displays the result. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_2.html Demo 2].
 

----
--[[User:BugBuster|BugBuster]] 21:42, 1 July 2011 (CEST)

BOM Checker

2013-12-08T23:06:34Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.2.0 / 3.2.0
| Version=ab 2.9
| TLVersion=2.8 (not tested, but should work)
| ERLink=http://http://www.contao.org/en/extension-list/view/bom_checker.html
| TrackerLink=https://github.com/BugBuster1701/bom_checker/issues
| VCSLink=https://github.com/BugBuster1701/bom_checker
| DonateLink=Cappuccino
| Comment=Version for Contao 3.2 online
}}
[[de:BOM_Checker]]
[[Category:Extensions]]

[[File:Bom_checker_er.jpg|right|thumb|BOM_Checker]]The BOM-Checker is a backend helper module for developers. 
In the backend, there is a new menu item "Developer tools", including the point will "BOM Checker" to be found. 
 
'''The module requires the Standard PHP Library (SPL), this is an integral part of PHP 5, if not disabled.'''
 

=BOM ?=
PHP5 can't correctly interpret Files with a BOM. (Byte Order Mark, 3 bytes at the beginning of a file)

----
--[[Benutzer:BugBuster|BugBuster]] 00:53, 8. Mai 2011 (CEST)

Backend User Online

2013-12-08T23:04:26Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
Shows in then back end the online status of the back end and front end user in the user / member overview.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.2.0 / 3.1.0
| Version=from 2.9
| TLVersion=2.7.2 - 2.8.4
| ERLink=http://http://contao.org/en/extension-list/view/backend_user_online.en.html
| TrackerLink=https://github.com/BugBuster1701/backend_user_online/issues
}}

[[de:Backend_User_Online]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/backend_user_online/issues Issue Tracker]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/backend_user_online.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/backend_user_online". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

=Using=
It expands the area of "Account manager" - "Members" and "Account manager" - "Users". 
For members it looks like this: 
[[File:Be_user_online_en_member.jpg|Backend User Online - Members]]

It represents the green eye "Online", the gray eyes "Offline".
 
For users it looks like this: 
[[File:Be_user_online_en_user.jpg|Backend User Online - Users]]

When you sort, as seen in the pictures, to "Last Login", this information can also be seen.
 

----
--[[User:BugBuster|BugBuster]] 18:54, 10 November 2012 (CET)

Banner

2013-12-08T23:01:23Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
A banner advertisement module with a simple form of weighting. 
In Backend you can see banner view and banner click statistics. (System Menu) 
 
IP-based ReClick blocker was integrated (5 minutes). Forwarding functioned, but isn't counted. 
Similarly, the views within a period not re-counted if the same banner displayed. (10 minutes) 
The amount of time to block the view count can be changed. 
 
By using the module "[[Bot Detection |Bot Detection]]" requests from bots and search engines are not counted. 
 
In the module directory is located in the file '''mod_banner_fe.css''' some CSS sample data. These can be included in the layout or you can import the file and activate this in the layout.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.4.4 / 3.2.0
| Version=from 2.9
| TLVersion=2.6.2 - 2.8.4 (see installations notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/banner.en.html
| TrackerLink=https://github.com/BugBuster1701/banner/issues
| VCSLink=https://github.com/BugBuster1701/banner
| Comment=Version for Contao 3.2 online
}}
[[de:Banner]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/banner/issues Issue Tracker].
 

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/banner.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/banner". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Banner is dependent on the modules "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Banner Module Version 1.11.2 ([http://www.contao.org/extension-list/view/banner.10110029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Banner Module Version 1.9.2 ([http://www.contao.org/extension-list/view/banner.10090029.en.html Direct Link])
===TYPOlight 2.6===
Users of TYPOlight 2.6.x, please use Banner Module Version 1.6.5 ([http://www.contao.org/extension-list/view/banner.10060059.en.html Direct Link])
 

=Installation as an update=
An update is identical to the installation. 
'''Notice when updating from < 1.10.0 to the latest version:''' 
The CSS file "mod_banner_fe.css" which is included as an example, the uppercase / lowercase letters changed in a class. 
Anyone who has imported this file or the design itself has to produce, the class ".mod_Banner" must change in ".mod_banner". 

==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Banner_Update_v1_to_v2|'''Banner Update Version 1 to Version 2''']]
 

=Overview=
The Banner Module contains two back end and one front end module. 
In the back end, there are "Banner" and "Banner Statistic", for the front end "Banner".

==Back end==

===Banner===
[[File:Banner_en_backend_banner.jpg|Back end module Banner]]

===Banner Statistic===
[[File:Banner_en_backend_bannerstatistic.jpg|Back end module Banner Statistic]]

==Front end==

===Display a banner===
[[File:Banner_en_frontend_one_banner.jpg|Front end module Banner]]
# Module Headline
# Banner Image
# Banner Comment
# Banner Name

More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".

===Display all Banner===
With 'all Banner' is meant here, all banners in the selected category. 
[[File:Banner_en_frontend_all_banner.jpg|Front end all banner|left]]
In this example, 3 banners have been defined, 
* Graphic Banner
* Flash Banner
* Text Banner 
More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".
 

=Using=
The first one creates a new banner category via the menu item "banner". In this then the banners.
Then, create a front end module and build it into the layout of the page.
Here are the steps, each with the default values. [[Banner#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Banner'. In the main area click on the button 'New category'.
[[File:Banner_en_backend_category_new.jpg|New Banner Category]]

There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create the banners==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New Banner' and then the arrow icon, or click the plus in the head of the category: 
[[File:Banner_en_backend_banner_new.jpg|New Banner]]

First they must select the banner source:
* internal Banner (Graphic / Flash files is stored on server)
* external Banner (Graphic / Flash files are integrated via URL)
* Text Banner
 
After selecting it appear the appropriate form fields.

===Graphic Banners===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template appears below the banner graphic.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the banner graphic. The input must include "http://".
#* Optional field.
#* Without a URL, the banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
#* '''CAUTION''': Animated GIFs are for size definitions through the GD recalculation unfortunately to still images.
# Banner Comment
#* The first line will be installed and displayed as a "title" tag in the HTML source code if you move the cursor over the banner graphic.
# Published
#* If this option is not selected, this banner is not displayed.

===Flash Banner===
# Banner Name
#* The banner name will be displayed only in the Banner overview.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the Flash Banner. The input must include "http://".
#* Optional field.
#* Without a URL, the Flash Banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
# Banner Comment
#* Input is not necessary, is not used in the front end
# Published
#* If this option is not selected, this banner is not displayed.

A flash fallback to an image file is available, see the section [[Banner#Flash_Fallback_Image|Technical Details]]

===Text Banner===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template as a headline that is linked simultaneously with the target URL.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking. The input must include "http://".
#* Optional field.
#* Without a URL, the Text Banner will be displayed without a link.
#* in provided template only the domain is shown as a short form. (Third row, see picture above)
# Banner Comment
#* This is the text line. (Second row, see picture above)
# Published
#* If this option is not selected, this banner is not displayed.

==Front end module==
A new front-end module is create with: 
* Layout -> Themes -> Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
Be sure to '''first enter the title''', then selecting for module type:''Miscellaneous -> Banner''.
Now the form fields change accordingly. 
In 'Banner Categories' select the previously created category, then 'Save and Close'. 
 
Now, the front end module must be included in the layout: 
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)
Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
For the first tests you should copy the provided file mod_banner_fe.css from /system/modules/banner to /tl_files . Then import them over the back end and activate it in the layout.

=Technical Details=
Technical details are inside of the category, in the banner denifinition and in the constructed front end module feasible / adjustable.

==Technical Details in the Category Definition==
===Number of banners===
* Show all banners
If you choose this option, all active banners will be showed in front end. 
In addition, you can choose:
* Limiting the number of banners
Here, the number can be limited. Default is 0: show all banners, otherwise maximum number of banners that will be showed.
* Random order
If you choose this option, the banners will shown in a random order.

==Technical Details in the Banner Definition==
===Flash Fallback Image===
If a browser does not support Flash or JavaScript is disabled, an image can be displayed instead (since version 2.2.0). At a local (internal) flash file, in the same path is searched for an image file with the same name but with the ending jpg, png or gif. 
Example: for "myflash.swf" would be a fallback image: "myflash.jpg" 
Was found a replacement image, the image is displayed. If necessary, the image is converted to the dimensions of the flash file.

===Display limitation by Start / Stop dates and times===
* Show from
** If you enter a date and time value here the current banner will not be shown on the website before this moment.
* Show until
** If you enter a date and time value here the current banner will not be shown on the website after this moment.

===Limiting the number of Views and Clicks===
* Limiting the number of Views and Clicks
If you select this option, you can define a maximum number of views and/or maximum number of clicks.
* Limiting the number of Views
** By entering a number, the current banner is no longer displayed after this number of views. The "Limiting the number of Views and Clicks" has enabled it to stay.
* Limiting the number of Clicks
** By entering a number, the current banner is no longer displayed after this number of clicks. The "Limiting the number of Views and Clicks" has enabled it to stay.

===Filter Domain===
If you enter a domain name, this banner is used only for this domain.If you leave the field empty, this banner is used for all domains. Example: '''yourdomain.com''' 
 
The banner will be displayed, if matches the domain. But also in partial match starting from the right. So also with access via "'''sub.yourdomain.com'''" .An entry in "Site structure" - "Domain Name" is not required for the filtering.

==Technical Details in the Front end Module Definition==

===First banner for new visitor===
For each new visitor, at first is displayed the first published banner in the category. The choice is then returned to random mode. Thus, a kind of recognition can be achieved.

===Templates===
Each module can be assigned its own Template. Two different templates are included. 
* mod_banner_list_all
** All fields are included.
* mod_banner_list_min
** The headline and name were removed. It will only display the banner itself.

Both templates also support text banners. 
For own Templates, the template files must start with "mod_banner_list_" and end with ".tpl".
Example: "mod_banner_list_special.tpl"

{{Note|In Banner Version 1.x this selection is located in the banner category.}}
 

===Prevention of counting their own requests===
You can set a custom UserAgent String in your browser and in the banner modul configuration.
 
Via:
* Layout -> Themes -> Modules -> Modul Name (Contao 2.9 and newer)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the applied banners module in the new field "No counting for this HTTP_USER_AGENT partial identifier" , a string is entered, it should be unique. 
Example: CTISOK 
Save it. 
Several strings are also possible, then enter them separated by commas. 
so you can change the User Agent String of Mozilla Firefox: 
 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER
# Type '''general.useragent.extra.firefox''' in the Filter bar
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.6.3 CTISOK".

 
You can check your new User Agent String , type '''about:''' in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]

=Specific feature=
==Bot Detection off==
Who wants to count the hits from bots and search engines on the banners can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_bot_check'] = false;
</source>

 

==Change Banner Block Time for Views==
As written in the beginning, when a banner is displayed multiple times within 10 minutes (C3: 5 minutes), this banner is only counted once. 
With an entry in the localconfig.php can change that. The values be there in minutes, the number must be> 0, otherwise will be automatically taken back to the default value (10).
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after ### INSTALL SCRIPT STOP ### ) causes a change to 5 minutes: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_block_time'] = 5;
</source>
 

==Exception: No active banners defined and no default banner defined==
If, in this case, "Hide if empty" is not activated, until now was an empty image tag generated, what was presented by the IE as Broken Image. From version 1.11.2 now a DIV tag with class = "banner_empty" is generated:
<source lang="html4strict">
<div class="mod_banner">
<div class="banner_empty">

</div>
</div>
</source>
With CSS can now be reached that is maintained (in this example) the amount and thus the layout of the site will not change:
<source lang="css">
.mod_banner .banner_empty {
height:90px;
}
</source>
The resultant text can be overridden to enforce in langconfig.php, here is an example of an empty text:
<source lang="php">
$GLOBALS['TL_LANG']['MSC']['tl_banner']['noBanner'] = '';
</source>

 
==Special case: Multiple Banner modules on one page==
Here are some hints and tips for well-known application scenarios and their characteristics.

===One category - Two front end modules on one page===
In the current version it is possible to display all the banners from one category. 
The old version's multiple banners on a Web page was to be able to create multiple front end modules and integrating them into the website. The module is prevented that a banner will not appear more than once. 
Well, it was assumed that all displayed below each other, so it made sense, the module title to display only once. 
If you want to leave now for all the title's banner front-end modules, because they are distributed on the page, must be made for this purpose a small modification to the template. Create a copy on the back end of the template "mod_banner_list_all" and renames it here, for example, in "mod_banner_list_special.tpl. 
There, now you change the third line as follows: 
Original: 
<source lang="php">
<?php if (($this->headline) && (!$this->headline_stop)): ?>
</source>
Special: 
<source lang="php">
<?php if ($this->headline) : ?>
</source>
Now edit the banner front end modules and select the new template. 
Done.
 
This is also true for more than two front end modules.
 

===Two categories - Two front end modules on one page===
In this case, each front end module its own category. Again, only on the first module, the heading will appear for the same reason as in the previous section. 
If you want to display in this scenario all module headers, the solution is the same. 
This is also true for more than two front end modules.
 
 

----
--[[User:BugBuster|BugBuster]] 16:27, 10 July 2011 (CEST)

Visitors

2013-11-07T22:55:42Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.2 / 3.2.1
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.2 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible.tpl
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".tpl".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Replace Language

2013-10-02T22:33:29Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Replace_language_en.jpg|right|Replace Language]]"Replace Language" replaces the language requested by search engines (over HTTP_ACCEPT_LANGUAGE) in a given language.

The aim is it, for a multilingual website in Contao, to provide the search engine the result of the request in a fixed language. Reason for the development was, that search engine query often with the English language and the German pages (e.g. over "change language" links) only with a lower classification have been evaluated.
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.0.0 / 3.0.0
| Version=from 2.9 / 3.1.0
| TLVersion=2.8.0 - 2.8.4
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=https://contao.org/en/extension-list/view/replacelanguage.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/replacelanguage/issues
| Comment=Version for Contao 3.1 online
}}
[[de:Replace_Language]]
[[Category:Extensions]]

=Forum=
Questions about the "Replace Language" module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/replacelanguage/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [https://contao.org/en/extension-list/view/replacelanguage.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/replacelanguage". 
'''''The module Replace Language is dependent on the module "[[Bot Detection|Bot Detection]]". It must therefore be installed with manual installation.'''''

=Using=
In the back end, the module is enabled in "Settings", and the language is defined there.

Bot Detection

2013-09-08T22:02:28Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:Bot_detection.jpg|right|No Bots!]]Bot Detection is a helper class for other extensions (Frontend) the need to detect whether the access is human or machine. 
(Detection of Search Engines, Spider, Crawler, Bots, Harvester, ...)
{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.7.1 / 3.0.1
| Version=from 2.9
| TLVersion=2.8
| ERLink=http://www.contao.org/extension-list/view/botdetection.en.html
| TrackerLink=https://github.com/BugBuster1701/botdetection/issues
| DonateLink=Cappuccino
| Comment=Now on GitHub
}}

[[de:Bot_Detection]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/botdetection/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/botdetection.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/botdetection". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations )

=Using=
The module Bot Detection provides three methods for detection. 
A reliable detection is not possible. 
It is to use two methods to detect this: 
* User Agent
* IP adress (IPv4, IPv6 from version 1.4.0)

The modul includes a method for the agent [[Bot_Detection#Method_BD_CheckBotAgent|BD_CheckBotAgent]] and one for the IP detection [[Bot_Detection#Method_BD_CheckBotIP|BD_CheckBotIP]]. 
These two methods return only "true" or "false" and are only a rough search on strings and substrings to identify the most important bots. 
Another method [[Bot_Detection#Method_BD_CheckBotAgentAdvanced|BD_CheckBotAgentAdvanced]] comes with an external configuration file for the user agent detection. As a result, it returns the short name of the bots or "false".

==Method BD_CheckBotAgent==
The method BD_CheckBotAgent "searches in two steps to be completed as quickly as possible. 
Step 1 searches for substrings that appear in most search engines / bots in the name: 
<source lang="text">
'bot'
'spider'
'spyder'
'crawl'
'slurp'
'robo'
'yahoo'
</source>

Step 2 then looks for other strings that usually follow the name of the search engine, such as: 
<source lang="text">
'altavista'
'archiver'
'inktomi'
'twiceler'
...
</source>
The result is "true" or "false". ("true" = search engine / bot found)

==Method BD_CheckBotIP==
The bot from Google, MSN / Bing looking sometimes with the user agent from a browser. 
To uncover these "undercover" search engines, you must be filtered by IP address. 
 
There is also configuration files in the ''config'' directory of the module: '''''bot-ip-list.txt''''' and '''''bot-ip-list-ipv6.txt''''' 
Current content knows an IP address of a spider from Israel as well as network addresses for Google and MSN / Bing. 
Additional IP addresses or networks can be entered in this file, but they are not then upgrade secure. 
Therefore, it is better to post them in the localconfig.php as follows: 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.1.2';
$GLOBALS['BOTDETECTION']['BOT_IP'][] = '192.168.0.0/24';
</source>
For IPv6 on this way:
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['BOTDETECTION']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Method BD_CheckBotAgentAdvanced==
The method BD_CheckBotAgentAdvanced "is controlled by an external configuration file to detect the user agent. 
The result is the short name of the bots or "false". 
 
The external configuration file is generated from known user agent information from search engines / bots and regularly renewed. 
'''Note''' 
This external DB differentiates between different types of search engines from a manufacturer. 
For example, the return is not "Google", but "Googlebot" or "Googlebot-Image" or "Googlebot-Mobile" and so on, depending on what was recognized. 
These multiple name of a search engine are also available from other producers such as MSN, Yahoo, and so on.
 
Own or unknown user agent identifiers can be entered in the file '''/system/config/localconfig.php''': 
<source lang="php">
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("unitbot","UniBot from FHTW");
$GLOBALS['BOTDETECTION']['BOT_AGENT'][] = array("myprivat","My privat bot");
</source>
The parameters are: short name in lower case, description.

=Demo Modules=
Module Bot Detection has 2 frontend demo modules as a demo for the implementation in your own modules. 
The using in the demo class is made by import.
<source lang="php">
$this->import('ModuleBotDetection');
</source>

==Frontend Demo 1==
Demo 1 tests with all three methods, the current IP and User Agent identifier and displays the results. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_1.html Demo 1].

==Frontend Demo 2==
Demo 2 makes available a form to check whether a user agent identifier from the module would be recognized as a bot. 
These are called the two agent methods and displays the result. 
See example on the developer website - [http://www.contao.glen-langer.de/BD_Frontend_Demo_2.html Demo 2].
 

----
--[[User:BugBuster|BugBuster]] 21:42, 1 July 2011 (CEST)

Visitors

2013-09-08T21:58:51Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.2 / 3.1.4
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.0 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible.tpl
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".tpl".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Bot Statistic

2013-08-11T21:27:19Z

BugBuster:

Bot Statistics counts the requests (visits, pages) of the bots. 
To identify the bots, the module is used [[Bot Detection|Bot Detection]] (necessary dependence).

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.glen-langer.de
| ExtVersion=0.5.2 / 3.1.0
| Version=ab 2.10
| TLVersion=no
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=http://www.contao.org/de/extension-list/view/botstatistics.de.html
| DonateLink=
| TrackerLink=https://github.com/BugBuster1701/botstatistics/issues
| Comment=
}}

[[de:Bot_Statistik]]
[[Category:Extensions]]

After installation, create a front end module of type "Bot Statistics" and install this in the layout, best in the footer. The module only returns a HTML comment, and therefore does not affect the layout.

In the backend, there is in "System" the new item "Bot Statistics".

Dlstats

2013-08-10T19:19:55Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Counts the number of file downloads

* Download statistics for the standard content elements Download and Downloads
* Count number of downloads per file plus latest download timestamp
* Optionally log every single download with timestamp, IP and username.
* Insert-Tag for number of downloads in the frontend (from 2.1.0)
* Ignore certain IPs (define itself, from 2.1.0)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.glen-langer.de
| ExtVersion=2.4.1 / 3.4.0
| Version=from 2.9
| TLVersion=2.7.6 - 2.8.4
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=http://www.contao.org/extension-list/view/dlstats.en.html
| TrackerLink=https://github.com/BugBuster1701/dlstats/issues
}}
[[de:dlstats]]
[[Category:Extensions]]

==Installation==
The installation of the module occurs about the extension Repository in back end of Contao. On manual installation, call /contao/install.php - Perform Update Database. 
'''''For manual installation, please note that the module "[[Bot Detection|Bot Detection]]" must be installed.'''''

==Using==
Go to the Contao Settings and switch on the logging, either only counting the number of downloads per file, or optionally also log each download with timestamp and IP. 
'''For dlstats 2.1.x:''' In the settings you can be deactivated the Anonymize IP function, it must be the admin. 
'''From dlstats 2.2.0:''' IP addresses anonymous: "yes/no" is now controlled by Contao itself. 
(System - Settings - Privacy settings - Anonymize IP addresses) 
Use the content element File Download or File Downloads for all downloaded files you want to have counted. 
After downloading a file you will find the statistics under Content - Download Stats.

==Using Insert-Tag==
The Insert-Tag "cache_dlstats::total downloads::..." supports both, the source of the file (relative path + file name), as well as in connection with the article alias and how it generates for ce_download and ce_downloads. Therefore, the use is well used in the templates of the two CEs, see examples. Return is only the number of downloads as a number.
<source lang="php">
{{cache_dlstats::totaldownloads::tl_files/cdc2010.pdf}}
{{cache_dlstats::totaldownloads::CDC_2010.html?file=tl_files/cdc2010.pdf}}

// in ce_download template:
{{cache_dlstats::totaldownloads::<?php echo $this->href; ?>}}

// in ce_downloads template:
{{cache_dlstats::totaldownloads::<?php echo $file['href']; ?>}}
</source>

==Ignore certain IPs==
If any downloads from certain IP addresses should not be counted, this can be defined in the localconfig.php as follows:
<source lang="php">
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.1.2';
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.0.0/24';
//respectively
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Notice==
* Simple links to files will not be counted as downloads!
* If you are logged in the backend, your download is not counted. (from 2.1.0)

----
--[[User:BugBuster|BugBuster]] 20:07, 1 April 2013 (CEST)

Integrity Check

2013-06-26T22:46:47Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.5 / 3.1.2
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 00:46, 27 June 2013 (CEST)

Xing

2013-06-05T19:58:38Z

BugBuster: /* Forum */

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
[[File:Mod_xing_team.tpl.jpg|right|Xing Team]]Normally, you need not a module, because it is just a linked image. 
But my aim was:
*to select the image
*to determine the position
*several of them on one side, or distributed on several domains.
 
First, categories are created, in these categories then the XING profile(s). With the XING-Lister, you can select the category that are used. Each front-end module can be assigned their own template. Three different templates are included. (see "[[Xing#Using|Using]]")
 
Thus, it is then possible, the categories to distribute on several layouts or several domains. Are there more than one profile in a category, all profiles will be shown from this category. Thus it would be e.g. possible to show the profiles of a whole team.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.2.1 / 3.1.0
| Version=from 2.9
| TLVersion=2.7.0 - 2.8.4 (see Installations notes)
| ERLink=http://www.contao.org/extension-list/view/gl_xing.html
| DonateLink=Cappuccino
| TrackerLink=http://dev.typolight-forge.org/projects/xing/issues
| Comment=Version for Contao 3.1 online
}}
[[de:Xing]]
[[Category:Extensions]]

=Forum=
Questions about the Xing module will be answered in forum: 
English: [http://www.contao-community.org/viewforum.php?f=21 Forum] 
German: [http://www.contao-community.de/showthread.php?4225 Forum] 
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/gl_xing/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/gl_xing.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/gl_xing". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use XING module 1.1.1! ([http://www.contao.org/extension-list/view/gl_xing.10010019.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use XING module 1.0.4! ([http://www.contao.org/extension-list/view/gl_xing.10000049.en.html Direct Link])
 

==Xing Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Xing_Update_v1_to_v2|'''Xing Update Version 1 to Version 2''']]
 

=Overview=
The Xing module contains a back end and a front end module. 
In the back end, there are "Xing", for the front end "Xing list".

==Back end==

===Xing===
[[File:Xing_en_backend.jpg|Xing Module Backend]]
 

==Frontend==
For the front end module, a CSS file is included as an example:
*mod_xing_fe.css for a normal, line-by-line output.

===Xing Banner===
The simplest variant, only the linked image: 
[[File:Module_Xing_List.tpl.jpg|Xing Banner]]
 
The more complex variant, several Xing banner of a team, with team name and names of team members. 
[[File:Module_Xing_Team.jpg|Xing Team]]
 

=Using=
First, create a new category. In the category create the Xing profile(s). 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Xing#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Xing'. In the main area click on the button 'New category'. 
[[File:Xing_en_backend_category.jpg|Xing - New category]] 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create Xing Profile==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New profile' and then the arrow icon, or click the plus in the head of the category: 
[[File:Xing_en_backend_profile_new.jpg|Xing - neues Profil]] 
Now, some information are needed:
* XING Profile, e.g.: John_Doe, explanations are provided in the help. (Help Wizard)
* XING Layout , explanations are provided in the help. (Help Wizard)
* activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> (Front end) Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add modules (TYPOlight 2.8.x and older)
 
At first, enter the title, and only then select in "Module type": 'Xing' - 'Xing list'. It changes the form fields. 
In 'Xing Category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, is provided a CSS file for presentation. 
For the first tests you should copy the file mod_xing_fe.css from '''/system/modules/gl_xing''' to '''/tl_files'''. 
Then import them over the back end and activate it in the layout. 

=Technical Details=
Technical details are inside of the category and in the constructed front end module feasible / adjustable.

==Technical Details inside of the category==
===Team Profile===
In the category, you can create multiple Xing profiles. 
Use would be for example an overview of all team members. 
Depending on the template selection in front-end module, the category name is the team name. 
See the next section, as it could look like then.

==Technical Details in the front end module definition==
===XING Template===
Is defined in the category only one Xing profile, the following two templates are useful:
* mod_xing_list, it shows only the linked graphic [[File:Module_Xing_List.tpl.jpg‎|mod_xing_list]]
* mod_xing_list_profile, it shows the linked graphic, including the profile name (underscore is removed) [[File:Module_Xing_Profile.tpl.jpg‎|mod_xing_profile]]

 
If several Xing profiles defined in the category to represent a team, the following two templates are useful:
* mod_xing_list_profile, it displays the graphics linked with each other, each including the profile name (underscore is removed) [[File:Module_Xing_Profile-2.tpl.jpg‎|mod_xing_profile]]
* mod_xing_list_team, as mod_xing_list_profile, in addition displays above the first graphic the team name (category name) [[File:Module_Xing_Team.jpg‎|mod_xing_team]]
 
You can save your own templates in the folder /templates or in the template folder of the used theme. 
Template names must begin with '''''mod_xing_list''''' and must have the suffix '''''.tpl''''' / '''''.xhtml''''' / '''''.html5'''''. ( e.g.: '''''mod_xing_list_club66.xhtml''''' )
 
===Company Template===
For a company profile, XING has a different destination URL. Therefore it was created a custom template.
Please select the template "mod_xing_list_company" for a company profile.

===Show to guests only===
Hide the module if a member is logged in.

===Protect module===
Show the module to certain member groups only.

Xing

2013-06-05T19:57:34Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
[[File:Mod_xing_team.tpl.jpg|right|Xing Team]]Normally, you need not a module, because it is just a linked image. 
But my aim was:
*to select the image
*to determine the position
*several of them on one side, or distributed on several domains.
 
First, categories are created, in these categories then the XING profile(s). With the XING-Lister, you can select the category that are used. Each front-end module can be assigned their own template. Three different templates are included. (see "[[Xing#Using|Using]]")
 
Thus, it is then possible, the categories to distribute on several layouts or several domains. Are there more than one profile in a category, all profiles will be shown from this category. Thus it would be e.g. possible to show the profiles of a whole team.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.2.1 / 3.1.0
| Version=from 2.9
| TLVersion=2.7.0 - 2.8.4 (see Installations notes)
| ERLink=http://www.contao.org/extension-list/view/gl_xing.html
| DonateLink=Cappuccino
| TrackerLink=http://dev.typolight-forge.org/projects/xing/issues
| Comment=Version for Contao 3.1 online
}}
[[de:Xing]]
[[Category:Extensions]]

=Forum=
Questions about the Xing module will be answered in forum: 
English: [http://www.contao-community.org/viewforum.php?f=21 Forum] 
German: [http://www.contao-community.de/showthread.php?4225 Forum] 
 
Errors and requests can be reported in the [http://dev.typolight-forge.org/projects/xing/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/gl_xing.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/gl_xing". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use XING module 1.1.1! ([http://www.contao.org/extension-list/view/gl_xing.10010019.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use XING module 1.0.4! ([http://www.contao.org/extension-list/view/gl_xing.10000049.en.html Direct Link])
 

==Xing Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Xing_Update_v1_to_v2|'''Xing Update Version 1 to Version 2''']]
 

=Overview=
The Xing module contains a back end and a front end module. 
In the back end, there are "Xing", for the front end "Xing list".

==Back end==

===Xing===
[[File:Xing_en_backend.jpg|Xing Module Backend]]
 

==Frontend==
For the front end module, a CSS file is included as an example:
*mod_xing_fe.css for a normal, line-by-line output.

===Xing Banner===
The simplest variant, only the linked image: 
[[File:Module_Xing_List.tpl.jpg|Xing Banner]]
 
The more complex variant, several Xing banner of a team, with team name and names of team members. 
[[File:Module_Xing_Team.jpg|Xing Team]]
 

=Using=
First, create a new category. In the category create the Xing profile(s). 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Xing#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Xing'. In the main area click on the button 'New category'. 
[[File:Xing_en_backend_category.jpg|Xing - New category]] 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create Xing Profile==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New profile' and then the arrow icon, or click the plus in the head of the category: 
[[File:Xing_en_backend_profile_new.jpg|Xing - neues Profil]] 
Now, some information are needed:
* XING Profile, e.g.: John_Doe, explanations are provided in the help. (Help Wizard)
* XING Layout , explanations are provided in the help. (Help Wizard)
* activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> (Front end) Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add modules (TYPOlight 2.8.x and older)
 
At first, enter the title, and only then select in "Module type": 'Xing' - 'Xing list'. It changes the form fields. 
In 'Xing Category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, is provided a CSS file for presentation. 
For the first tests you should copy the file mod_xing_fe.css from '''/system/modules/gl_xing''' to '''/tl_files'''. 
Then import them over the back end and activate it in the layout. 

=Technical Details=
Technical details are inside of the category and in the constructed front end module feasible / adjustable.

==Technical Details inside of the category==
===Team Profile===
In the category, you can create multiple Xing profiles. 
Use would be for example an overview of all team members. 
Depending on the template selection in front-end module, the category name is the team name. 
See the next section, as it could look like then.

==Technical Details in the front end module definition==
===XING Template===
Is defined in the category only one Xing profile, the following two templates are useful:
* mod_xing_list, it shows only the linked graphic [[File:Module_Xing_List.tpl.jpg‎|mod_xing_list]]
* mod_xing_list_profile, it shows the linked graphic, including the profile name (underscore is removed) [[File:Module_Xing_Profile.tpl.jpg‎|mod_xing_profile]]

 
If several Xing profiles defined in the category to represent a team, the following two templates are useful:
* mod_xing_list_profile, it displays the graphics linked with each other, each including the profile name (underscore is removed) [[File:Module_Xing_Profile-2.tpl.jpg‎|mod_xing_profile]]
* mod_xing_list_team, as mod_xing_list_profile, in addition displays above the first graphic the team name (category name) [[File:Module_Xing_Team.jpg‎|mod_xing_team]]
 
You can save your own templates in the folder /templates or in the template folder of the used theme. 
Template names must begin with '''''mod_xing_list''''' and must have the suffix '''''.tpl''''' / '''''.xhtml''''' / '''''.html5'''''. ( e.g.: '''''mod_xing_list_club66.xhtml''''' )
 
===Company Template===
For a company profile, XING has a different destination URL. Therefore it was created a custom template.
Please select the template "mod_xing_list_company" for a company profile.

===Show to guests only===
Hide the module if a member is logged in.

===Protect module===
Show the module to certain member groups only.

Integrity Check

2013-05-21T23:24:35Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.5 / 3.1.1
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 20:06, 1 April 2013 (CEST)

Banner

2013-04-28T15:02:51Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 
A banner advertisement module with a simple form of weighting. 
In Backend you can see banner view and banner click statistics. (System Menu) 
 
IP-based ReClick blocker was integrated (5 minutes). Forwarding functioned, but isn't counted. 
Similarly, the views within a period not re-counted if the same banner displayed. (10 minutes) 
The amount of time to block the view count can be changed. 
 
By using the module "[[Bot Detection |Bot Detection]]" requests from bots and search engines are not counted. 
 
In the module directory is located in the file '''mod_banner_fe.css''' some CSS sample data. These can be included in the layout or you can import the file and activate this in the layout.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.4.4 / 3.0.0
| Version=from 2.9
| TLVersion=2.6.2 - 2.8.4 (see installations notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/banner.en.html
| TrackerLink=https://github.com/BugBuster1701/banner/issues
| VCSLink=https://github.com/BugBuster1701/banner
| Comment=Version for Contao 3.0 online
}}
[[de:Banner]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/banner/issues Issue Tracker].
 

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/banner.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/banner". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Banner is dependent on the modules "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Banner Module Version 1.11.2 ([http://www.contao.org/extension-list/view/banner.10110029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Banner Module Version 1.9.2 ([http://www.contao.org/extension-list/view/banner.10090029.en.html Direct Link])
===TYPOlight 2.6===
Users of TYPOlight 2.6.x, please use Banner Module Version 1.6.5 ([http://www.contao.org/extension-list/view/banner.10060059.en.html Direct Link])
 

=Installation as an update=
An update is identical to the installation. 
'''Notice when updating from < 1.10.0 to the latest version:''' 
The CSS file "mod_banner_fe.css" which is included as an example, the uppercase / lowercase letters changed in a class. 
Anyone who has imported this file or the design itself has to produce, the class ".mod_Banner" must change in ".mod_banner". 

==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Banner_Update_v1_to_v2|'''Banner Update Version 1 to Version 2''']]
 

=Overview=
The Banner Module contains two back end and one front end module. 
In the back end, there are "Banner" and "Banner Statistic", for the front end "Banner".

==Back end==

===Banner===
[[File:Banner_en_backend_banner.jpg|Back end module Banner]]

===Banner Statistic===
[[File:Banner_en_backend_bannerstatistic.jpg|Back end module Banner Statistic]]

==Front end==

===Display a banner===
[[File:Banner_en_frontend_one_banner.jpg|Front end module Banner]]
# Module Headline
# Banner Image
# Banner Comment
# Banner Name

More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".

===Display all Banner===
With 'all Banner' is meant here, all banners in the selected category. 
[[File:Banner_en_frontend_all_banner.jpg|Front end all banner|left]]
In this example, 3 banners have been defined, 
* Graphic Banner
* Flash Banner
* Text Banner 
More details about this see under "[[Banner#Using|Using]]" or "[[Banner#Technical_Details|Technical Details]]".
 

=Using=
The first one creates a new banner category via the menu item "banner". In this then the banners.
Then, create a front end module and build it into the layout of the page.
Here are the steps, each with the default values. [[Banner#Technical_Details|Technical details]] will be explained later.

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Banner'. In the main area click on the button 'New category'.
[[File:Banner_en_backend_category_new.jpg|New Banner Category]]

There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

==Create the banners==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New Banner' and then the arrow icon, or click the plus in the head of the category: 
[[File:Banner_en_backend_banner_new.jpg|New Banner]]

First they must select the banner source:
* internal Banner (Graphic / Flash files is stored on server)
* external Banner (Graphic / Flash files are integrated via URL)
* Text Banner
 
After selecting it appear the appropriate form fields.

===Graphic Banners===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template appears below the banner graphic.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the banner graphic. The input must include "http://".
#* Optional field.
#* Without a URL, the banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
#* '''CAUTION''': Animated GIFs are for size definitions through the GD recalculation unfortunately to still images.
# Banner Comment
#* The first line will be installed and displayed as a "title" tag in the HTML source code if you move the cursor over the banner graphic.
# Published
#* If this option is not selected, this banner is not displayed.

===Flash Banner===
# Banner Name
#* The banner name will be displayed only in the Banner overview.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking on the Flash Banner. The input must include "http://".
#* Optional field.
#* Without a URL, the Flash Banner will be displayed without a link.
#* Alternative can be selected an internal target (Banner target page)
# Banner Image
#* Here you can now select the banner file.
# Banner width and height
#* To customize the banner size, you can specify the banner width and / or the banner height in pixels.
# Banner Comment
#* Input is not necessary, is not used in the front end
# Published
#* If this option is not selected, this banner is not displayed.

A flash fallback to an image file is available, see the section [[Banner#Flash_Fallback_Image|Technical Details]]

===Text Banner===
# Banner Name
#* The banner name will be displayed in the Banner overview and in the provided template as a headline that is linked simultaneously with the target URL.
# Banner weighting
#* This controls the display frequency of the banners. The higher the priority, the more often this banner is displayed.
# Banner target URL
#* The URL of the target by clicking. The input must include "http://".
#* Optional field.
#* Without a URL, the Text Banner will be displayed without a link.
#* in provided template only the domain is shown as a short form. (Third row, see picture above)
# Banner Comment
#* This is the text line. (Second row, see picture above)
# Published
#* If this option is not selected, this banner is not displayed.

==Front end module==
A new front-end module is create with: 
* Layout -> Themes -> Modules -> Add module (Contao 2.9 and newer)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
Be sure to '''first enter the title''', then selecting for module type:''Miscellaneous -> Banner''.
Now the form fields change accordingly. 
In 'Banner Categories' select the previously created category, then 'Save and Close'. 
 
Now, the front end module must be included in the layout: 
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)
Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
For the first tests you should copy the provided file mod_banner_fe.css from /system/modules/banner to /tl_files . Then import them over the back end and activate it in the layout.

=Technical Details=
Technical details are inside of the category, in the banner denifinition and in the constructed front end module feasible / adjustable.

==Technical Details in the Category Definition==
===Number of banners===
* Show all banners
If you choose this option, all active banners will be showed in front end. 
In addition, you can choose:
* Limiting the number of banners
Here, the number can be limited. Default is 0: show all banners, otherwise maximum number of banners that will be showed.
* Random order
If you choose this option, the banners will shown in a random order.

==Technical Details in the Banner Definition==
===Flash Fallback Image===
If a browser does not support Flash or JavaScript is disabled, an image can be displayed instead (since version 2.2.0). At a local (internal) flash file, in the same path is searched for an image file with the same name but with the ending jpg, png or gif. 
Example: for "myflash.swf" would be a fallback image: "myflash.jpg" 
Was found a replacement image, the image is displayed. If necessary, the image is converted to the dimensions of the flash file.

===Display limitation by Start / Stop dates and times===
* Show from
** If you enter a date and time value here the current banner will not be shown on the website before this moment.
* Show until
** If you enter a date and time value here the current banner will not be shown on the website after this moment.

===Limiting the number of Views and Clicks===
* Limiting the number of Views and Clicks
If you select this option, you can define a maximum number of views and/or maximum number of clicks.
* Limiting the number of Views
** By entering a number, the current banner is no longer displayed after this number of views. The "Limiting the number of Views and Clicks" has enabled it to stay.
* Limiting the number of Clicks
** By entering a number, the current banner is no longer displayed after this number of clicks. The "Limiting the number of Views and Clicks" has enabled it to stay.

===Filter Domain===
If you enter a domain name, this banner is used only for this domain.If you leave the field empty, this banner is used for all domains. Example: '''yourdomain.com''' 
 
The banner will be displayed, if matches the domain. But also in partial match starting from the right. So also with access via "'''sub.yourdomain.com'''" .An entry in "Site structure" - "Domain Name" is not required for the filtering.

==Technical Details in the Front end Module Definition==

===First banner for new visitor===
For each new visitor, at first is displayed the first published banner in the category. The choice is then returned to random mode. Thus, a kind of recognition can be achieved.

===Templates===
Each module can be assigned its own Template. Two different templates are included. 
* mod_banner_list_all
** All fields are included.
* mod_banner_list_min
** The headline and name were removed. It will only display the banner itself.

Both templates also support text banners. 
For own Templates, the template files must start with "mod_banner_list_" and end with ".tpl".
Example: "mod_banner_list_special.tpl"

{{Note|In Banner Version 1.x this selection is located in the banner category.}}
 

===Prevention of counting their own requests===
You can set a custom UserAgent String in your browser and in the banner modul configuration.
 
Via:
* Layout -> Themes -> Modules -> Modul Name (Contao 2.9 and newer)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the applied banners module in the new field "No counting for this HTTP_USER_AGENT partial identifier" , a string is entered, it should be unique. 
Example: CTISOK 
Save it. 
Several strings are also possible, then enter them separated by commas. 
so you can change the User Agent String of Mozilla Firefox: 
 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER
# Type '''general.useragent.extra.firefox''' in the Filter bar
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.6.3 CTISOK".

 
You can check your new User Agent String , type '''about:''' in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]

=Specific feature=
==Bot Detection off==
Who wants to count the hits from bots and search engines on the banners can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_bot_check'] = false;
</source>

 

==Change Banner Block Time for Views==
As written in the beginning, when a banner is displayed multiple times within 10 minutes (C3: 5 minutes), this banner is only counted once. 
With an entry in the localconfig.php can change that. The values be there in minutes, the number must be> 0, otherwise will be automatically taken back to the default value (10).
{{Caution|This applies to all Banner modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after ### INSTALL SCRIPT STOP ### ) causes a change to 5 minutes: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_banner_block_time'] = 5;
</source>
 

==Exception: No active banners defined and no default banner defined==
If, in this case, "Hide if empty" is not activated, until now was an empty image tag generated, what was presented by the IE as Broken Image. From version 1.11.2 now a DIV tag with class = "banner_empty" is generated:
<source lang="html4strict">
<div class="mod_banner">
<div class="banner_empty">

</div>
</div>
</source>
With CSS can now be reached that is maintained (in this example) the amount and thus the layout of the site will not change:
<source lang="css">
.mod_banner .banner_empty {
height:90px;
}
</source>
The resultant text can be overridden to enforce in langconfig.php, here is an example of an empty text:
<source lang="php">
$GLOBALS['TL_LANG']['MSC']['tl_banner']['noBanner'] = '';
</source>

 
==Special case: Multiple Banner modules on one page==
Here are some hints and tips for well-known application scenarios and their characteristics.

===One category - Two front end modules on one page===
In the current version it is possible to display all the banners from one category. 
The old version's multiple banners on a Web page was to be able to create multiple front end modules and integrating them into the website. The module is prevented that a banner will not appear more than once. 
Well, it was assumed that all displayed below each other, so it made sense, the module title to display only once. 
If you want to leave now for all the title's banner front-end modules, because they are distributed on the page, must be made for this purpose a small modification to the template. Create a copy on the back end of the template "mod_banner_list_all" and renames it here, for example, in "mod_banner_list_special.tpl. 
There, now you change the third line as follows: 
Original: 
<source lang="php">
<?php if (($this->headline) && (!$this->headline_stop)): ?>
</source>
Special: 
<source lang="php">
<?php if ($this->headline) : ?>
</source>
Now edit the banner front end modules and select the new template. 
Done.
 
This is also true for more than two front end modules.
 

===Two categories - Two front end modules on one page===
In this case, each front end module its own category. Again, only on the first module, the heading will appear for the same reason as in the previous section. 
If you want to display in this scenario all module headers, the solution is the same. 
This is also true for more than two front end modules.
 
 

----
--[[User:BugBuster|BugBuster]] 16:27, 10 July 2011 (CEST)

Integrity Check

2013-04-04T20:04:34Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.5 / 3.1.0
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 20:06, 1 April 2013 (CEST)

LastLogin

2013-04-02T14:40:45Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Display of last login and the list of online / offline members over Insert-Tags. 
From Contao 2.8 is already displayed by the login module itself the last login time. 
This module now supports the internal method and also includes an insert-tag for this. 
More Insert-Tags have been added over the course of development, as shown in the follow list. 

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.9.1 / 3.0.0
| Version=from 2.9
| TLVersion=2.8.0 - 2.8.4 (see installations notes)
| Depending=[[Memberlist|memberlist]] (mandatory), [[Avatar|avatar]] (optional)
| ERLink=http://www.contao.org/extension-list/view/lastlogin.en.html
| DonateLink=http://www.amazon.de/wishlist/26HHEJOU03G76
| TrackerLink=https://github.com/BugBuster1701/lastlogin/issues
| VCSLink=https://github.com/BugBuster1701/lastlogin
| Comment=Version for Contao 3.0 online
}}
[[de:LastLogin]]
[[Category:Extensions]]

=Forum=
Questions about the LastLogin module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/lastlogin/issues Issue Tracker].
 

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/lastlogin.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/lastlogin". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

==Note for older Contao versions==
===Contao 2.8 - 2.11 ===
Contao 2.8 - 2.11 , please use LastLogin module version 1.9.1 ([http://www.contao.org/extension-list/view/lastlogin.10090019.en.html Direct Link])
===Contao 2.7===
Users of Contao 2.7.x, please use LastLogin module version 1.4.1 ([http://www.contao.org/extension-list/view/lastlogin.10040019.en.html Direct Link])

=Installation as an update=
An update is identical to the installation.

=Overview=
The last login module has no back end or front end modules, it provides only insert tags. 
{{Hint|All Insert-Tags from the module to be resistant from Contao 2.8 cache by adding the prefix "cache_".}}
When the cache is turned on in the site structure, the values of the insert tags will not be saved with the cache, but will be replaced again with each delivery from the cache. 
Example: "last_login" becomes "cache_last_login.
 

The following Insert-Tags are currently available:
* [[LastLogin#Last_Login|Last Login]]
** last_login / cache_last_login

* [[LastLogin#Online_members|Online Members]]
** last_login_members_online / cache_last_login_members_online
* [[LastLogin#Online_members_linked|Online Members linked]]
** last_login_members_online_link / cache_last_login_members_online_link

* [[LastLogin#Number_registered_members|Number registered members]]
** last_login_number_registered_members / cache_last_login_number_registered_members
* [[LastLogin#Number_online_members|Number online members]]
** last_login_number_online_members / cache_last_login_number_online_members
* [[LastLogin#Number_offline_members|Number offline members]]
** last_login_number_offline_members / cache_last_login_number_offline_members

* [[LastLogin#Offline_members|Offline Members]]
** last_login_members_offline / cache_last_login_members_offline
* [[LastLogin#Offline_members_linked|Offline Members linked]]
** last_login_members_offline_link / cache_last_login_members_offline_link

All the insert tags are controlled by parameters of what and how something is to be displayed. (firstname,lastname,avatar,...)

==Last Login==
Shows the own "Last Login" time. Expandable with additional parameters. 
Without the format information is generated after the system definition "dateFormat". The example of the default installation "webacademy" is there defined as: "Y-m-d". 
On example would be the last login on 3.4.2009 at 16:27 o'clock: :
<source lang="php">
Last Login: {{cache_last_login}}
Last Login: {{cache_last_login::d.m.y H:i}}
</source>
shows:
<source lang="text">
Last Login: 2009-04-03
Last Login: 03.04.09 16:27
</source>

If a member log on for the first time, no date for the last login is available. Instead, the current date is displayed. 
Since version 1.9.0 it is possible to force the output in this case with a "0". Syntax:
<source lang="php">
Last Login: {{cache_last_login::zero}}
</source>
shows on first login: 0, after each additional login will shown the date. The date format can also be defined again:
<source lang="php">
Last Login: {{cache_last_login::zero::d.m.Y H:i}}
</source>

About the output of the "0", you can now respond in the template and print information on first login:
<source lang="php">
<?php if ($this->replaceInsertTags( '{{cache_last_login::zero}}' ) == 0 ) : ?>
Warning: This is your first login, please immediately change your password!
<?php endif; ?>
</source>

==Online members==
Shows all the online and active members. Expandable with additional parameters. Each member must have released these fields. (Public fields)

===Comma-separated output===
Examples:
<source lang="php">
{{cache_last_login_members_online::username}}
{{cache_last_login_members_online::firstname}}
{{cache_last_login_members_online::lastname}}
{{cache_last_login_members_online::fullname}}
{{cache_last_login_members_online::avatar}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_online}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Output as a list===
The further declaration "list", will be used the included template "mod_last_login_members". 
This will output a list of the names. 
Examples:
<source lang="php">
{{cache_last_login_members_online::username::list}}
{{cache_last_login_members_online::firstname::list}}
{{cache_last_login_members_online::lastname::list}}
{{cache_last_login_members_online::fullname::list}}
{{cache_last_login_members_online::avatar::list}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_online::list}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Online members linked===
Online members as a linked issue with connection to the module member list. It can be specified which field to display (first parameter) and the alias name of the site by the Member List module has been integrated (second parameter). 
Use as cache_last_login_members_online, following information are available:
<source lang="php">
{{cache_last_login_members_online_link::username::memberlist}}
{{cache_last_login_members_online_link::firstname::memberlist}}
{{cache_last_login_members_online_link::lastname::memberlist}}
{{cache_last_login_members_online_link::fullname::memberlist}}
{{cache_last_login_members_online_link::avatar::memberlist}}
</source>
The words "username" and "memberlist" represents the default specification, <nowiki>{{cache_last_login_members_online_link}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
 

Examples: Output should be firstname, alias name is "mymemberlist":
<source lang="php">
{{cache_last_login_members_online_link::firstname::mymemberlist}}
</source>
generated when there are 2 users online (with ID 4 and 5):
<source lang="html4strict">
<div class="mod_last_login">
<ul class="members_online_link">
<li><a href="mymemberlist.html?show=4" title="Profile view">Donna</a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view">John</a></li>
</ul>
</div>
</source>
With "avatar", as follows:
<source lang="html4strict">
<div class="mod_last_login">
<ul class="members_online_link_avatar">
<li><a href="mymemberlist.html?show=4" title="Profile view Donna Evans">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_4.jpg"></a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view John Smith">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_5.jpg"></a></li>
</ul>
</div>
</source>

==Number registered members==
Shows the number of registered members. 
Examples:
<source lang="php">
There are {{cache_last_login_number_registered_members}} registered members.
</source>

==Number online members==
Shows the number of online members. 
Examples:
<source lang="php">
There are {{cache_last_login_number_online_members}} online members.
</source>

==Number offline members==
Shows the number of offline members, but were already online today. 
Examples:
<source lang="php">
There are {{cache_last_login_number_offline_members}} offline members, recently online.
</source>

==Offline members==
Shows offline members, recently online. Expandable with additional parameters.
===Comma-separated output===
<source lang="php">
{{cache_last_login_members_offline::username}}
{{cache_last_login_members_offline::firstname}}
{{cache_last_login_members_offline::lastname}}
{{cache_last_login_members_offline::fullname}}
{{cache_last_login_members_offline::avatar}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_offline}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}
===Output as a list===
<source lang="php">
{{cache_last_login_members_offline::list}}
{{cache_last_login_members_offline::username::list}}
{{cache_last_login_members_offline::firstname::list}}
{{cache_last_login_members_offline::lastname::list}}
{{cache_last_login_members_offline::fullname::list}}
{{cache_last_login_members_offline::avatar::list}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_offline::list}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Offline members linked===
Offline members (recently online) as a linked issue with connection to the module member list. It can be specified which field to display (first parameter) and the alias name of the site by the Member List module has been integrated (second parameter). 
Use as last_login_members_offline, following information are available:
<source lang="php">
{{cache_last_login_members_offline_link::username::memberlist}}
{{cache_last_login_members_offline_link::firstname::memberlist}}
{{cache_last_login_members_offline_link::lastname::memberlist}}
{{cache_last_login_members_offline_link::fullname::memberlist}}
{{cache_last_login_members_offline_link::avatar::memberlist}}
</source>
The words "username" and "memberlist" represents the default specification, <nowiki>{{cache_last_login_members_offline_link}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
 

Examples: Output should be firstname, alias name is "mymemberlist":
<source lang="php">
{{cache_last_login_members_offline_link::firstname::mymemberlist}}
</source>
generated when there are 2 users online (with ID 4 and 5):
<source lang="html4strict">
<div class="mod_last_login_offline">
<ul class="members_offline_link">
<li><a href="mymemberlist.html?show=4" title="Profile view">Donna</a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view">John</a></li>
</ul>
</div>
</source>
With "avatar", as follows:
<source lang="html4strict">
<div class="mod_last_login_offline">
<ul class="members_offline_link_avatar">
<li><a href="mymemberlist.html?show=4" title="Profile view Donna Evans">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_4.jpg"></a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view John Smith">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_5.jpg"></a></li>
</ul>
</div>
</source>

=Tutorials=
==Using as HTML Module==
The following code could be used to place the insert-tags to an HTML module:
<source lang="html4strict">

<div class="mod_login">
Last Login: {{cache_last_login::d.m.Y}}
</div>

</source>
Then specify in the HTML module, "Protect module" and on "Allowed member groups" select "Select all".
So that the module is shown only in a logged state.

==Multilingualism==
With the Insert-Tag "<nowiki>{{iflng}}</nowiki>" you could do it in several languages:
<source lang="php">
{{iflng::en}}Last login:{{iflng}}{{iflng::de}}Letzer Login:{{iflng}} {{cache_last_login}}
</source>

==When does "online" / "offline"?==
In "cache_last_login_members_online" / "cache_last_login_number_online_members" users must perform an action (page view) have done in Contao within the last 5 minutes. (Session table)

In "cache_last_login_members_offline" / "cache_last_login_number_offline_members" it is quite complex, which was then so are discussed and defined:
* Users who have accessed within the session time for 5 minutes no pages (but session owner)
* Users were today or yesterday online and today offline, by logging off
* Users were online today, but have no more session, and are not logged (but session deleted)

This means you get not all appear. It will only be displayed that were recently online, but already offline or considered as such.

==Limit the number of output as a list==
In output as a list, it is possible by an additional parameter to limit the number. Examples of each type (with 5 lines):
<source lang="php">
{{cache_last_login_members_online::username::list::5}}
{{cache_last_login_members_online::avatar::list::5}}
{{cache_last_login_members_online_link::lastname::memberlist::5}}
{{cache_last_login_members_online_link::avatar::memberlist::5}}
{{cache_last_login_members_offline::lastname::list::5}}
{{cache_last_login_members_offline::avatar::list::5}}
{{cache_last_login_members_offline_link::fullname::memberlist::5}}
{{cache_last_login_members_offline_link::avatar::memberlist::5}}
</source>

----
--[[User:BugBuster|BugBuster]] 00:06, 27 January 2013 (CET)

Visitors

2013-04-01T18:19:42Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.8.0 / 3.1.0
| Version=from 2.19
| TLVersion=2.7 - 2.9 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.0 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight/Contao" versions==
===Contao 2.9===
Users of Contao 2.9.x, please use Visitors Module Version 2.7.1 ([http://www.contao.org/extension-list/view/visitors.20070019.en.html Direct Link])
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.2 ([http://www.contao.org/extension-list/view/visitors.10070029.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible.tpl
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".tpl".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Dlstats

2013-04-01T18:07:54Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Counts the number of file downloads

* Download statistics for the standard content elements Download and Downloads
* Count number of downloads per file plus latest download timestamp
* Optionally log every single download with timestamp, IP and username.
* Insert-Tag for number of downloads in the frontend (from 2.1.0)
* Ignore certain IPs (define itself, from 2.1.0)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.glen-langer.de
| ExtVersion=2.3.1 / 3.1.0
| Version=from 2.9
| TLVersion=2.7.6 - 2.8.4
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=http://www.contao.org/extension-list/view/dlstats.en.html
| TrackerLink=https://github.com/BugBuster1701/dlstats/issues
}}
[[de:dlstats]]
[[Category:Extensions]]

==Installation==
The installation of the module occurs about the extension Repository in back end of Contao. On manual installation, call /contao/install.php - Perform Update Database. 
'''''For manual installation, please note that the module "[[Bot Detection|Bot Detection]]" must be installed.'''''

==Using==
Go to the Contao Settings and switch on the logging, either only counting the number of downloads per file, or optionally also log each download with timestamp and IP. 
'''For dlstats 2.1.x:''' In the settings you can be deactivated the Anonymize IP function, it must be the admin. 
'''From dlstats 2.2.0:''' IP addresses anonymous: "yes/no" is now controlled by Contao itself. 
(System - Settings - Privacy settings - Anonymize IP addresses) 
Use the content element File Download or File Downloads for all downloaded files you want to have counted. 
After downloading a file you will find the statistics under Content - Download Stats.

==Using Insert-Tag==
The Insert-Tag "cache_dlstats::total downloads::..." supports both, the source of the file (relative path + file name), as well as in connection with the article alias and how it generates for ce_download and ce_downloads. Therefore, the use is well used in the templates of the two CEs, see examples. Return is only the number of downloads as a number.
<source lang="php">
{{cache_dlstats::totaldownloads::tl_files/cdc2010.pdf}}
{{cache_dlstats::totaldownloads::CDC_2010.html?file=tl_files/cdc2010.pdf}}

// in ce_download template:
{{cache_dlstats::totaldownloads::<?php echo $this->href; ?>}}

// in ce_downloads template:
{{cache_dlstats::totaldownloads::<?php echo $file['href']; ?>}}
</source>

==Ignore certain IPs==
If any downloads from certain IP addresses should not be counted, this can be defined in the localconfig.php as follows:
<source lang="php">
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.1.2';
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.0.0/24';
//respectively
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Notice==
* Simple links to files will not be counted as downloads!
* If you are logged in the backend, your download is not counted. (from 2.1.0)

----
--[[User:BugBuster|BugBuster]] 20:07, 1 April 2013 (CEST)

Integrity Check

2013-04-01T18:06:58Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.3.4 / 3.1.0
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0: minutely(manual), hourly, daily, weekly, monthly

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 20:06, 1 April 2013 (CEST)

Dlstats

2013-03-17T17:20:41Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Counts the number of file downloads

* Download statistics for the standard content elements Download and Downloads
* Count number of downloads per file plus latest download timestamp
* Optionally log every single download with timestamp, IP and username.
* Insert-Tag for number of downloads in the frontend (from 2.1.0)
* Ignore certain IPs (define itself, from 2.1.0)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://contao.glen-langer.de
| ExtVersion=2.3.0 / 3.0.0
| Version=from 2.9
| TLVersion=2.7.6 - 2.8.4
| Depending=[[Bot Detection|Bot Detection]]
| ERLink=http://www.contao.org/extension-list/view/dlstats.en.html
| TrackerLink=https://github.com/BugBuster1701/dlstats/issues
}}
[[de:dlstats]]
[[Category:Extensions]]

==Installation==
The installation of the module occurs about the extension Repository in back end of Contao. On manual installation, call /contao/install.php - Perform Update Database. 
'''''For manual installation, please note that the module "[[Bot Detection|Bot Detection]]" must be installed.'''''

==Using==
Go to the Contao Settings and switch on the logging, either only counting the number of downloads per file, or optionally also log each download with timestamp and IP. 
'''For dlstats 2.1.x:''' In the settings you can be deactivated the Anonymize IP function, it must be the admin. 
'''From dlstats 2.2.0:''' IP addresses anonymous: "yes/no" is now controlled by Contao itself. 
(System - Settings - Privacy settings - Anonymize IP addresses) 
Use the content element File Download or File Downloads for all downloaded files you want to have counted. 
After downloading a file you will find the statistics under Content - Download Stats.

==Using Insert-Tag==
The Insert-Tag "cache_dlstats::total downloads::..." supports both, the source of the file (relative path + file name), as well as in connection with the article alias and how it generates for ce_download and ce_downloads. Therefore, the use is well used in the templates of the two CEs, see examples. Return is only the number of downloads as a number.
<source lang="php">
{{cache_dlstats::totaldownloads::tl_files/cdc2010.pdf}}
{{cache_dlstats::totaldownloads::CDC_2010.html?file=tl_files/cdc2010.pdf}}

// in ce_download template:
{{cache_dlstats::totaldownloads::<?php echo $this->href; ?>}}

// in ce_downloads template:
{{cache_dlstats::totaldownloads::<?php echo $file['href']; ?>}}
</source>

==Ignore certain IPs==
If any downloads from certain IP addresses should not be counted, this can be defined in the localconfig.php as follows:
<source lang="php">
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.1.2';
$GLOBALS['DLSTATS']['BOT_IPV4'][] = '192.168.0.0/24';
//respectively
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8::1';
$GLOBALS['DLSTATS']['BOT_IPV6'][] = '2001:0db8:85a3:0800::/56';
</source>

==Notice==
* Simple links to files will not be counted as downloads!
* If you are logged in the backend, your download is not counted. (from 2.1.0)

----
--[[User:BugBuster|BugBuster]] 00:10, 29 December 2011 (CET)

LastLogin

2013-01-26T23:06:40Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.''''' 

Display of last login and the list of online / offline members over Insert-Tags. 
From Contao 2.8 is already displayed by the login module itself the last login time. 
This module now supports the internal method and also includes an insert-tag for this. 
More Insert-Tags have been added over the course of development, as shown in the follow list. 

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.9.0 / 3.0.0
| Version=from 2.9
| TLVersion=2.8.0 - 2.8.4 (see installations notes)
| Depending=[[Memberlist|memberlist]] (mandatory), [[Avatar|avatar]] (optional)
| ERLink=http://www.contao.org/extension-list/view/lastlogin.en.html
| DonateLink=http://www.amazon.de/wishlist/26HHEJOU03G76
| TrackerLink=https://github.com/BugBuster1701/lastlogin/issues
| VCSLink=https://github.com/BugBuster1701/lastlogin
| Comment=Version for Contao 3.0 online
}}
[[de:LastLogin]]
[[Category:Extensions]]

=Forum=
Questions about the LastLogin module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/lastlogin/issues Issue Tracker].
 

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/lastlogin.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/lastlogin". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

==Note for older Contao versions==
===Contao 2.8 - 2.11 ===
Contao 2.8 - 2.11 , please use LastLogin module version 1.9.1 ([http://www.contao.org/extension-list/view/lastlogin.10090019.en.html Direct Link])
===Contao 2.7===
Users of Contao 2.7.x, please use LastLogin module version 1.4.1 ([http://www.contao.org/extension-list/view/lastlogin.10040019.en.html Direct Link])

=Installation as an update=
An update is identical to the installation.

=Overview=
The last login module has no back end or front end modules, it provides only insert tags. 
{{Hint|All Insert-Tags from the module to be resistant from Contao 2.8 cache by adding the prefix "cache_".}}
When the cache is turned on in the site structure, the values of the insert tags will not be saved with the cache, but will be replaced again with each delivery from the cache. 
Example: "last_login" becomes "cache_last_login.
 

The following Insert-Tags are currently available:
* [[LastLogin#Last_Login|Last Login]]
** last_login / cache_last_login

* [[LastLogin#Online_members|Online Members]]
** last_login_members_online / cache_last_login_members_online
* [[LastLogin#Online_members_linked|Online Members linked]]
** last_login_members_online_link / cache_last_login_members_online_link

* [[LastLogin#Number_registered_members|Number registered members]]
** last_login_number_registered_members / cache_last_login_number_registered_members
* [[LastLogin#Number_online_members|Number online members]]
** last_login_number_online_members / cache_last_login_number_online_members
* [[LastLogin#Number_offline_members|Number offline members]]
** last_login_number_offline_members / cache_last_login_number_offline_members

* [[LastLogin#Offline_members|Offline Members]]
** last_login_members_offline / cache_last_login_members_offline
* [[LastLogin#Offline_members_linked|Offline Members linked]]
** last_login_members_offline_link / cache_last_login_members_offline_link

All the insert tags are controlled by parameters of what and how something is to be displayed. (firstname,lastname,avatar,...)

==Last Login==
Shows the own "Last Login" time. Expandable with additional parameters. 
Without the format information is generated after the system definition "dateFormat". The example of the default installation "webacademy" is there defined as: "Y-m-d". 
On example would be the last login on 3.4.2009 at 16:27 o'clock: :
<source lang="php">
Last Login: {{cache_last_login}}
Last Login: {{cache_last_login::d.m.y H:i}}
</source>
shows:
<source lang="text">
Last Login: 2009-04-03
Last Login: 03.04.09 16:27
</source>

If a member log on for the first time, no date for the last login is available. Instead, the current date is displayed. 
Since version 1.9.0 it is possible to force the output in this case with a "0". Syntax:
<source lang="php">
Last Login: {{cache_last_login::zero}}
</source>
shows on first login: 0, after each additional login will shown the date. The date format can also be defined again:
<source lang="php">
Last Login: {{cache_last_login::zero::d.m.Y H:i}}
</source>

About the output of the "0", you can now respond in the template and print information on first login:
<source lang="php">
<?php if ($this->replaceInsertTags( '{{cache_last_login::zero}}' ) == 0 ) : ?>
Warning: This is your first login, please immediately change your password!
<?php endif; ?>
</source>

==Online members==
Shows all the online and active members. Expandable with additional parameters. Each member must have released these fields. (Public fields)

===Comma-separated output===
Examples:
<source lang="php">
{{cache_last_login_members_online::username}}
{{cache_last_login_members_online::firstname}}
{{cache_last_login_members_online::lastname}}
{{cache_last_login_members_online::fullname}}
{{cache_last_login_members_online::avatar}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_online}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Output as a list===
The further declaration "list", will be used the included template "mod_last_login_members". 
This will output a list of the names. 
Examples:
<source lang="php">
{{cache_last_login_members_online::username::list}}
{{cache_last_login_members_online::firstname::list}}
{{cache_last_login_members_online::lastname::list}}
{{cache_last_login_members_online::fullname::list}}
{{cache_last_login_members_online::avatar::list}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_online::list}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Online members linked===
Online members as a linked issue with connection to the module member list. It can be specified which field to display (first parameter) and the alias name of the site by the Member List module has been integrated (second parameter). 
Use as cache_last_login_members_online, following information are available:
<source lang="php">
{{cache_last_login_members_online_link::username::memberlist}}
{{cache_last_login_members_online_link::firstname::memberlist}}
{{cache_last_login_members_online_link::lastname::memberlist}}
{{cache_last_login_members_online_link::fullname::memberlist}}
{{cache_last_login_members_online_link::avatar::memberlist}}
</source>
The words "username" and "memberlist" represents the default specification, <nowiki>{{cache_last_login_members_online_link}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
 

Examples: Output should be firstname, alias name is "mymemberlist":
<source lang="php">
{{cache_last_login_members_online_link::firstname::mymemberlist}}
</source>
generated when there are 2 users online (with ID 4 and 5):
<source lang="html4strict">
<div class="mod_last_login">
<ul class="members_online_link">
<li><a href="mymemberlist.html?show=4" title="Profile view">Donna</a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view">John</a></li>
</ul>
</div>
</source>
With "avatar", as follows:
<source lang="html4strict">
<div class="mod_last_login">
<ul class="members_online_link_avatar">
<li><a href="mymemberlist.html?show=4" title="Profile view Donna Evans">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_4.jpg"></a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view John Smith">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_5.jpg"></a></li>
</ul>
</div>
</source>

==Number registered members==
Shows the number of registered members. 
Examples:
<source lang="php">
There are {{cache_last_login_number_registered_members}} registered members.
</source>

==Number online members==
Shows the number of online members. 
Examples:
<source lang="php">
There are {{cache_last_login_number_online_members}} online members.
</source>

==Number offline members==
Shows the number of offline members, but were already online today. 
Examples:
<source lang="php">
There are {{cache_last_login_number_offline_members}} offline members, recently online.
</source>

==Offline members==
Shows offline members, recently online. Expandable with additional parameters.
===Comma-separated output===
<source lang="php">
{{cache_last_login_members_offline::username}}
{{cache_last_login_members_offline::firstname}}
{{cache_last_login_members_offline::lastname}}
{{cache_last_login_members_offline::fullname}}
{{cache_last_login_members_offline::avatar}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_offline}}</nowiki> will also apply. 
'''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}
===Output as a list===
<source lang="php">
{{cache_last_login_members_offline::list}}
{{cache_last_login_members_offline::username::list}}
{{cache_last_login_members_offline::firstname::list}}
{{cache_last_login_members_offline::lastname::list}}
{{cache_last_login_members_offline::fullname::list}}
{{cache_last_login_members_offline::avatar::list}}
</source>
The word "username" represents the default specification, <nowiki>{{cache_last_login_members_offline::list}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
{{Hint|The term "avatar" will only work if the module "[http://www.contao.org/extension-list/view/avatar.en.html avatar]" is installed. This does not happen automatically because it has not been defined as dependence in the ER.}}

===Offline members linked===
Offline members (recently online) as a linked issue with connection to the module member list. It can be specified which field to display (first parameter) and the alias name of the site by the Member List module has been integrated (second parameter). 
Use as last_login_members_offline, following information are available:
<source lang="php">
{{cache_last_login_members_offline_link::username::memberlist}}
{{cache_last_login_members_offline_link::firstname::memberlist}}
{{cache_last_login_members_offline_link::lastname::memberlist}}
{{cache_last_login_members_offline_link::fullname::memberlist}}
{{cache_last_login_members_offline_link::avatar::memberlist}}
</source>
The words "username" and "memberlist" represents the default specification, <nowiki>{{cache_last_login_members_offline_link}}</nowiki> will also apply. '''The members are displayed only when you are online.'''
 

Examples: Output should be firstname, alias name is "mymemberlist":
<source lang="php">
{{cache_last_login_members_offline_link::firstname::mymemberlist}}
</source>
generated when there are 2 users online (with ID 4 and 5):
<source lang="html4strict">
<div class="mod_last_login_offline">
<ul class="members_offline_link">
<li><a href="mymemberlist.html?show=4" title="Profile view">Donna</a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view">John</a></li>
</ul>
</div>
</source>
With "avatar", as follows:
<source lang="html4strict">
<div class="mod_last_login_offline">
<ul class="members_offline_link_avatar">
<li><a href="mymemberlist.html?show=4" title="Profile view Donna Evans">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_4.jpg"></a></li>
<li><a href="mymemberlist.html?show=5" title="Profile view John Smith">
<img width="32" height="31" class="avatar" alt="avatar" src="tl_files/avatars/member_5.jpg"></a></li>
</ul>
</div>
</source>

=Tutorials=
==Using as HTML Module==
The following code could be used to place the insert-tags to an HTML module:
<source lang="html4strict">

<div class="mod_login">
Last Login: {{cache_last_login::d.m.Y}}
</div>

</source>
Then specify in the HTML module, "Protect module" and on "Allowed member groups" select "Select all".
So that the module is shown only in a logged state.

==Multilingualism==
With the Insert-Tag "<nowiki>{{iflng}}</nowiki>" you could do it in several languages:
<source lang="php">
{{iflng::en}}Last login:{{iflng}}{{iflng::de}}Letzer Login:{{iflng}} {{cache_last_login}}
</source>

==When does "online" / "offline"?==
In "cache_last_login_members_online" / "cache_last_login_number_online_members" users must perform an action (page view) have done in Contao within the last 5 minutes. (Session table)

In "cache_last_login_members_offline" / "cache_last_login_number_offline_members" it is quite complex, which was then so are discussed and defined:
* Users who have accessed within the session time for 5 minutes no pages (but session owner)
* Users were today or yesterday online and today offline, by logging off
* Users were online today, but have no more session, and are not logged (but session deleted)

This means you get not all appear. It will only be displayed that were recently online, but already offline or considered as such.

==Limit the number of output as a list==
In output as a list, it is possible by an additional parameter to limit the number. Examples of each type (with 5 lines):
<source lang="php">
{{cache_last_login_members_online::username::list::5}}
{{cache_last_login_members_online::avatar::list::5}}
{{cache_last_login_members_online_link::lastname::memberlist::5}}
{{cache_last_login_members_online_link::avatar::memberlist::5}}
{{cache_last_login_members_offline::lastname::list::5}}
{{cache_last_login_members_offline::avatar::list::5}}
{{cache_last_login_members_offline_link::fullname::memberlist::5}}
{{cache_last_login_members_offline_link::avatar::memberlist::5}}
</source>

----
--[[User:BugBuster|BugBuster]] 00:06, 27 January 2013 (CET)

Visitors

2012-11-10T18:11:59Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''

[[File:Visitors-package-fe-wiki-en.jpg|right|Visitors]]This module allows you to count hits and visits of your website. 
In the display appears the hits and visits from the current day, as well as the respective total.
Statistic is also in the backend.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=2.7.1 / 3.0.0
| Version=from 2.9
| TLVersion=2.7.0 - 2.8.4 (see installation notes)
| Depending=[[Bot Detection|Bot Detection]],[[xls_export|Excel 95 writer (xls_export)]]
| ERLink=http://www.contao.org/extension-list/view/visitors.en.html
| DonateLink=Cappuccino
| TrackerLink=https://github.com/BugBuster1701/visitors/issues
| Comment=Version for Contao 3.0 online
}}
[[de:Visitors]]
[[Category:Extensions]]

=Forum=
Questions about the Visitors module will be answered in forum: [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported at GitHub: [https://github.com/BugBuster1701/visitors/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/visitors.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/visitors". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 
'''''The module Visitors is dependent on the module "[[Bot Detection|Bot Detection]]" and "[[xls_export|Excel 95 writer (xls_export)]]". They must therefore be installed with manual installation.'''''

 
==Note for older "TYPOlight" versions==
===TYPOlight 2.8===
Users of TYPOlight 2.8.x, please use Visitors Module Version 1.7.1 ([http://www.contao.org/extension-list/view/visitors.10070019.en.html Direct Link])
===TYPOlight 2.7===
Users of TYPOlight 2.7.x, please use Visitors Module Version 1.4.1 ([http://www.contao.org/extension-list/view/visitors.10040019.en.html Direct Link])
 
==Update version 1.x to version 2.x==
{{Caution|Version 2.x is not fully compatible with previous versions, an update is possible.}}
 
What is to be observed, can be found here.
*[[Visitors_Update_v1_to_v2|'''Visitors Update Version 1 to Version 2''']]
 

= Overview=
The Visitors module contains two back end and one front end module. 
In the back end, there are "Visitors" and "Visitor Statistics", for the front end "Visitors". 

 
==Back end==

===Visitors===
[[File:Visitors_en_backend_visitors.jpg]]

===Visitors Statistics===
[[File:Visitors_en_backend_visitorstatistics.jpg]]

shows in detail: (Click on image for higher resolution)
<gallery widths="240" heights="180" caption="Visitors Statistics">
File:Visitors_en_backend_visitorstatistics_details.jpg|Visitors Statistics
File:Visitors_en_backend_visitorstatistics_details_browser.jpg|Browser Statistics
File:Visitors_en_backend_visitorstatistics_details_searchengine.jpg|Search Engine Referer Statistics
</gallery>

==Front end==
For the front end are provided two CSS files as an example:
*mod_visitors_fe.css for the normal output, line by line
*mod_visitors_fe_horizontal.css for the horizontal output

===Visitors Statistics===
[[File:Visitors-package-fe-wiki-en.jpg]]

===Visitors Statistics, horizontal===
[[File:Visitors-package-fe-horizontal-wiki-en.jpg]]

 

=Using=
The first one creates a new visitor category via the menu item "visitors". In this then the counter. 
Then, create a front end module and build it into the layout of the page. 
Here are the steps, each with the default values. [[Visitors#Technical_Details|Technical details]] will be explained later. 
 

==Create the category==
To create a new category, just click on the left in the back end in 'content' to 'Visitors'. In the main area click on the button 'New category'. 
[[File:Visitors_en_backend_category_new.jpg]]
 
There, enter the name of the category. The front end module will later use this name. Then you click on "Save and close". 
Now you can see the category overview. By clicking on the pencil in the line of the category and repeated clicking on the pencil in the head of the category you return to the settings of the category.

 

== Create new counter==
In the category list now clicking on Edit (pencil) of the category. 
Now, either click the 'New counter' and then the arrow icon, or click the plus in the head of the category: 
[[File:Visitors_en_backend_counter_new.jpg]]

Now, some information are needed: :
* Name, (is displayed as a heading on the numbers).
* Start date, optional, only for display in font end
* Optional: 'Initial value of visitors/hits'
* Optional: 'Visitors per day'
* Activate "Published"
Then you click on "Save and close".

==Front end Module==
A new front-end module is create with:
* Layout -> Themes -> Modules -> Add module (Contao 2.9)
* Layout -> Modules -> Add module (TYPOlight 2.8.x)
 
At first, enter the title, and only then select in "Module type": 'Miscellaneous'-'Visitors'. It changes the form fields. 
In 'Visitors category' now select the previously created category, then 'Save and close'. 
 
Now, the front end module must be included in the layout:
* Layout -> Themes -> Layout -> Edit the used layout (Contao 2.9 and newer)
* Layout -> Page layout -> Edit the used layout (TYPOlight 2.8.x)

Include in 'Included modules' the just-created front end module (e.g. to left)

==CSS-File==
As mentioned above, are provided two CSS file for presentation. 
For the first tests you should copy the file <code>mod_visitors_fe.css</code> from <code>/system/modules/visitors</code> to <code>/tl_files</code> . Then import them over the back end and activate it in the layout.

 

=Technical Details=
Technical details are inside of the category, in the counter denifinition and in the constructed front end module feasible / adjustable. 

==Technical Details inside of the category==
===Counting mode===
From version 1.6.0, Counting mode is selectable, server side or browser side, by category:
* Load counting, server side by Contao
* Read counting, client side by browser
** (only on Contao cacheMode: server and browser cache / only browser cache)

With "Read counting" can be counted when the page is in the browser cache and will be called from it.
The system setting "Cache mode" will be respected.

{{Note|The display of current values will continue but only if the page is requested from the server.}}

==Technical Details inside of the counter denifinition==
===Block time===
The block time is in seconds. After interruption of the requests at this time, an access is counted as an additional visitor. 
Pre-entered are 1800 seconds, so that is 30 minutes. 

 
==Technical Details in the front end module definition==
===Templates===
Each module can be assigned its own Template. Four different templates are included.
* mod_visitors_fe_all
** All fields are included. (see example above)
* mod_visitors_fe_hits
** Here the visit rows were removed.
* mod_visitors_fe_visits
** Here the hit rows were removed.
* mod_visitors_fe_invisible.tpl
** Here, nothing is displayed. This template is used for a pure counting.

For own Templates, the template files must start with "mod_visitors_fe_" and end with ".tpl".

===Show to guests only===
Hide the module if a member (front end user) is logged in.

===Protect module===
Show the module to certain member groups only.

===No counting for this HTTP_USER_AGENT partial identifier===
You can set a custom UserAgent String in your browser and in the visitors module configuration.
 
* Layout -> Themes -> Modules -> Module Name (Contao 2.9)
* Layout -> Modules -> Module Name (TYPOlight 2.8.x)
In the field: "No counting for this HTTP_USER_AGENT partial identifier", you can enter a unique identifier. 
Example: CTISOK 
Save it. 
Now, change the User Agent String of Mozilla Firefox: 
# Type '''about:config''' in the Mozilla Firefox address bar and press ENTER,
# Type '''general.useragent.extra.firefox''' in the Filter bar,
# Double-click on the returned Firefox setting, where you can change a user agent string to overwrite the default.
# Add her "CTISOK" separated by space, e.g. "Firefox/3.5.2 CTISOK".

 
You can check your new User Agent String , type '''about:''' + ENTER in the Mozilla Firefox address bar and press ENTER, see last row. 
 
For other browsers, see:
[http://www.walkernews.net/2007/07/05/how-to-change-user-agent-string/ walkernews.net - how to change user agent string]
{{Hint|This does not work anymore in Firefox 4. Alternatively, use the add-on: [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ User-Agent-Switcher]}}

=Insert-Tags=
==Show the values==
From version 1.2.0 there is Insert-Tags to show the values.
<source lang="text">
{{visitors::catid::name}}
{{visitors::catid::online}}
{{visitors::catid::start}}
{{visitors::catid::totalvisit}}
{{visitors::catid::totalhit}}
{{visitors::catid::todayvisit}}
{{visitors::catid::todayhit}}
{{visitors::catid::averagevisits}}
</source>
From version 1.5.0 and from TYPOlight 2.8, Insert-Tags can be extended with prefix 'cache_'. Thus, these then cache resistant.
<source lang="text">
{{cache_visitors::catid::name}}
...
</source>
The counting is continued through the module! Who wants to use to display the insert tags, the module continues to need, but only to count. With the templates mod_visitors_fe_invisible the module may be invisible, if desired. 
To determine the category ID, go into the category overview of the module with your mouse over the "i". 
From version 2.3.1, the ID is shown right behind the category name. 

[[File:Visitors-package-category.jpg|Visitor category ID]]
 
The tooltip displays the ID. 
Or click on the "i", in the following site is in the first line the ID. 
For category ID = 1 that would be like that: 
<source lang="text">
{{visitors::1::online}}
</source>
 

==Count==
An alternative to "counting only" would be to use an Insert-Tag. From version 1.5.0 there is another Insert-Tag. The module itself uses this as well:
<source lang="text">
{{cache_visitors::catid::count}}
</source>
Example for installation in an article (for category ID = 1):
<source lang="html4strict">
{{cache_visitors::1::count}}
</source>

{{Caution|It must be noticed, that the insert-tag for the count will be installed at first on the page so that the counting is carried out before the identification of the values.}}

 

==More Insert-Tags==
From version 2.1.0, there ist Insert-Tags for display the values of the day with the most visitors.
<source lang="text">
{{visitors::catid::bestday::date}} - Day (Date) with the most visitors
{{visitors::catid::bestday::visits}} - Number of visitors of the day with most visitors
{{visitors::catid::bestday::hits}} - Number of hits of the day with most visitors
or
{{cache_visitors::catid::bestday::date}}
{{cache_visitors::catid::bestday::visits}}
{{cache_visitors::catid::bestday::hits}}
</source>
The "date" insert-tag has an optional parameter to format the date output. (m.d.Y , Y-m-d, etc.) 
The system setting is used as default. As a separator, a "::" are used. 
A complete example (with category 1):
<source lang="text">
Best Day: {{visitors::1::bestday::date::j. F Y}} with {{visitors::1::bestday::visits}} visitors
(and {{visitors::1::bestday::hits}} hits)
</source>
results:
Best Day: 31. August 2010 with 25 visitors (and 123 hits)

 

=Specific feature=
==No counting==
No front-end call is counted when one is logged on at the same time in the back end.
 

==Visitors per day: Ø = 0==
The average value per day will be calculated for each full calendar day. 
So, having only one day before a counting or a counting of the current day, no meaningful value can be calculated. 
(average = number visitors) 
In these cases appears "0".
 

==Bot Detection off==
Who wants to count the hits from bots and search engines can switch off the bot detection. This is done by the file localconfig.php.
{{Caution|This applies to all Visitors modules when several front end modules have been created!}}
The following entry to the end of localconfig.php (after: ### INSTALL SCRIPT STOP ### ) switching off the bot detection: 
<source lang="php">
$GLOBALS['TL_CONFIG']['mod_visitors_bot_check'] = false;
</source>
 

----
--[[User:BugBuster|BugBuster]] 00:42, 12 December 2010 (CET)

Backend User Online

2012-11-10T17:54:48Z

BugBuster: /* Using */

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
Shows in then back end the online status of the back end and front end user in the user / member overview.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.2.0 / 3.0.0
| Version=from 2.9
| TLVersion=2.7.2 - 2.8.4
| ERLink=http://http://contao.org/en/extension-list/view/backend_user_online.en.html
| TrackerLink=https://github.com/BugBuster1701/backend_user_online/issues
}}

[[de:Backend_User_Online]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/backend_user_online/issues Issue Tracker]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/backend_user_online.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/backend_user_online". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

=Using=
It expands the area of "Account manager" - "Members" and "Account manager" - "Users". 
For members it looks like this: 
[[File:Be_user_online_en_member.jpg|Backend User Online - Members]]

It represents the green eye "Online", the gray eyes "Offline".
 
For users it looks like this: 
[[File:Be_user_online_en_user.jpg|Backend User Online - Users]]

When you sort, as seen in the pictures, to "Last Login", this information can also be seen.
 

----
--[[User:BugBuster|BugBuster]] 18:54, 10 November 2012 (CET)

Backend User Online

2012-11-10T17:54:30Z

BugBuster: /* Using */

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
Shows in then back end the online status of the back end and front end user in the user / member overview.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.2.0 / 3.0.0
| Version=from 2.9
| TLVersion=2.7.2 - 2.8.4
| ERLink=http://http://contao.org/en/extension-list/view/backend_user_online.en.html
| TrackerLink=https://github.com/BugBuster1701/backend_user_online/issues
}}

[[de:Backend_User_Online]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/backend_user_online/issues Issue Tracker]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/backend_user_online.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/backend_user_online". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

=Using=
It expands the area of "Account manager" - "Members" and "Account manager" - "Users". 
For members it looks like this: 
[[File:Be_user_online_en_member.jpg|Backend User Online - Members]]

It represents the green eye "Online", the gray eyes "Offline".
 
For users it looks like this: 
[[File:Be_user_online_en_user.jpg|Backend User Online - Users]]

When you sort, as seen in the pictures, to "Last Login", this information can also be seen.
 

----
--[[User:BugBuster|BugBuster]] 23:33, 25 September 2010 (CEST)

File:Be user online en user.jpg

2012-11-10T17:51:31Z

BugBuster: uploaded a new version of "File:Be user online en user.jpg": Contao 3 Version

Back end user online - users

File:Be user online en member.jpg

2012-11-10T17:51:03Z

BugBuster: uploaded a new version of "File:Be user online en member.jpg": Contao 3 Version

Back end user online - members

Backend User Online

2012-11-10T17:41:40Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
Shows in then back end the online status of the back end and front end user in the user / member overview.

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.2.0 / 3.0.0
| Version=from 2.9
| TLVersion=2.7.2 - 2.8.4
| ERLink=http://http://contao.org/en/extension-list/view/backend_user_online.en.html
| TrackerLink=https://github.com/BugBuster1701/backend_user_online/issues
}}

[[de:Backend_User_Online]]
[[Category:Extensions]]

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum]
 
Errors and requests can be reported in the [https://github.com/BugBuster1701/backend_user_online/issues Issue Tracker]

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/extension-list/view/backend_user_online.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/backend_user_online". 
Then call /contao/install.php - Perform Update Database. 
( /typolight/install.php in older TYPOlight installations ) 

=Using=
It expands the area of "Account manager" - "Members" and "Account manager" - "Users". 
For members it looks like this: 
[[File:Be_user_online_en_member.jpg|Backend User Online - Members]]

It represents the green eye "Online", the gray eyes "Offline".
 
For users it looks like this: 
[[File:Be_user_online_en_user.jpg|Backend User Online - Users]]

It represents the green eye "Online", the gray eyes "Offline".
 

----
--[[User:BugBuster|BugBuster]] 23:33, 25 September 2010 (CEST)

Integrity Check

2012-09-03T18:02:37Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.1.0
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0*: minutely, hourly, daily, weekly, monthly
*Contao 3.0 Version still in development

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 14:14, 2 August 2012 (CEST)

File:Check overview en.jpg

2012-08-26T20:01:16Z

BugBuster: Ceck Overview

Ceck Overview

Integrity Check

2012-08-26T20:00:45Z

BugBuster:

'''''I'm not a native English speaker. Please correct my mistakes.'''''
 
[[File:check_overview_en.jpg|right|Integrity Check]] Integrity check for some files from Contao (Detection of hacked Contao installations.)

{{ExtInfo
| Dev=Glen Langer ([[User:BugBuster|BugBuster]])
| DevSite=http://www.contao.glen-langer.de
| ExtVersion=1.1.0 rc1
| Version=from 2.10.0
| ERLink=http://www.contao.org/en/extension-list/view/integrity_check.en.html
| TrackerLink=https://github.com/BugBuster1701/integrity_check/issues
}}
[[de:Integrity_Check]]
[[Category:Extensions]]

In Contao Forum, reports came about changed files, which malicious code was attached. 
The problem itself can not be attributed to a vulnerability in Contao, but will be distributed over other ways of the server, eg vulnerable WP plugins, hacked servers, hacked FTP logins, etc.

=Forum=
Questions about the Bot Detection module will be answered in [http://www.contao-community.org/viewforum.php?f=21 Forum] 
Errors and requests can be reported in the [https://github.com/BugBuster1701/integrity_check/issues Issue Tracker].

=Installation=
The installation of the module occurs about the extension Repository in back end of Contao. 
A manual installation is possible. [http://www.contao.org/en/extension-list/view/integrity_check.en.html Download] the ZIP file from Extension Repository, unzip and transfer it. 
A directory should have been created "/system/modules/integrity_check". 
Then call /contao/install.php - Perform Update Database. 

=Example of an Infection=
How now looks like such a hack? 
The attachment to the file index.php looked like this (shortened): 
<source lang="php">
#c3284d#
echo(gzinflate(base64_decode("ZZBNisMwDIX.......T7oD")));
#/c3284d#
</source>

Or like this (shortened): 
<source lang="javascript">
<script type="text/javascript">
function frmAdd() {
var ifrm = document.createElement('iframe');
....
};
window.onload = frmAdd;
</script>
</source>

==Site one the black list==
When you does not react fast enough, and Google notices this, the page is set to the "black list". Browsers like Firefox use this to warn against unauthorized access to it. It looks like this: 
[[File:site_on_black_list_en.jpg]]

=Function of the module=
In the current version, the most important PHP files are checked for modifications. 
This files will be checked:
* index.php
* cron.php (from version 1.1.0)
* contao/index.php
* contao/main.php

==Time of verification==
This test is performed automatically (Contao-Cron), see the section [[Integrity_Check#Technical_Details|Technical Details]].

==Detection==
The check is identical to the official Contao check tool, that means via MD5 checksums. Checksums are available for comparison for Contao from 2.10.0. 
From version 1.1.0, check via timestamps is possible.

==Using==
In the backend, you can see the results: System - System Log. Normally if everything is OK, no message appears. In its own module debug mode then there is only a message::
* Checking files for integrity is completed.
If modifications were detected, a message is generated for each file:
* Integrity status for file index.php is: Corrupt [MD5]
* Integrity status for cron.php file is corrupted [Timestamp]
** It was checked by time stamp, possible from version 1.1.0.
An information is available via System Log and mail, see the section [[Integrity_Check#Technical_Details|Technical Details]].

=Technical Details=
==Creating integrity check==
The integrity check need a check plan. This can be used for any of the files for the time, the art of check and the action. 

[[File:check_plan_en.jpg]]

===Time intervals===
* in Contao 2.10: daily, weekly, monthly
* in Contao 2.11: hourly, daily, weekly, monthly
* in Contao 3.0*: minutely, hourly, daily, weekly, monthly
*Contao 3.0 Version still in development

===Art of check===
The detection of a change in the file is possible via:
* MD5 checksum
* Timestamps

===Action===
* System log: Message in the system log (backend)
* Mail to Admin: a mail is sent to the admin of the Contao installation.
** It will then creates also automatically an entry in the System log (from version 1.1.0)

==Notes==
===System-Log und Mail===
From version 1.1.0 automatically gets an entry in the system log when a mail is sent. 
In Version 1.0.0, if you want to have both types of information, you creates the check twice, each with one of the actions: 

[[File:check_plan_2_en.jpg]]
 
Here is an example only for the index.php. This is of course also for the other files.

===There can be only one!===
It is possible in the integrity check overview to create multiple checks. It basically makes no sense. Therefore, it is ensured that there can be only an integrity check, which is activated. If you switch a new integrity check active, all other existing tests are automatically switched inactive.

==Protection against infection==
Well, a general protection is probably not possible. 
But there is a possibility that the malicious code is not executed. There is a ticket to GitHub, it is accepted for Contao 3. Here is the short info for Contao 2. 
Edit the index.php, go to the method "run" in the last line, should be the line of 269th (2.11.5) Before the curly bracket insert an exit; or insert a row for it. Here is from line 268 as an example:
<source lang="php">
}
}
</source>
change to:
<source lang="php">
}
exit;
}
</source>
Note: Now, the Integrity Check Tool as well as the Contao Check Tool report a change. Use the check vie timestamp now.

----
--[[User:BugBuster|BugBuster]] 14:14, 2 August 2012 (CEST)