The global options for the component can be found at:
Joomla Backend - System - Global Configuration - AttendanceLists


The most important language strings of the component are listed here. If you wish to change a certain expression, the corresponding language string used in the language override can be found here.



Here you can select which character sets are allowed to be entered in the text fields of the form view. It is recommended to select only those character sets that are really needed. This way spam from regions of the world that you do not wish to serve can be avoided.


Should versioning be enabled?


Here you can configure the routing how the URL is generated if SEF is enabled. The settings correspond to the possibilities of com_content.


In the frontend views of the component, certain functions are implemented using JavaScript. At certain points the JavaScript has to be paused for a few milliseconds using the timeout function. This setting determines how long the JavaScript should be paused.
A lower value makes the views loading faster, but depending on your system it is possible that certain functions may not work properly. (Setting only for experts!)

General component settings

General component settings



Here you can set how the date will be displayed. All available display options can be found at

Display Settings

Settings for displaying in the views


Message storage period

Here you define after how many days from the event date a message expires. Expired messages are marked as such and serve to indicate the administrator which messages could be deleted. This mechanism is intended to prevent messages with private data from being stored unnecessarily long. A system message can remind an administrator if expired messages exist and prompts him to delete the messages. Optionally, the system message can also be sent by e-mail. Or the automatic deletion function can be activated. Expired messages are then automatically deleted.

Set up a cron job

In order for the functionality of the expiring messages to be run correctly, it is necessary that the website is called up at least once per day. If the website generates too little traffic, so that this is not automatically the case, it is recommended to set up a cron job that calls up the website once a day.

How to create a Cron-Job?

Cron-Job Command

* * * * * wget -O - >/dev/null 2>&1

Privacy text

This is the setting for the data privacy check boxes of the component. Wherever a privacy check box is displayed, these setting will be applied. It is possible to define your custom data protection text to replace the default text. If no custom text has been entered, the data protection text is: I have read the privacy policy and agree to it. The word privacy policy is provided with a link to the privacy policy. The privacy URL in the settings defines the link behind the word privacy policy of the default privacy text.

Visibility of personal data

Here you will find the settings for the visibility of personal data - that is data submitted by event visitors. This personal data is displayed in the views AttendanceLists, single Message and Administration. You can define here which user group is allowed to view which personal data.

  • Public: This data is visible to everyone. Even unregistered users of the website are allowed to view this data.
  • Admins: This data is only visible to the owner of the message and logged-in users. Logged-in users additionally need the permission "show sensitive information".
  • User: This data is only visible to the owner of the message and to the Joomla SuperUser.
Privacy settings

Privacy settings


Here you will find the settings for the PDF generation. A logo can be selected, which will appear in the header of the document and its location within the header can be defined. If no logo is chosen, the Joomla-Logo will be used.
In addition a source text can be defined. The source text will appear in the footer of the document.

PDF settings

Settings for generating PDF files


The permissions of the individual user groups can be defined here. Below is a example configuration for three different user groups. It is the same configuration which is used for the demo.


User group of all not logged in website users. Not logged in users should be allowed to create messages and edit their own messages. You can edit your own messages by filling out the form again with the same information about your person, but with changed information. A conflict message will then appear in which the old message can be overwritten with the new message.

Permissions of the 'Public' user group

Permissions of the 'Public' user group


User group of all authors. This user group contains users who are supposed to manage the attendance lists. Additionally to the public users, these users are allowed to view the attendance list view and also delete the messages. They are also allowed to view everyone's sensitive data and output it in the attendance lists.

Permissions of the 'Admin' user group

Permissions of the 'Admin' user group


User group of all doorkeepers. This user group contains users who check the submitted messages of each event visitor at the entrance. In addition to the public users, these users are able to view all sensitive data and to give the messages time stamps. They confirm the received informations by giving a check-in time stamp with an entry time, and note the exit time with a check-out time stamp.

Permissions of the 'Doorkeeper' user group

Permissions of the 'Doorkeeper' user group


User group of all managers. This user group contains users who have full permissions to manage the messages. They can create, edit and delete messages, as well as create and delete check-ins and check-outs. The appropriate component view for this users is the administrator view.

Permissions of the 'Manager' user group

Permissions of the 'Manager' user group