https://en.contaowiki.org/api.php?action=feedcontributions&user=Webseven&feedformat=atomContao Community Documentation - User contributions [en]2024-03-28T12:25:04ZUser contributionsMediaWiki 1.22.6https://en.contaowiki.org/Contao.Dev_ExtensionsQuickpollContao.Dev ExtensionsQuickpoll2011-12-30T12:57:38Z<p>Webseven: </p>
<hr />
<div>{{stub}}<br />
= Quick Poll Module =<br />
This module allows you to set-up multiple polls in TYPOlight - each with their own '''Title, Description, Show Until date and Options''' -- options are the "answers" you want the user to choose from with a radio button group.<br />
<br />
The user is required to make a a choice on the form (with error if not) and when you submit the form, your vote is added to the database and the results of the poll are displayed in graphic format. The stop date closes the poll for voting, so only results are displayed.<br />
<br />
You are able to customize the look using different width algorithms and using CSS classes to change colors. <br />
{{Note|This Module allows you to create multiple polls at the same time, each with its own set of parameters.}}<br />
<br />
== Installation ==<br />
* Download and Install from [http://www.contao.org/extension-list/view/quickpoll.10080029.en.html Extension Repository]<br />
** [http://www.thyon.com/files/typolight/quickpoll/quickpoll-1.7.8-nl.zip dutch language files] _for version 1.7.8 by Anima-t3d<br />
** [http://www.thyon.com/files/typolight/quickpoll/quickpoll-1.7.6-de.zip german language files] _for version 1.7.6 by NoSi<br />
** [http://www.thyon.com/files/typolight/quickpoll/quickpoll-1.7.4-pl.zip polish language files] _for version 1.7.4 by qrczak<br />
<br />
== Create a new Quick Poll ==<br />
Click on the [[File:icon.gif]] QuickPoll icon in the Back-end Left Navigation Menu. You will see an sorted list of all your Quick Polls here - most likely, your screen will be empty. We'll add a new Quick Poll by clicking on (+) new Quick Poll icon at the top.<br />
{{Note|From v1.2 you can also reset the poll with the reset button - only visible to *Administrators*. This will also clear session and cookie values on the Admin machine. Cookies will have to be manually deleted on machines that would like to vote again after the reset.}}<br />
[[File:quickpoll-list.jpg|200px|thumb|none|quickpoll list]]<br />
<br />
== Edit the Quick Poll ==<br />
Here you enter the Title, e.g. Console Quick Poll -- the '''Description''', where you ask the question for the poll, e.g. What is your favourite gaming console? -- the '''Show Until Date''', which is your voting cut-off date (voting is disabled) and the '''Show Results Link''' which forces the display of a results link below the form. Finally your '''Options''', which is just a list of answers the user can vote for in the poll, e.g. Sony Playstation 3, Microsoft XBOX 360, Nintendo Wii, etc...<br />
{{Note|You enter 1 Option/Answer per line.}}<br />
<br />
[[File:quickpoll-edit.jpg|200px|thumb|none|quickpoll edit]]<br />
<br />
== Create a Module for your Quick Poll ==<br />
Go to the Modules Menu and then create a new '''Module''', give it a '''Module Name''', select Quick Poll as the '''Module Type''' and choose the '''QuickPoll Name''' you created above, by clicking on the correct radio button.<br />
<br />
You can then also choose the display template, e.g. qpoll_xxxxx.tpl. You can copy and create your own templates, by placing them in the (tl_root)/templates folder.<br />
<br />
[[File:quickpoll-module.jpg|200px|thumb|none|quickpoll module]]<br />
<br />
== Create a Quick Polls Archive ==<br />
As above, but instead select Quick Polls List in the Module Type. You can select how many items to show, e.g. 2 will show the 2 most recent completed poll results. You can also choose the display template as above, but one template will be used for all the polls in the archive list.<br />
<br />
[[File:quickpoll-archive.jpg|thumb|none|quickpoll archive]]<br />
<br />
== Find a Home for your Quick Poll Module ==<br />
Now you have two choices, you can:<br />
* add the Module as a CE (content element) to a specific Article on a Page (relating to a story)<br />
* add the Module directly to a page layout (to always show the latest poll on the front page)<br />
<br />
I'll show the first Article option in the screen below.<br />
{{Note|Remember to first create a Page in the Structure, then create a blank Article and then add the [[QuickPoll]] Module to the Article as a Content Element (CE)}}<br />
[[File:quickpoll-article.jpg|thumb|none|quickpoll article]]<br />
<br />
== The Quick Poll Voting Page ==<br />
When displayed in the front end, the Title, Description are listed with the options as a radio button group. If you selected the show results options, the results link will appear directly below the form.<br />
<br />
You will be able to select ONLY 1 value. If you don't select a value an error will be displayed when you try to submit the form.<br />
<br />
This is what the CSS-unformatted view will look like, but you can always pretty-it-up using your own CSS styles.<br />
{{Note|The Submit button contains the value: *Vote! * -- this is configurable in the language files.}}<br />
[[File:quickpoll-vote.jpg|200px|thumb|none|quickpoll vote]]<br />
<br />
== The QuickPoll Results Page ==<br />
Once you have voted (clicked submit), the system stores the result into the QuickPoll Database and displays a graphical view with percentages of the results. The total number of votes is also displayed. Each bar also has its percentage of the total in text, over the colored background bar. This is again very basic and CSS-unformatted. You can use CSS with colors to make it blend with your site.<br />
<br />
Here is a sample from the included quickpoll.css file, which you can copy/paste/modify into your site's css file.<br />
<br />
<source><br />
.mod_quickpoll .graph .results .color1 { color:#FFFFFF; background-color:#333333; text-align:center;}<br />
.mod_quickpoll .graph .results .color2 { color:#000000; background-color:#99CC33; text-align:center;}<br />
.mod_quickpoll .graph .results .color3 { color:#000000; background-color:#99CCFF; text-align:center;}<br />
.mod_quickpoll .graph .results .color4 { color:#000000; background-color:#FFFFCC; text-align:center;}<br />
.mod_quickpoll .graph .results .color5 { color:#000000; background-color:#FFCCCC; text-align:center;}<br />
</source><br />
<br />
You can also link the quickpoll.css file into your existing file, but I suggest you copy it before you import it, so that updates, don't overwrite changes you've made. Import CSS example:<br />
<br />
<source>@import "quickpoll.css";</source><br />
{{Note|The lines ''Poll end date: 2007-09-19'' and ''Total votes = 303'' - are both configurable in the language files using the format: }}<br />
<source>@Text %s Text@</source><br />
<br />
[[File:quickpoll-results.jpg|200px|thumb|none|quickpoll results]]<br />
<br />
== End Note about Session, Cookie, IP ==<br />
To prevent automated polls, the system stores _SESSION and _COOKIE values that prevent multiple votes. Nothing stops you from closing the browser, deleting the cookies and voting again. I do not store any per-vote data, e.g. IP addresses. Also IP's can be spoofed, by simply logging off from your wireless or ADSL session and then you get a new IP when you re-connect.<br />
<br />
*Happy Quick Poll! *</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogContao.Dev ExtensionsCatalog2011-12-30T12:55:41Z<p>Webseven: </p>
<hr />
<div>{{stub}}<br />
= Catalog Module Documentation =<br />
The Catalog and Catalog Extension modules are advanced modules and will require intermediate knowledge of PHP, HTML/CSS in order to create catalog that displays the way you really need it. To create advanced displays, you will need to understand PHP array structures provided in the TPL files. <br />
{{Caution|This is not a module for beginners.}}<br />
{{Hint|The Catalog module is a simple stop-gap to assist beginners with quickly getting up a custom application without having to write any code. However, the Catalog module is obviously NOT capable of working for all situations, at some point you have to get yourself dirty with PHP programming and just write your own TL applicationa, which is a bit of work and a lot of files, but easier than you might think.}}<br />
The Catalog System is currently divided into two modules (which will merge in the next release). You will have to install both catalog and catalogext to get all the features.<br />
<br />
The Catalog (main) module allows user to define and manage catalogs of items. The [http://tmp.contao.org/projects/typolight/wiki/CatalogExt CatalogExt adds] features and allows you to build powerful front-end modules to display and arrange the data in your catalog.<br />
<br />
Imagine you want to show to visitors of your site a list of your games. You may have many games, but all share certain attributes, like title, author, genre, console formats, release date, etc. You want to save all this information and later present it to visitors, let them show only games in the driving games genre, or games with price above a certain amount, only games that are available, etc. This module allows you to do just that.<br />
<br />
In this documentation we will create a catalog of computer and console games.<br />
<br />
== Installation ==<br />
* Download Catalog from [http://www.contao.org/extension-list/compat/any/tags/Catalog.html Extension Repository]<br />
* Download CatalogExt from [http://www.contao.org/extension-list/compat/any/tags/catalog%20extension.html Extension Repository]<br />
Install both packages from the Repository or download the ZIP and install files in their relative folders.<br />
<br />
== Reference Links ==<br />
* [ExtensionsCatalogExt Catalog Extension] module to create front-end modules<br />
* [TutorialsCatalog Catalog Templates Tutotial] explains advanced template customisation<br />
* [TutorialsCatalogMultiLanguage Catalog Multi-Language Tutorial] explains how to easily set-up multi-language catalogs<br />
<br />
== Site Examples ==<br />
[http://www.thyon.com/ Thyon Design] My own Client catalog (no reader, just list)<br />
[[File:catalog-site-thyon.jpg|200px|thumb|none|catalog site thyon]]<br />
[http://www.remaxteamaa.co.za/properties.html TeamAA Property Catalog] Property Website<br />
[[File:catalog-site-example1.jpg|200px|thumb|none|catalog site example 1]]<br />
[http://www.nags.co.za/locator.html National Auto Glass] Auto Glass Company -- with CSS hover-map<br />
[[File:catalog-site-nags.jpg|200px|thumb|none|catalog site nags]]<br />
[http://www.english-sofas.com/ English Sofa Company] Sofa Company<br />
[[File:catalog-site-sofa.jpg|200px|thumb|none|alt text]]<br />
[http://www.whitakeroil.com/products.html Whitaker Oil Company] Oil Chemicals<br />
[[File:catalog-site-whitaker.jpg|200px|thumb|none|catalog site whitaker]]<br />
<br />
== Create your Catalog ==<br />
The first step is to create the catalog of items. Click Catalog in the left menu and then click New catalog in the top action menu.<br />
<br />
The catalog list shows the name, item count and optionally the image thumbnail if set.<br />
[[File:catalog-type-list.jpg|200px|thumb|none|atalog type list]]<br />
<br />
Now fill the form as seen on image bellow. Name is only for your orientation, it is displayed in item types list. More important is Table name. It is the name of the table which will store your catalog data. Use only letters, numbers and underscore, but make sure table name does not start with number. Also some names are reserved, so you may obtain an error when creating item type. It is a good idea to add prefix to your tables like cat_, so that you know they belong to catalog, e.g. cat_mycatalogname<br />
<br />
{{Hint|If you prefix your catalog instead with tl_ the TYPOlight Database update tool thinks this is an application table without matching application files anywhere, so you will be asked to "Drop existing table". This will happen every time you install/uninstall an extension or perform an installation update. If you "Drop existing table" you will lose all your Catalog data. So its probably best to use the cat_ prefix that TL doesn't recognise as an internal system table.}}<br />
Leave the format title string empty for now, we get to that in a later section.<br />
<br />
You can also add an image and set its preview size (as in picture above). This will be displayed below the name of the catalog when you return to the catalog list.<br />
[[File:catalog-types.jpg|200px|thumb|none|catalog types]]<br />
<br />
Further down (installed by the Catalog Extension module), you will find additional parameters to set.<br />
<br />
=== Catalog Extension - additional catalog fields ===<br />
[[File:catalog_ext-config.jpg|200px|thumb|none|catalog ext config]]<br />
<br />
* Adds a JumpTo page to the Catalog, which will use the selected alias instead of id (creating nice SEO Urls) -- you will of course need to create fields first (as described further down), so once you have created an alias field, you can come back to this section to select it here.<br />
* Adds [x] Searchable to the Catalog, indexes each entry above using its alias and title as page title -- again, you will first need to setup fields so that the drop-down will show fields.<br />
Now click Save and close. Don't click Save and edit, because we need to define fields, before we can add our items. (As a matter of fact you can add items now, but they won't contain any useful information).<br />
<br />
== Define Catalog fields ==<br />
Next to the catalog you just created, click the Define fields button (shown on the image bellow).<br />
[[File:catalog-fields.jpg|200px|thumb|none|catalog fields]]<br />
<br />
After that the list of item type fields is displayed. It is currently empty. So go ahead and create new by clicking the New field button.<br />
<br />
After that the field definition dialog appears. You need to enter Label, Description and Column name. The rules for column name are the same as for the table name, so use only letters, numbers and underscore.<br />
<br />
Next you need to specify the type of item. Type tells what may user put into the field. For example if you want to store book title, you will choose field type text. If you want to store number of pages, use type number. If you want to add longer description, use longtext. After selecting type, you may further customize the field. I believe you will be able to figure out what type best serves what purpose.<br />
<br />
Valid field types are:<br />
* text - for titles and short heading<br />
* alias - creates unique text alias reference, based on a selected title field<br />
* longtext - for descriptions, with rich text support<br />
* number - integer numbers only (can be formatted)<br />
* decimal - floating point numbers (can be formatted)<br />
* date - dates, can be entered using a date calendar clicker (can be formatted)<br />
* checkbox - toggle states like published or archived (use as filter or hide sections when selected as controlling checkbox)<br />
* select - single selection drop-down from a database list (taxonomy module, another catalog or your own reference database)<br />
* tags - multi-select checkboxes from database list (taxonomy module, another catalog or your own reference database)<br />
* url - used to create e-mail and http links automatically<br />
* file - store file links or images (thumbnail support with width, height)<br />
You can also set various visual options like: insert break (field separation line), title field (shown in items list), filter (in BE), search (in BE), sort (in BE), grouping mode (in BE) and controlling checkbox (hides field below this checkbox).<br />
<br />
Then there are also other control options like: mandatory (field is then required), unique, default value and format (string, number, money, date formats supported).<br />
[[File:catalog-field-edit.jpg|200px|thumb|none|catalog field edit]]<br />
<br />
Now click Save and we have our first item field. Create as many fields as you want. The examples created the following fields:<br />
[[File:catalog-field-list2.jpg|200px|thumb|none|catalog field list2]]<br />
<br />
== Use the Taxonomy Module to create selectable options ==<br />
In order to create a quick reference for options like genres or formats you can simply create these in a tree within the taxonomy module and use them as input reference for a select or tags field type.<br />
<br />
Here is the Taxonomy module's configuration for this Games Catalog example:<br />
[[File:taxonomy-games.jpg|200px|thumb|none|taxonomy games]]<br />
<br />
To use the Taxonomy as a reference in Select and Tags field types, you have to choose the tl_taxonomy table as your reference.<br />
[[File:catalog-select-taxonomy.jpg|200px|thumb|none|alt text]]<br />
<br />
== Using Formatting on a text, number or decimal field == <br />
The formatting option allows you to format the field. Here are the ways in which to do it:<br />
* Text - enter sprintf format string (see "more more options): <br />
<source>Help on [%s":http://php.net/sprintf] => Help on [Space Invaders]</source><br />
* Number - enter decimals only, as TL configured separators are used<br />
<source>2 => 1,524.31</source><br />
* Date - enter date-time format (see "for more options): <br />
<source>Y-m-d H:i => 2009-03-02 17:34</source><br />
*Money - this function will most likely be deprecated, because not all PHP configurations are correctly set-up for the correct LOCALE, so 90% of the time, this php function doesn't work correctly.<br />
<br />
== Edit Catalog Items ==<br />
We have successfully defined fields for our catalog. Now it is time to create few catalog items.<br />
<br />
Select Catalog module again and you will see a list of item types defined. Click the Manage items button to add, delete and edit items.<br />
[[File:catalog-items-btn.jpg|200px|thumb|none|http://php.net/date]]<br />
<br />
Now create a new item by clicking the New item button in the header area. You see that the new item contains all the fields we defined and you may fill it in a very convenient way, just like in many other modules in Contao.<br />
[[File:catalog-item-edit.jpg|200px|thumb|none|catalog item edit]]<br />
<br />
== Back-end Custom Item Display ==<br />
You can now also customize your catalog entries using a new feature in version 0.3.0. In the back-end you can define the format string in the catalog type definition (see using Catalog Module). Although values are already formatted using the catalog definition (format string), this format string additionally allows you to create thumbnails, wrap values in bold, italic. Actually any HTML is allowed.<br />
{{Note|Ensure that all fields you want to use in the Back-end display with this '''format title string''', have been selected as ''[x] Title field'' in their individual field definitions.}}<br />
Below is an example of what you can achieve.<br />
<br />
First, enter the code in the Catalog Type definition of Format title string:<br />
<source><strong>{{title}}</strong> - {{price}} <em>[{{releasedate}}]</em> {{archived::src=all.gif}} {{archived}}<br /> {{image::w=60&h=80}}</source><br />
<br />
== Catalog Permissions ==<br />
The Catalog application is integrated into the TYPOlight user permissions system and will allow you to set permissions for editing items within User and User Groups (for Back-end). You will be able to restrict who can edit which Catalog.<br />
<br />
<source><code class="div"><br />
Only the Administrator can create, edit or modify field types, so you cannot give a User permissions to change the catalog's table structures.<br />
</code></source><br />
<br />
== Front-End Modules using the Catalog Extension ==<br />
<br />
Catalog Extension modules:<br />
<br />
* Catalog Filter Module: build your filter on field values, range, date, search.<br />
* Catalog List Module: displays a list of items responding to the filter above.<br />
* Catalog Reader: displays item detail view + reference info (jump links to other catalogs).<br />
* Catalog Notify: creates contact form for clients to send contact info on catalog item (used on reader page)<br />
* Catalog Featured: selectable number of (random) items filtered by a preset condition.<br />
* Catalog Related: show related catalog items (except current) with selectable matching parameters.<br />
* Catalog Reference: show child catalog items where a selected reference field is matching the current viewed parent item.<br />
<br />
You may continue configuring your catalog using the documentation for the [ExtensionsCatalogExt Catalog Extension] module to create the front-end modules listed above.</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogDevContao.Dev ExtensionsCatalogDev2011-12-30T12:53:02Z<p>Webseven: Created page with '{{stub}} = Catalog Extension Development = {{Note|This is not a substitute for proper tracking, but provides a means for TL users to add items.}} == Reference Links == * [http://…'</p>
<hr />
<div>{{stub}}<br />
= Catalog Extension Development =<br />
{{Note|This is not a substitute for proper tracking, but provides a means for TL users to add items.}}<br />
== Reference Links ==<br />
* [http://dev.typolight.org/wiki/ExtensionsCatalog Catalog module] to create back-end data and default formatting<br />
* [http://dev.typolight.org/wiki/ExtensionsCatalogExt Catalog Extension module] to create front-end modules<br />
* [http://dev.typolight.org/wiki/TutorialsCatalog Catalog Templates Tutotial] explains advanced template customisation<br />
== Bugs ==<br />
* Select/Tags - add stored value (default = id): will allow correct sorting in BE<br />
== Feature Requests ==<br />
'''HIGH'''<br />
* Add Flatten Tree option: [SELECT] and [CHECKBOX]<br />
'''MEDIUM'''<br />
* Link wrap field to all listing modules<br />
* Enable Catalog Featured to respond to Catalog Filter<br />
* Catalog Navigation Module<br />
* Catalog Comments Module<br />
* Catalog Compare Module (as function of Catalog List/Reader?)<br />
'''LOW'''<br />
* Catalog Edit Module<br />
* parseFiles() -- sort on meta.txt or provide sorting options to image/file field<br />
=== NEW ===<br />
* Add your item here …</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogContao.Dev ExtensionsCatalog2011-12-30T11:01:30Z<p>Webseven: /* Edit Catalog Items */</p>
<hr />
<div>{{stub}}<br />
<br />
= Catalog Module Documentation =<br />
The Catalog and Catalog Extension modules are advanced modules and will require intermediate knowledge of PHP, HTML/CSS in order to create catalog that displays the way you really need it. To create advanced displays, you will need to understand PHP array structures provided in the TPL files. <br />
{{Caution|This is not a module for beginners.}}<br />
{{Hint|The Catalog module is a simple stop-gap to assist beginners with quickly getting up a custom application without having to write any code. However, the Catalog module is obviously NOT capable of working for all situations, at some point you have to get yourself dirty with PHP programming and just write your own TL applicationa, which is a bit of work and a lot of files, but easier than you might think.}}<br />
The Catalog System is currently divided into two modules (which will merge in the next release). You will have to install both catalog and catalogext to get all the features.<br />
<br />
The Catalog (main) module allows user to define and manage catalogs of items. The [http://tmp.contao.org/projects/typolight/wiki/CatalogExt CatalogExt adds] features and allows you to build powerful front-end modules to display and arrange the data in your catalog.<br />
<br />
Imagine you want to show to visitors of your site a list of your games. You may have many games, but all share certain attributes, like title, author, genre, console formats, release date, etc. You want to save all this information and later present it to visitors, let them show only games in the driving games genre, or games with price above a certain amount, only games that are available, etc. This module allows you to do just that.<br />
<br />
In this documentation we will create a catalog of computer and console games.<br />
<br />
== Installation ==<br />
* Download Catalog from [http://www.contao.org/extension-list/compat/any/tags/Catalog.html Extension Repository]<br />
* Download CatalogExt from [http://www.contao.org/extension-list/compat/any/tags/catalog%20extension.html Extension Repository]<br />
Install both packages from the Repository or download the ZIP and install files in their relative folders.<br />
<br />
== Reference Links ==<br />
* [ExtensionsCatalogExt Catalog Extension] module to create front-end modules<br />
* [TutorialsCatalog Catalog Templates Tutotial] explains advanced template customisation<br />
* [TutorialsCatalogMultiLanguage Catalog Multi-Language Tutorial] explains how to easily set-up multi-language catalogs<br />
<br />
== Site Examples ==<br />
[http://www.thyon.com/ Thyon Design] My own Client catalog (no reader, just list)<br />
[[File:catalog-site-thyon.jpg|200px|thumb|none|catalog site thyon]]<br />
[http://www.remaxteamaa.co.za/properties.html TeamAA Property Catalog] Property Website<br />
[[File:catalog-site-example1.jpg|200px|thumb|none|catalog site example 1]]<br />
[http://www.nags.co.za/locator.html National Auto Glass] Auto Glass Company -- with CSS hover-map<br />
[[File:catalog-site-nags.jpg|200px|thumb|none|catalog site nags]]<br />
[http://www.english-sofas.com/ English Sofa Company] Sofa Company<br />
[[File:catalog-site-sofa.jpg|200px|thumb|none|alt text]]<br />
[http://www.whitakeroil.com/products.html Whitaker Oil Company] Oil Chemicals<br />
[[File:catalog-site-whitaker.jpg|200px|thumb|none|catalog site whitaker]]<br />
<br />
== Create your Catalog ==<br />
The first step is to create the catalog of items. Click Catalog in the left menu and then click New catalog in the top action menu.<br />
<br />
The catalog list shows the name, item count and optionally the image thumbnail if set.<br />
[[File:catalog-type-list.jpg|200px|thumb|none|atalog type list]]<br />
<br />
Now fill the form as seen on image bellow. Name is only for your orientation, it is displayed in item types list. More important is Table name. It is the name of the table which will store your catalog data. Use only letters, numbers and underscore, but make sure table name does not start with number. Also some names are reserved, so you may obtain an error when creating item type. It is a good idea to add prefix to your tables like cat_, so that you know they belong to catalog, e.g. cat_mycatalogname<br />
<br />
{{Hint|If you prefix your catalog instead with tl_ the TYPOlight Database update tool thinks this is an application table without matching application files anywhere, so you will be asked to "Drop existing table". This will happen every time you install/uninstall an extension or perform an installation update. If you "Drop existing table" you will lose all your Catalog data. So its probably best to use the cat_ prefix that TL doesn't recognise as an internal system table.}}<br />
Leave the format title string empty for now, we get to that in a later section.<br />
<br />
You can also add an image and set its preview size (as in picture above). This will be displayed below the name of the catalog when you return to the catalog list.<br />
[[File:catalog-types.jpg|200px|thumb|none|catalog types]]<br />
<br />
Further down (installed by the Catalog Extension module), you will find additional parameters to set.<br />
<br />
=== Catalog Extension - additional catalog fields ===<br />
[[File:catalog_ext-config.jpg|200px|thumb|none|catalog ext config]]<br />
<br />
* Adds a JumpTo page to the Catalog, which will use the selected alias instead of id (creating nice SEO Urls) -- you will of course need to create fields first (as described further down), so once you have created an alias field, you can come back to this section to select it here.<br />
* Adds [x] Searchable to the Catalog, indexes each entry above using its alias and title as page title -- again, you will first need to setup fields so that the drop-down will show fields.<br />
Now click Save and close. Don't click Save and edit, because we need to define fields, before we can add our items. (As a matter of fact you can add items now, but they won't contain any useful information).<br />
<br />
== Define Catalog fields ==<br />
Next to the catalog you just created, click the Define fields button (shown on the image bellow).<br />
[[File:catalog-fields.jpg|200px|thumb|none|catalog fields]]<br />
<br />
After that the list of item type fields is displayed. It is currently empty. So go ahead and create new by clicking the New field button.<br />
<br />
After that the field definition dialog appears. You need to enter Label, Description and Column name. The rules for column name are the same as for the table name, so use only letters, numbers and underscore.<br />
<br />
Next you need to specify the type of item. Type tells what may user put into the field. For example if you want to store book title, you will choose field type text. If you want to store number of pages, use type number. If you want to add longer description, use longtext. After selecting type, you may further customize the field. I believe you will be able to figure out what type best serves what purpose.<br />
<br />
Valid field types are:<br />
* text - for titles and short heading<br />
* alias - creates unique text alias reference, based on a selected title field<br />
* longtext - for descriptions, with rich text support<br />
* number - integer numbers only (can be formatted)<br />
* decimal - floating point numbers (can be formatted)<br />
* date - dates, can be entered using a date calendar clicker (can be formatted)<br />
* checkbox - toggle states like published or archived (use as filter or hide sections when selected as controlling checkbox)<br />
* select - single selection drop-down from a database list (taxonomy module, another catalog or your own reference database)<br />
* tags - multi-select checkboxes from database list (taxonomy module, another catalog or your own reference database)<br />
* url - used to create e-mail and http links automatically<br />
* file - store file links or images (thumbnail support with width, height)<br />
You can also set various visual options like: insert break (field separation line), title field (shown in items list), filter (in BE), search (in BE), sort (in BE), grouping mode (in BE) and controlling checkbox (hides field below this checkbox).<br />
<br />
Then there are also other control options like: mandatory (field is then required), unique, default value and format (string, number, money, date formats supported).<br />
[[File:catalog-field-edit.jpg|200px|thumb|none|catalog field edit]]<br />
<br />
Now click Save and we have our first item field. Create as many fields as you want. The examples created the following fields:<br />
[[File:catalog-field-list2.jpg|200px|thumb|none|catalog field list2]]<br />
<br />
== Use the Taxonomy Module to create selectable options ==<br />
In order to create a quick reference for options like genres or formats you can simply create these in a tree within the taxonomy module and use them as input reference for a select or tags field type.<br />
<br />
Here is the Taxonomy module's configuration for this Games Catalog example:<br />
[[File:taxonomy-games.jpg|200px|thumb|none|taxonomy games]]<br />
<br />
To use the Taxonomy as a reference in Select and Tags field types, you have to choose the tl_taxonomy table as your reference.<br />
[[File:catalog-select-taxonomy.jpg|200px|thumb|none|alt text]]<br />
<br />
== Using Formatting on a text, number or decimal field == <br />
The formatting option allows you to format the field. Here are the ways in which to do it:<br />
* Text - enter sprintf format string (see "more more options): <br />
<source>Help on [%s":http://php.net/sprintf] => Help on [Space Invaders]</source><br />
* Number - enter decimals only, as TL configured separators are used<br />
<source>2 => 1,524.31</source><br />
* Date - enter date-time format (see "for more options): <br />
<source>Y-m-d H:i => 2009-03-02 17:34</source><br />
*Money - this function will most likely be deprecated, because not all PHP configurations are correctly set-up for the correct LOCALE, so 90% of the time, this php function doesn't work correctly.<br />
<br />
== Edit Catalog Items ==<br />
We have successfully defined fields for our catalog. Now it is time to create few catalog items.<br />
<br />
Select Catalog module again and you will see a list of item types defined. Click the Manage items button to add, delete and edit items.<br />
[[File:catalog-items-btn.jpg|200px|thumb|none|http://php.net/date]]<br />
<br />
Now create a new item by clicking the New item button in the header area. You see that the new item contains all the fields we defined and you may fill it in a very convenient way, just like in many other modules in Contao.<br />
[[File:catalog-item-edit.jpg|200px|thumb|none|catalog item edit]]<br />
<br />
== Back-end Custom Item Display ==<br />
You can now also customize your catalog entries using a new feature in version 0.3.0. In the back-end you can define the format string in the catalog type definition (see using Catalog Module). Although values are already formatted using the catalog definition (format string), this format string additionally allows you to create thumbnails, wrap values in bold, italic. Actually any HTML is allowed.<br />
{{Note|Ensure that all fields you want to use in the Back-end display with this '''format title string''', have been selected as ''[x] Title field'' in their individual field definitions.}}<br />
Below is an example of what you can achieve.<br />
<br />
First, enter the code in the Catalog Type definition of Format title string:<br />
<source><strong>{{title}}</strong> - {{price}} <em>[{{releasedate}}]</em> {{archived::src=all.gif}} {{archived}}<br /> {{image::w=60&h=80}}</source><br />
<br />
== Catalog Permissions ==<br />
The Catalog application is integrated into the TYPOlight user permissions system and will allow you to set permissions for editing items within User and User Groups (for Back-end). You will be able to restrict who can edit which Catalog.<br />
<br />
<source><code class="div"><br />
Only the Administrator can create, edit or modify field types, so you cannot give a User permissions to change the catalog's table structures.<br />
</code></source><br />
<br />
== Front-End Modules using the Catalog Extension ==<br />
<br />
Catalog Extension modules:<br />
<br />
* Catalog Filter Module: build your filter on field values, range, date, search.<br />
* Catalog List Module: displays a list of items responding to the filter above.<br />
* Catalog Reader: displays item detail view + reference info (jump links to other catalogs).<br />
* Catalog Notify: creates contact form for clients to send contact info on catalog item (used on reader page)<br />
* Catalog Featured: selectable number of (random) items filtered by a preset condition.<br />
* Catalog Related: show related catalog items (except current) with selectable matching parameters.<br />
* Catalog Reference: show child catalog items where a selected reference field is matching the current viewed parent item.<br />
<br />
You may continue configuring your catalog using the documentation for the [ExtensionsCatalogExt Catalog Extension] module to create the front-end modules listed above.</div>Websevenhttps://en.contaowiki.org/File:Catalog-item-edit.jpgFile:Catalog-item-edit.jpg2011-12-30T10:57:18Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogContao.Dev ExtensionsCatalog2011-12-30T10:56:06Z<p>Webseven: /* Edit Catalog Items */</p>
<hr />
<div>{{stub}}<br />
<br />
= Catalog Module Documentation =<br />
The Catalog and Catalog Extension modules are advanced modules and will require intermediate knowledge of PHP, HTML/CSS in order to create catalog that displays the way you really need it. To create advanced displays, you will need to understand PHP array structures provided in the TPL files. <br />
{{Caution|This is not a module for beginners.}}<br />
{{Hint|The Catalog module is a simple stop-gap to assist beginners with quickly getting up a custom application without having to write any code. However, the Catalog module is obviously NOT capable of working for all situations, at some point you have to get yourself dirty with PHP programming and just write your own TL applicationa, which is a bit of work and a lot of files, but easier than you might think.}}<br />
The Catalog System is currently divided into two modules (which will merge in the next release). You will have to install both catalog and catalogext to get all the features.<br />
<br />
The Catalog (main) module allows user to define and manage catalogs of items. The [http://tmp.contao.org/projects/typolight/wiki/CatalogExt CatalogExt adds] features and allows you to build powerful front-end modules to display and arrange the data in your catalog.<br />
<br />
Imagine you want to show to visitors of your site a list of your games. You may have many games, but all share certain attributes, like title, author, genre, console formats, release date, etc. You want to save all this information and later present it to visitors, let them show only games in the driving games genre, or games with price above a certain amount, only games that are available, etc. This module allows you to do just that.<br />
<br />
In this documentation we will create a catalog of computer and console games.<br />
<br />
== Installation ==<br />
* Download Catalog from [http://www.contao.org/extension-list/compat/any/tags/Catalog.html Extension Repository]<br />
* Download CatalogExt from [http://www.contao.org/extension-list/compat/any/tags/catalog%20extension.html Extension Repository]<br />
Install both packages from the Repository or download the ZIP and install files in their relative folders.<br />
<br />
== Reference Links ==<br />
* [ExtensionsCatalogExt Catalog Extension] module to create front-end modules<br />
* [TutorialsCatalog Catalog Templates Tutotial] explains advanced template customisation<br />
* [TutorialsCatalogMultiLanguage Catalog Multi-Language Tutorial] explains how to easily set-up multi-language catalogs<br />
<br />
== Site Examples ==<br />
[http://www.thyon.com/ Thyon Design] My own Client catalog (no reader, just list)<br />
[[File:catalog-site-thyon.jpg|200px|thumb|none|catalog site thyon]]<br />
[http://www.remaxteamaa.co.za/properties.html TeamAA Property Catalog] Property Website<br />
[[File:catalog-site-example1.jpg|200px|thumb|none|catalog site example 1]]<br />
[http://www.nags.co.za/locator.html National Auto Glass] Auto Glass Company -- with CSS hover-map<br />
[[File:catalog-site-nags.jpg|200px|thumb|none|catalog site nags]]<br />
[http://www.english-sofas.com/ English Sofa Company] Sofa Company<br />
[[File:catalog-site-sofa.jpg|200px|thumb|none|alt text]]<br />
[http://www.whitakeroil.com/products.html Whitaker Oil Company] Oil Chemicals<br />
[[File:catalog-site-whitaker.jpg|200px|thumb|none|catalog site whitaker]]<br />
<br />
== Create your Catalog ==<br />
The first step is to create the catalog of items. Click Catalog in the left menu and then click New catalog in the top action menu.<br />
<br />
The catalog list shows the name, item count and optionally the image thumbnail if set.<br />
[[File:catalog-type-list.jpg|200px|thumb|none|atalog type list]]<br />
<br />
Now fill the form as seen on image bellow. Name is only for your orientation, it is displayed in item types list. More important is Table name. It is the name of the table which will store your catalog data. Use only letters, numbers and underscore, but make sure table name does not start with number. Also some names are reserved, so you may obtain an error when creating item type. It is a good idea to add prefix to your tables like cat_, so that you know they belong to catalog, e.g. cat_mycatalogname<br />
<br />
{{Hint|If you prefix your catalog instead with tl_ the TYPOlight Database update tool thinks this is an application table without matching application files anywhere, so you will be asked to "Drop existing table". This will happen every time you install/uninstall an extension or perform an installation update. If you "Drop existing table" you will lose all your Catalog data. So its probably best to use the cat_ prefix that TL doesn't recognise as an internal system table.}}<br />
Leave the format title string empty for now, we get to that in a later section.<br />
<br />
You can also add an image and set its preview size (as in picture above). This will be displayed below the name of the catalog when you return to the catalog list.<br />
[[File:catalog-types.jpg|200px|thumb|none|catalog types]]<br />
<br />
Further down (installed by the Catalog Extension module), you will find additional parameters to set.<br />
<br />
=== Catalog Extension - additional catalog fields ===<br />
[[File:catalog_ext-config.jpg|200px|thumb|none|catalog ext config]]<br />
<br />
* Adds a JumpTo page to the Catalog, which will use the selected alias instead of id (creating nice SEO Urls) -- you will of course need to create fields first (as described further down), so once you have created an alias field, you can come back to this section to select it here.<br />
* Adds [x] Searchable to the Catalog, indexes each entry above using its alias and title as page title -- again, you will first need to setup fields so that the drop-down will show fields.<br />
Now click Save and close. Don't click Save and edit, because we need to define fields, before we can add our items. (As a matter of fact you can add items now, but they won't contain any useful information).<br />
<br />
== Define Catalog fields ==<br />
Next to the catalog you just created, click the Define fields button (shown on the image bellow).<br />
[[File:catalog-fields.jpg|200px|thumb|none|catalog fields]]<br />
<br />
After that the list of item type fields is displayed. It is currently empty. So go ahead and create new by clicking the New field button.<br />
<br />
After that the field definition dialog appears. You need to enter Label, Description and Column name. The rules for column name are the same as for the table name, so use only letters, numbers and underscore.<br />
<br />
Next you need to specify the type of item. Type tells what may user put into the field. For example if you want to store book title, you will choose field type text. If you want to store number of pages, use type number. If you want to add longer description, use longtext. After selecting type, you may further customize the field. I believe you will be able to figure out what type best serves what purpose.<br />
<br />
Valid field types are:<br />
* text - for titles and short heading<br />
* alias - creates unique text alias reference, based on a selected title field<br />
* longtext - for descriptions, with rich text support<br />
* number - integer numbers only (can be formatted)<br />
* decimal - floating point numbers (can be formatted)<br />
* date - dates, can be entered using a date calendar clicker (can be formatted)<br />
* checkbox - toggle states like published or archived (use as filter or hide sections when selected as controlling checkbox)<br />
* select - single selection drop-down from a database list (taxonomy module, another catalog or your own reference database)<br />
* tags - multi-select checkboxes from database list (taxonomy module, another catalog or your own reference database)<br />
* url - used to create e-mail and http links automatically<br />
* file - store file links or images (thumbnail support with width, height)<br />
You can also set various visual options like: insert break (field separation line), title field (shown in items list), filter (in BE), search (in BE), sort (in BE), grouping mode (in BE) and controlling checkbox (hides field below this checkbox).<br />
<br />
Then there are also other control options like: mandatory (field is then required), unique, default value and format (string, number, money, date formats supported).<br />
[[File:catalog-field-edit.jpg|200px|thumb|none|catalog field edit]]<br />
<br />
Now click Save and we have our first item field. Create as many fields as you want. The examples created the following fields:<br />
[[File:catalog-field-list2.jpg|200px|thumb|none|catalog field list2]]<br />
<br />
== Use the Taxonomy Module to create selectable options ==<br />
In order to create a quick reference for options like genres or formats you can simply create these in a tree within the taxonomy module and use them as input reference for a select or tags field type.<br />
<br />
Here is the Taxonomy module's configuration for this Games Catalog example:<br />
[[File:taxonomy-games.jpg|200px|thumb|none|taxonomy games]]<br />
<br />
To use the Taxonomy as a reference in Select and Tags field types, you have to choose the tl_taxonomy table as your reference.<br />
[[File:catalog-select-taxonomy.jpg|200px|thumb|none|alt text]]<br />
<br />
== Using Formatting on a text, number or decimal field == <br />
The formatting option allows you to format the field. Here are the ways in which to do it:<br />
* Text - enter sprintf format string (see "more more options): <br />
<source>Help on [%s":http://php.net/sprintf] => Help on [Space Invaders]</source><br />
* Number - enter decimals only, as TL configured separators are used<br />
<source>2 => 1,524.31</source><br />
* Date - enter date-time format (see "for more options): <br />
<source>Y-m-d H:i => 2009-03-02 17:34</source><br />
*Money - this function will most likely be deprecated, because not all PHP configurations are correctly set-up for the correct LOCALE, so 90% of the time, this php function doesn't work correctly.<br />
<br />
== Edit Catalog Items ==<br />
We have successfully defined fields for our catalog. Now it is time to create few catalog items.<br />
<br />
Select Catalog module again and you will see a list of item types defined. Click the Manage items button to add, delete and edit items.<br />
[[File:catalog-items-btn.jpg|200px|thumb|none|http://php.net/date]]<br />
<br />
Now create a new item by clicking the New item button in the header area. You see that the new item contains all the fields we defined and you may fill it in a very convenient way, just like in many other modules in Contao.<br />
[[File:catalog-item-edit.jpg|200px|thumb|none|catalog item edit]]<br />
<br />
Back-end Custom Item Display<br />
You can now also customize your catalog entries using a new feature in version 0.3.0. In the back-end you can define the format string in the catalog type definition (see using Catalog Module). Although values are already formatted using the catalog definition (format string), this format string additionally allows you to create thumbnails, wrap values in bold, italic. Actually any HTML is allowed.<br />
<br />
{{Note|Ensure that all fields you want to use in the Back-end display with this *format title string*, have been selected as *@[x] Title field@* in their individual field definitions.}}<br />
Below is an example of what you can achieve.<br />
<br />
First, enter the code in the Catalog Type definition of Format title string:<br />
<source><strong>{{title}}</strong> - {{price}} <em>[{{releasedate}}]</em> {{archived::src=all.gif}} {{archived}}<br /> {{image::w=60&h=80}}</source><br />
<br />
== Catalog Permissions ==<br />
The Catalog application is integrated into the TYPOlight user permissions system and will allow you to set permissions for editing items within User and User Groups (for Back-end). You will be able to restrict who can edit which Catalog.<br />
<br />
<source><code class="div"><br />
Only the Administrator can create, edit or modify field types, so you cannot give a User permissions to change the catalog's table structures.<br />
</code></source><br />
<br />
== Front-End Modules using the Catalog Extension ==<br />
<br />
Catalog Extension modules:<br />
<br />
* Catalog Filter Module: build your filter on field values, range, date, search.<br />
* Catalog List Module: displays a list of items responding to the filter above.<br />
* Catalog Reader: displays item detail view + reference info (jump links to other catalogs).<br />
* Catalog Notify: creates contact form for clients to send contact info on catalog item (used on reader page)<br />
* Catalog Featured: selectable number of (random) items filtered by a preset condition.<br />
* Catalog Related: show related catalog items (except current) with selectable matching parameters.<br />
* Catalog Reference: show child catalog items where a selected reference field is matching the current viewed parent item.<br />
<br />
You may continue configuring your catalog using the documentation for the [ExtensionsCatalogExt Catalog Extension] module to create the front-end modules listed above.</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogContao.Dev ExtensionsCatalog2011-12-30T10:53:58Z<p>Webseven: </p>
<hr />
<div>{{stub}}<br />
<br />
= Catalog Module Documentation =<br />
The Catalog and Catalog Extension modules are advanced modules and will require intermediate knowledge of PHP, HTML/CSS in order to create catalog that displays the way you really need it. To create advanced displays, you will need to understand PHP array structures provided in the TPL files. <br />
{{Caution|This is not a module for beginners.}}<br />
{{Hint|The Catalog module is a simple stop-gap to assist beginners with quickly getting up a custom application without having to write any code. However, the Catalog module is obviously NOT capable of working for all situations, at some point you have to get yourself dirty with PHP programming and just write your own TL applicationa, which is a bit of work and a lot of files, but easier than you might think.}}<br />
The Catalog System is currently divided into two modules (which will merge in the next release). You will have to install both catalog and catalogext to get all the features.<br />
<br />
The Catalog (main) module allows user to define and manage catalogs of items. The [http://tmp.contao.org/projects/typolight/wiki/CatalogExt CatalogExt adds] features and allows you to build powerful front-end modules to display and arrange the data in your catalog.<br />
<br />
Imagine you want to show to visitors of your site a list of your games. You may have many games, but all share certain attributes, like title, author, genre, console formats, release date, etc. You want to save all this information and later present it to visitors, let them show only games in the driving games genre, or games with price above a certain amount, only games that are available, etc. This module allows you to do just that.<br />
<br />
In this documentation we will create a catalog of computer and console games.<br />
<br />
== Installation ==<br />
* Download Catalog from [http://www.contao.org/extension-list/compat/any/tags/Catalog.html Extension Repository]<br />
* Download CatalogExt from [http://www.contao.org/extension-list/compat/any/tags/catalog%20extension.html Extension Repository]<br />
Install both packages from the Repository or download the ZIP and install files in their relative folders.<br />
<br />
== Reference Links ==<br />
* [ExtensionsCatalogExt Catalog Extension] module to create front-end modules<br />
* [TutorialsCatalog Catalog Templates Tutotial] explains advanced template customisation<br />
* [TutorialsCatalogMultiLanguage Catalog Multi-Language Tutorial] explains how to easily set-up multi-language catalogs<br />
<br />
== Site Examples ==<br />
[http://www.thyon.com/ Thyon Design] My own Client catalog (no reader, just list)<br />
[[File:catalog-site-thyon.jpg|200px|thumb|none|catalog site thyon]]<br />
[http://www.remaxteamaa.co.za/properties.html TeamAA Property Catalog] Property Website<br />
[[File:catalog-site-example1.jpg|200px|thumb|none|catalog site example 1]]<br />
[http://www.nags.co.za/locator.html National Auto Glass] Auto Glass Company -- with CSS hover-map<br />
[[File:catalog-site-nags.jpg|200px|thumb|none|catalog site nags]]<br />
[http://www.english-sofas.com/ English Sofa Company] Sofa Company<br />
[[File:catalog-site-sofa.jpg|200px|thumb|none|alt text]]<br />
[http://www.whitakeroil.com/products.html Whitaker Oil Company] Oil Chemicals<br />
[[File:catalog-site-whitaker.jpg|200px|thumb|none|catalog site whitaker]]<br />
<br />
== Create your Catalog ==<br />
The first step is to create the catalog of items. Click Catalog in the left menu and then click New catalog in the top action menu.<br />
<br />
The catalog list shows the name, item count and optionally the image thumbnail if set.<br />
[[File:catalog-type-list.jpg|200px|thumb|none|atalog type list]]<br />
<br />
Now fill the form as seen on image bellow. Name is only for your orientation, it is displayed in item types list. More important is Table name. It is the name of the table which will store your catalog data. Use only letters, numbers and underscore, but make sure table name does not start with number. Also some names are reserved, so you may obtain an error when creating item type. It is a good idea to add prefix to your tables like cat_, so that you know they belong to catalog, e.g. cat_mycatalogname<br />
<br />
{{Hint|If you prefix your catalog instead with tl_ the TYPOlight Database update tool thinks this is an application table without matching application files anywhere, so you will be asked to "Drop existing table". This will happen every time you install/uninstall an extension or perform an installation update. If you "Drop existing table" you will lose all your Catalog data. So its probably best to use the cat_ prefix that TL doesn't recognise as an internal system table.}}<br />
Leave the format title string empty for now, we get to that in a later section.<br />
<br />
You can also add an image and set its preview size (as in picture above). This will be displayed below the name of the catalog when you return to the catalog list.<br />
[[File:catalog-types.jpg|200px|thumb|none|catalog types]]<br />
<br />
Further down (installed by the Catalog Extension module), you will find additional parameters to set.<br />
<br />
=== Catalog Extension - additional catalog fields ===<br />
[[File:catalog_ext-config.jpg|200px|thumb|none|catalog ext config]]<br />
<br />
* Adds a JumpTo page to the Catalog, which will use the selected alias instead of id (creating nice SEO Urls) -- you will of course need to create fields first (as described further down), so once you have created an alias field, you can come back to this section to select it here.<br />
* Adds [x] Searchable to the Catalog, indexes each entry above using its alias and title as page title -- again, you will first need to setup fields so that the drop-down will show fields.<br />
Now click Save and close. Don't click Save and edit, because we need to define fields, before we can add our items. (As a matter of fact you can add items now, but they won't contain any useful information).<br />
<br />
== Define Catalog fields ==<br />
Next to the catalog you just created, click the Define fields button (shown on the image bellow).<br />
[[File:catalog-fields.jpg|200px|thumb|none|catalog fields]]<br />
<br />
After that the list of item type fields is displayed. It is currently empty. So go ahead and create new by clicking the New field button.<br />
<br />
After that the field definition dialog appears. You need to enter Label, Description and Column name. The rules for column name are the same as for the table name, so use only letters, numbers and underscore.<br />
<br />
Next you need to specify the type of item. Type tells what may user put into the field. For example if you want to store book title, you will choose field type text. If you want to store number of pages, use type number. If you want to add longer description, use longtext. After selecting type, you may further customize the field. I believe you will be able to figure out what type best serves what purpose.<br />
<br />
Valid field types are:<br />
* text - for titles and short heading<br />
* alias - creates unique text alias reference, based on a selected title field<br />
* longtext - for descriptions, with rich text support<br />
* number - integer numbers only (can be formatted)<br />
* decimal - floating point numbers (can be formatted)<br />
* date - dates, can be entered using a date calendar clicker (can be formatted)<br />
* checkbox - toggle states like published or archived (use as filter or hide sections when selected as controlling checkbox)<br />
* select - single selection drop-down from a database list (taxonomy module, another catalog or your own reference database)<br />
* tags - multi-select checkboxes from database list (taxonomy module, another catalog or your own reference database)<br />
* url - used to create e-mail and http links automatically<br />
* file - store file links or images (thumbnail support with width, height)<br />
You can also set various visual options like: insert break (field separation line), title field (shown in items list), filter (in BE), search (in BE), sort (in BE), grouping mode (in BE) and controlling checkbox (hides field below this checkbox).<br />
<br />
Then there are also other control options like: mandatory (field is then required), unique, default value and format (string, number, money, date formats supported).<br />
[[File:catalog-field-edit.jpg|200px|thumb|none|catalog field edit]]<br />
<br />
Now click Save and we have our first item field. Create as many fields as you want. The examples created the following fields:<br />
[[File:catalog-field-list2.jpg|200px|thumb|none|catalog field list2]]<br />
<br />
== Use the Taxonomy Module to create selectable options ==<br />
In order to create a quick reference for options like genres or formats you can simply create these in a tree within the taxonomy module and use them as input reference for a select or tags field type.<br />
<br />
Here is the Taxonomy module's configuration for this Games Catalog example:<br />
[[File:taxonomy-games.jpg|200px|thumb|none|taxonomy games]]<br />
<br />
To use the Taxonomy as a reference in Select and Tags field types, you have to choose the tl_taxonomy table as your reference.<br />
[[File:catalog-select-taxonomy.jpg|200px|thumb|none|alt text]]<br />
<br />
== Using Formatting on a text, number or decimal field == <br />
The formatting option allows you to format the field. Here are the ways in which to do it:<br />
* Text - enter sprintf format string (see "more more options): <br />
<source>Help on [%s":http://php.net/sprintf] => Help on [Space Invaders]</source><br />
* Number - enter decimals only, as TL configured separators are used<br />
<source>2 => 1,524.31</source><br />
* Date - enter date-time format (see "for more options): <br />
<source>Y-m-d H:i => 2009-03-02 17:34</source><br />
*Money - this function will most likely be deprecated, because not all PHP configurations are correctly set-up for the correct LOCALE, so 90% of the time, this php function doesn't work correctly.<br />
<br />
== Edit Catalog Items ==<br />
We have successfully defined fields for our catalog. Now it is time to create few catalog items.<br />
<br />
Select Catalog module again and you will see a list of item types defined. Click the Manage items button to add, delete and edit items.<br />
[[File:catalog-items-btn.jpg|200px|thumb|none|http://php.net/date]]<br />
<br />
Now create a new item by clicking the New item button in the header area. You see that the new item contains all the fields we defined and you may fill it in a very convenient way, just like in many other modules in Contao.<br />
[[File:catalog-item-edit.jpg)|200px|thumb|none|catalog item edit]]<br />
<br />
Back-end Custom Item Display<br />
You can now also customize your catalog entries using a new feature in version 0.3.0. In the back-end you can define the format string in the catalog type definition (see using Catalog Module). Although values are already formatted using the catalog definition (format string), this format string additionally allows you to create thumbnails, wrap values in bold, italic. Actually any HTML is allowed.<br />
<br />
{{Note|Ensure that all fields you want to use in the Back-end display with this *format title string*, have been selected as *@[x] Title field@* in their individual field definitions.}}<br />
Below is an example of what you can achieve.<br />
<br />
First, enter the code in the Catalog Type definition of Format title string:<br />
<source><strong>{{title}}</strong> - {{price}} <em>[{{releasedate}}]</em> {{archived::src=all.gif}} {{archived}}<br /> {{image::w=60&h=80}}</source> <br />
<br />
== Catalog Permissions ==<br />
The Catalog application is integrated into the TYPOlight user permissions system and will allow you to set permissions for editing items within User and User Groups (for Back-end). You will be able to restrict who can edit which Catalog.<br />
<br />
<source><code class="div"><br />
Only the Administrator can create, edit or modify field types, so you cannot give a User permissions to change the catalog's table structures.<br />
</code></source><br />
<br />
== Front-End Modules using the Catalog Extension ==<br />
<br />
Catalog Extension modules:<br />
<br />
* Catalog Filter Module: build your filter on field values, range, date, search.<br />
* Catalog List Module: displays a list of items responding to the filter above.<br />
* Catalog Reader: displays item detail view + reference info (jump links to other catalogs).<br />
* Catalog Notify: creates contact form for clients to send contact info on catalog item (used on reader page)<br />
* Catalog Featured: selectable number of (random) items filtered by a preset condition.<br />
* Catalog Related: show related catalog items (except current) with selectable matching parameters.<br />
* Catalog Reference: show child catalog items where a selected reference field is matching the current viewed parent item.<br />
<br />
You may continue configuring your catalog using the documentation for the [ExtensionsCatalogExt Catalog Extension] module to create the front-end modules listed above.</div>Websevenhttps://en.contaowiki.org/File:Catalog-type-list.jpgFile:Catalog-type-list.jpg2011-12-30T10:44:13Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-types.jpgFile:Catalog-types.jpg2011-12-30T10:44:01Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-fields.jpgFile:Catalog-fields.jpg2011-12-30T10:43:49Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Taxonomy-games.jpgFile:Taxonomy-games.jpg2011-12-30T10:43:31Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-field-list2.jpgFile:Catalog-field-list2.jpg2011-12-30T10:43:18Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-items-btn.jpgFile:Catalog-items-btn.jpg2011-12-30T10:42:41Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Extensions-catalog-catalog-formatstring.jpgFile:Extensions-catalog-catalog-formatstring.jpg2011-12-30T10:42:25Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-formatstring.jpgFile:Catalog-formatstring.jpg2011-12-30T10:41:20Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-field-edit.jpgFile:Catalog-field-edit.jpg2011-12-30T10:40:57Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog_ext-config.jpgFile:Catalog ext-config.jpg2011-12-30T10:40:46Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog_ext-filter-csshover2.jpgFile:Catalog ext-filter-csshover2.jpg2011-12-30T10:40:33Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-site-example1.jpgFile:Catalog-site-example1.jpg2011-12-30T10:40:21Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-site-nags.jpgFile:Catalog-site-nags.jpg2011-12-30T10:40:02Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-site-thyon.jpgFile:Catalog-site-thyon.jpg2011-12-30T10:39:47Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-site-sofa.jpgFile:Catalog-site-sofa.jpg2011-12-30T10:39:34Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-site-whitaker.jpgFile:Catalog-site-whitaker.jpg2011-12-30T10:39:20Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Catalog-select-taxonomy.jpgFile:Catalog-select-taxonomy.jpg2011-12-30T10:39:08Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsCatalogContao.Dev ExtensionsCatalog2011-12-30T10:09:54Z<p>Webseven: Created page with '{{stub}} = Catalog Module Documentation ='</p>
<hr />
<div>{{stub}}<br />
= Catalog Module Documentation =</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsInvitationContao.Dev ExtensionsInvitation2011-12-28T14:48:08Z<p>Webseven: /* Installation */</p>
<hr />
<div>{{stub}}<br />
= Invitation Module =<br />
This module allows you to manage HTML invitations groups, sent from your designer, to send in bulk to a recipient list. This Module works similar to the Newsletter module, except the recipient list is configured in a selectable file, the input is also a selectable HTML file (from the e-vite designer) and a text-alternate version is auto-generated (extracted from the HTML).<br />
<br />
The option to send to a list of predefined e-mail addresses for preview is also built into the system.<br />
<br />
== Installation ==<br />
Download and Install from [http://www.contao.org/extension-list/compat/any/tags/Invitation.html Extension Repository]<br />
<br />
== Create an Invitation Group ==<br />
You can create an invitation group first. I design hundreds of invitations for client groups, so I create a group for each Event Company. That way i can assign permissions to each back-end user based on Invitation group. Then that Event Company can only see their invitation designs.<br />
* Add a Group Name<br />
* Add multiple Preview e-mail addresses (for the group, e.g. all possible e-mails in the group, including your own)<br />
[[File:invitation-group-edit.jpg|200px|thumb|none|invitation group edit]]<br />
<br />
== Create an Invitation ==<br />
Always ensure you've uploaded the invitation files into a TL files folder, e.g.<br />
<source> tl_files/events/launch/* </source><br />
Then go to the Invitation Group and add a new Invitation:<br />
* Add Subject for the Invitation e-mail<br />
* Select the Preview e-mail addresses (for the invitation, including yourself)<br />
* Optionally, select the recipient file (1 e-mail entry per line)<br />
* Select the HTML file in the TL folder above<br />
* You can also tick Add attachments and then select multiple attachments if you need to<br />
* Save and exit<br />
[[File:invitation-edit.jpg|200px|thumb|none|invitation edit]]<br />
<br />
== Send the Invitation ==<br />
Click the '''SEND''' button and a preview screen will appear. Here you can:<br />
* Preview the HTML Invitation (in a new window)<br />
* Tick a selection of e-mail addresses to send a preview to (yourself, or the invitation approver)<br />
* Finally when you're ready, you can click Send Invitation, which sends the invitation to all the recipients on the list as well as all the preview names. The sending process will be 10 e-mails per cycle by default, or whatever you entered in the box.<br />
[[File:invitation-send.jpg|200px|thumb|none|invitation send]]</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsGalleryContao.Dev ExtensionsGallery2011-12-28T14:47:19Z<p>Webseven: /* Installation */</p>
<hr />
<div>{{stub}}<br />
= Gallery Module =<br />
The Gallery module allows you to manage image galleries grouped by gallery archives, outside of an Article. This Module works similar to the Gallery CE, but its uses its own separate database and uses modules (similar to news) to create a gallery list, viewer and single gallery.<br />
<br />
== Installation ==<br />
* Download and Install from [http://www.contao.org/extension-list/compat/any/tags/Gallery.html Extension Repository]<br />
** [http://www.thyon.com/files/typolight/gallery/gallery-0.6.4-de.zip German language files] by manfred<br />
<br />
== Create a Gallery Archive ==<br />
You can create and edit new Gallery Archives, e.g. Wallpapers, Nature, Travel, Modern. These will then contain many galleries creating a theme grouping.<br />
<br />
[[File:gallery-archive-edit.jpg|200px|thumb|none|gallery archive edit]]<br />
<br />
== Gallery Edit Screen ==<br />
Inside a Gallery archive, create several galleries, each with its own settings.<br />
<br />
[[File:gallery-edit.jpg|200px|thumb|none|gallery edit]]<br />
<br />
When you've added a few galleries, this is what they will look like in the item list.<br />
<br />
[[File:gallery-items.jpg|200px|thumb|none|gallery items]]<br />
<br />
== Gallery List Module ==<br />
The gallery list module (with '''gallery_short.tpl''') shows all the galleries in an archive each with a small 1-line image preview, clicks through to gallery viewer below.<br />
{{Hint|Use the '''gallery_short.tpl''' template for the gallery list, and either '''gallery_fullscreen.tpl''' to support the slimbox fullscreen effect checkbox in the gallery, or '''gallery_default.tpl''' to disable the fullscreen, but still suppoty '''meta.txt''' links (as per regular gallery)}}<br />
[[File:gallery-module-list.jpg|200px|thumb|none|gallery module list]]<br />
<br />
Gallery Viewer, Single Modules<br />
A gallery viewer (like news reader) module to view a single gallery using the id/alias as parameter.<br />
<br />
[[File:gallery-module-viewer.jpg|200px|thumb|none|gallery module viewer]]<br />
<br />
== Gallery Single Module ==<br />
Gallery Single Module looks identical to this but does not require an ID/alias in the URL, as this is predefined in the module. This can then be used in a news item, event, or added to an article.</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsEventsattendContao.Dev ExtensionsEventsattend2011-12-28T14:43:30Z<p>Webseven: /* Support Modules */</p>
<hr />
<div>{{stub}}<br />
= Calendar Events Attend Module =<br />
This module provides a new type of event which links a registration form, a last registration date, show Free remaining (for count validation) and provides a module that displays the event with these new additional options.<br />
<br />
== Installation ==<br />
Download and Install from [http://www.contao.org/extension-list/compat/any/tags/Eventsattend.html Extension Repository]<br />
<br />
== Create Event with Attendance ==<br />
* Create a new '''Calendar Archive'''<br />
* Create a new '''Event''' in the above Archive<br />
** at the bottom of the event look for the '''Event Registration''' section and enable the registation (note: this will only appear for a '''default''' type event (internal/external does not allow registration)<br />
** choose from the '''Select the form''' a form with type set to Automatic Form (see Form Auto Module)<br />
** Add a * Form Headline*, e.g. Registration Information<br />
** Add a '''Last Registration Date''', after which the form will be deactivated and say: "Registration is closed for this event" (which is editable in the language files).<br />
** Enable '''Show Free places remaining''', to display a block with free places remaining below the form<br />
** If above enabled, add a * Show Free Headline*, e.g. Free Places Remaining<br />
[[File:eventsattend-options2.jpg|200px|thumb|none|eventsattend-options2]]<br />
<br />
== Support Modules ==<br />
'''Event Front-end'''<br />
<br />
* Event Attendance (use instead of regular Event Reader)<br />Create a Module for Event Attendance, which will display the event like the TL Event Reader Module, but will check if booking is full or over last registration date. If not, it will display the booking form, and optionally the free places section. The ''mod_eventsattend.tpl'' now only contains the appended registration information (the original ''modules mod_event.tpl'' and ''event_xxx.tpl'' need to be modified to change their output accordingly)<br />
{{Note|Use this module INSTEAD of your regular Event Reader module. If the event you are viewing is a default event (no registration) it will display as a normal TL event using the default TL templates as described above (without any additional info).}}</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsEventsattendContao.Dev ExtensionsEventsattend2011-12-28T14:41:07Z<p>Webseven: Created page with '{{stub}} = Calendar Events Attend Module = This module provides a new type of event which links a registration form, a last registration date, show Free remaining (for count vali…'</p>
<hr />
<div>{{stub}}<br />
= Calendar Events Attend Module =<br />
This module provides a new type of event which links a registration form, a last registration date, show Free remaining (for count validation) and provides a module that displays the event with these new additional options.<br />
<br />
== Installation ==<br />
Download and Install from [http://www.contao.org/extension-list/compat/any/tags/Eventsattend.html Extension Repository]<br />
<br />
== Create Event with Attendance ==<br />
* Create a new '''Calendar Archive'''<br />
* Create a new '''Event''' in the above Archive<br />
** at the bottom of the event look for the '''Event Registration''' section and enable the registation (note: this will only appear for a '''default''' type event (internal/external does not allow registration)<br />
** choose from the '''Select the form''' a form with type set to Automatic Form (see Form Auto Module)<br />
** Add a * Form Headline*, e.g. Registration Information<br />
** Add a '''Last Registration Date''', after which the form will be deactivated and say: "Registration is closed for this event" (which is editable in the language files).<br />
** Enable '''Show Free places remaining''', to display a block with free places remaining below the form<br />
** If above enabled, add a * Show Free Headline*, e.g. Free Places Remaining<br />
[[File:eventsattend-options2.jpg|200px|thumb|none|eventsattend-options2]]<br />
<br />
== Support Modules ==<br />
'''Event Front-end'''<br />
<br />
Event Attendance (use instead of regular Event Reader)<br />
Create a Module for Event Attendance, which will display the event like the TL Event Reader Module, but will check if booking is full or over last registration date. If not, it will display the booking form, and optionally the free places section. The ''mod_eventsattend.tpl'' now only contains the appended registration information (the original ''modules mod_event.tpl'' and ''event_xxx.tpl'' need to be modified to change their output accordingly)<br />
{{Note|Use this module INSTEAD of your regular Event Reader module. If the event you are viewing is a default event (no registration) it will display as a normal TL event using the default TL templates as described above (without any additional info).}}</div>Websevenhttps://en.contaowiki.org/File:Eventsattend-options2.jpgFile:Eventsattend-options2.jpg2011-12-28T14:35:01Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:32:06Z<p>Webseven: /* Installation */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from [http://www.contao.org/extension-list/compat/any/tags/Formauto.html Extension Repository]<br />
<br />
== Create Form Thank You Page ==<br />
#First, create a '''Page''' for Thank You<br />
#Create a '''Form Auto Info Module''' (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
<br />
== Create Automatic Form == <br />
Use the '''Form Generator''' and create a Registration Form using the form generator<br />
#Change the '''Form Type''' to [Automatic Form]<br />
#Enter the '''Store Table''' value -- the tablename to be auto-managed in the database, e.g. ''form_myform1''<br />
#[x] '''Jump to page''' -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click '''Save and Edit'''<br />
{{Caution|'''REMEMBER''', as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use '''Filtered Validation'''<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
* [x] Use '''Unique Validation'''<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
* [x] Use '''Count Validation'''<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
'''Using the Image below as an Example:'''<br />
<br />
'''Filter:'''<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
'''Count Fields:'''<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
'''[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]'''<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select '''Total Field'''<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the '''Confirmation E-mail field''' to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add '''Confirmation Sender''' using friendly format: Name [name@domain.com]<br />
# Add '''Subject''' of the e-mail<br />
# [*] '''Confirmation HTML Template''' -- select file used as HTML template -- you can add tags like ''<nowiki>{{form::firstname}}</nowiki>'' or to save some effort, you can include 1 tag called ''<nowiki>{{formauto::all}}</nowiki>'' which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:22:41Z<p>Webseven: /* Create Automatic Form */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a '''Page''' for Thank You<br />
#Create a '''Form Auto Info Module''' (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
<br />
== Create Automatic Form == <br />
Use the '''Form Generator''' and create a Registration Form using the form generator<br />
#Change the '''Form Type''' to [Automatic Form]<br />
#Enter the '''Store Table''' value -- the tablename to be auto-managed in the database, e.g. ''form_myform1''<br />
#[x] '''Jump to page''' -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click '''Save and Edit'''<br />
{{Caution|'''REMEMBER''', as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use '''Filtered Validation'''<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
* [x] Use '''Unique Validation'''<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
* [x] Use '''Count Validation'''<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
'''Using the Image below as an Example:'''<br />
<br />
'''Filter:'''<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
'''Count Fields:'''<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
'''[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]'''<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select '''Total Field'''<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the '''Confirmation E-mail field''' to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add '''Confirmation Sender''' using friendly format: Name [name@domain.com]<br />
# Add '''Subject''' of the e-mail<br />
# [*] '''Confirmation HTML Template''' -- select file used as HTML template -- you can add tags like ''<nowiki>{{form::firstname}}</nowiki>'' or to save some effort, you can include 1 tag called ''<nowiki>{{formauto::all}}</nowiki>'' which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:21:23Z<p>Webseven: /* Create Form Thank You Page */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a '''Page''' for Thank You<br />
#Create a '''Form Auto Info Module''' (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use '''Filtered Validation'''<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
* [x] Use '''Unique Validation'''<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
* [x] Use '''Count Validation'''<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
'''Using the Image below as an Example:'''<br />
<br />
'''Filter:'''<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
'''Count Fields:'''<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
'''[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]'''<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select '''Total Field'''<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the '''Confirmation E-mail field''' to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add '''Confirmation Sender''' using friendly format: Name [name@domain.com]<br />
# Add '''Subject''' of the e-mail<br />
# [*] '''Confirmation HTML Template''' -- select file used as HTML template -- you can add tags like ''<nowiki>{{form::firstname}}</nowiki>'' or to save some effort, you can include 1 tag called ''<nowiki>{{formauto::all}}</nowiki>'' which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:20:09Z<p>Webseven: /* Add Form Validation (optional) */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a Page for Thank You<br />
#Create a Form Auto Info Module (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use '''Filtered Validation'''<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
* [x] Use '''Unique Validation'''<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
* [x] Use '''Count Validation'''<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
'''Using the Image below as an Example:'''<br />
<br />
'''Filter:'''<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
'''Count Fields:'''<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
'''[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]'''<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select '''Total Field'''<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the '''Confirmation E-mail field''' to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add '''Confirmation Sender''' using friendly format: Name [name@domain.com]<br />
# Add '''Subject''' of the e-mail<br />
# [*] '''Confirmation HTML Template''' -- select file used as HTML template -- you can add tags like ''<nowiki>{{form::firstname}}</nowiki>'' or to save some effort, you can include 1 tag called ''<nowiki>{{formauto::all}}</nowiki>'' which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:17:21Z<p>Webseven: /* Add Confirmation E-mail (optional) */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a Page for Thank You<br />
#Create a Form Auto Info Module (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use Filtered Validation<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
<br />
* [x] Use Unique Validation<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
<br />
* [x] Use Count Validation<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
Using the Image below as an Example:<br />
<br />
Filter:<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
Count Fields:<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select Total Field<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the '''Confirmation E-mail field''' to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add '''Confirmation Sender''' using friendly format: Name [name@domain.com]<br />
# Add '''Subject''' of the e-mail<br />
# [*] '''Confirmation HTML Template''' -- select file used as HTML template -- you can add tags like ''<nowiki>{{form::firstname}}</nowiki>'' or to save some effort, you can include 1 tag called ''<nowiki>{{formauto::all}}</nowiki>'' which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:12:09Z<p>Webseven: /* Form Auto Info Modules */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a Page for Thank You<br />
#Create a Form Auto Info Module (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use Filtered Validation<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
<br />
* [x] Use Unique Validation<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
<br />
* [x] Use Count Validation<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
Using the Image below as an Example:<br />
<br />
Filter:<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
Count Fields:<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select Total Field<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the Confirmation E-mail field to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add Confirmation Sender using friendly format: Name [name@domain.com]<br />
# Add Subject of the e-mail<br />
# [*] Confirmation HTML Template -- select file used as HTML template -- you can add tags like {{form::firstname}} or to save some effort, you can include 1 tag called {{formauto::all}} which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a '''Thank You''' page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:11:47Z<p>Webseven: /* Form Auto Listing (use instead of Listing) */</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a Page for Thank You<br />
#Create a Form Auto Info Module (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use Filtered Validation<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
<br />
* [x] Use Unique Validation<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
<br />
* [x] Use Count Validation<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
Using the Image below as an Example:<br />
<br />
Filter:<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
Count Fields:<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select Total Field<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the Confirmation E-mail field to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add Confirmation Sender using friendly format: Name [name@domain.com]<br />
# Add Subject of the e-mail<br />
# [*] Confirmation HTML Template -- select file used as HTML template -- you can add tags like {{form::firstname}} or to save some effort, you can include 1 tag called {{formauto::all}} which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a Thank You page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the '''list_formauto.tpl''' template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/File:Formauto-type.jpgFile:Formauto-type.jpg2011-12-28T14:10:57Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Formauto-validation.jpgFile:Formauto-validation.jpg2011-12-28T14:10:42Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Formauto-confirmation.jpgFile:Formauto-confirmation.jpg2011-12-28T14:10:33Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsFormautoContao.Dev ExtensionsFormauto2011-12-28T14:10:16Z<p>Webseven: Created page with '{{stub}} = Form Auto Module = The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify…'</p>
<hr />
<div>{{stub}}<br />
= Form Auto Module =<br />
The Form Auto Module adds a new form type called Automatic Form, which allows you to store the form values into an auto-managed table (as you modify form name and form fields), adds filter, unique and count/total validation and also adds a confirmation e-mail using HTML template with tags.<br />
<br />
The package consists of 3 parts:<br />
* Module -- auto-store into a table, validation and back-end view, edit, delete<br />
* DataContainer -- to wrap the form database table into a data container<br />
* Support Files -- 2 example confirmation e-mails using both methods for tags<br />
== Installation ==<br />
* Download and Install from Extension Repository<br />
== Create Form Thank You Page ==<br />
#First, create a Page for Thank You<br />
#Create a Form Auto Info Module (there are no "parameters" to set)<br />
#Place the module above into your above Thank You page (example, use an article and add the module as a Content Element). This will display the submitted values after the registration has been completed.<br />
== Create Automatic Form == <br />
Use the Form Generator and create a Registration Form using the form generator<br />
#Change the Form Type to [Automatic Form]<br />
#Enter the Store Table value -- the tablename to be auto-managed in the database, e.g. form_myform1<br />
#[x] Jump to page -- select the "THANK YOU" page above, where you placed the Form Auto Results Module -- to display the posted form data correctly to the user as confirmation.<br />
#Click Save and Edit<br />
{{Caution|REMEMBER, as the form stores data for itself, you will need a SEPARATE form for EVERY event. You can easily duplicate a form and include in a new event (usually the confirmation e-mail and thank you can be made once per site, so no other changes needed).}}<br />
[[File:formauto-type.jpg|200px|thumb|none|formauto-type]]<br />
<br />
== Create Form Fields ==<br />
While adding fields, the database table will be automatically managed. Warnings will be presented if you try to create certain system columns as field names.<br />
<br />
#Add form fields like: firstname, lastname, email, venue, session1, session2, guests, etc.<br />
#If you want to use a venue to filter your results, use a radio/select fields (no multiples)<br />
#If you want to ensure unique entries, ensure you have a field like e-mail, which will be unique.<br />
#If you want to make breakout sessions, use a radio/select/checkbox fields<br />
== Add Form Validation (optional) ==<br />
Go back and edit the form again. Now go down to the 3 validation types and add them using the guide below.<br />
<br />
* [x] Use Filtered Validation<br />Select a Filter field from the drop-down that will be used as a filter for validation, e.g. venue or city.<br />
<br />
* [x] Use Unique Validation<br />Select a Unique field from the drop-down that must be unique (no duplicates), e.g. email<br />
<br />
* [x] Use Count Validation<br />Select one or more Count fields from the checkbox list to add counter fields. Use the radio/select/checkbox if you want them to book multiple choice or several sessions or breakout sessions.<br />
<br />
* Count Maximum Values:<br />Enter the count maximum values using the guide below:<br />
<br />
** Separate each Filter option by (|)<br />
** Separate each Count Field by (;)<br />
** Separate each Count Option by (,)<br />
Using the Image below as an Example:<br />
<br />
Filter:<br />
* Venue [select] (CPT, DBN, JHB) -- option values in brackets<br />
Count Fields:<br />
* Breakout 1 [select] (A, B, C) -- option values in brackets<br />
* Breakout 2 [select] (A, B, C)<br />
Now you can enter Count Maximum Values like this:<br />
<br />
[* 15,12,10; 30,12,10 | 10,10,10; 20,10,10 | 50,20,20; 50,30,25 *]<br />
<br />
or in words --<br />
<br />
* Venue: CPT | Breakout1: A=15,B=12,C=10 ; Breakout 2: A=30,B=12,C=10<br />
* Venue: DBN | Breakout1: A=10,B=10,C=10 ; Breakout 2: A=20,B=10,C=10<br />
* Venue: JHB | Breakout1: A=50,B=20,C=20 ; Breakout 2: A=50,B=30,C=25<br />
<br />
* Select Total Field<br />Select a field from the drop-down to use as a value to count with, instead of just 1. Use this to allow the user to choose how many guests they will bring to the session (e.g. 1: just me, 2: me + partner, 3: family of 3, 4: family of 4, etc.). Here you can ONLY choose a SELECT/RADIO drop-down, as you don't want the user to type this in (to restrict his maximum).<br />
* Show inline free countbr />Select to show the free count appended to the label (text field label, or option label in select, checkbox or radio fields)<br />
[[File:formauto-validation.jpg|200px|thumb|none|formauto-validation]]<br />
<br />
== Add Confirmation E-mail (optional) ==<br />
# select the Confirmation E-mail field to use as the e-mail of the person registering, so the confirmation e-mail will know where to send.<br />
# Add Confirmation Sender using friendly format: Name [name@domain.com]<br />
# Add Subject of the e-mail<br />
# [*] Confirmation HTML Template -- select file used as HTML template -- you can add tags like {{form::firstname}} or to save some effort, you can include 1 tag called {{formauto::all}} which will create a table and add all the fields to the e-mail (useful if you want to set-up 1 standard confirmation e-mail per site)<br />
[[File:formauto-confirmation.jpg|200px|thumb|none|formauto confirmation]]<br />
<br />
== Form Auto Info Modules ==<br />
This support module has no real parameters and it is used on a Thank You page to display the processed form data in readable format to the end-user, as confirmation of their form submission (as used above).<br />
<br />
== Form Auto Free Module ==<br />
This support module asks for the FORM and will show a table with all the free seats available.<br />
<br />
== Form Auto Listing (use instead of Listing) ==<br />
This support module asks for the FORM, instead of the tablename. The module works just like the listing module, but with CSV formatted export -- if you use the list_formauto.tpl template.<br />
<br />
== Form Data: View/Edit/Export ==<br />
When you list the forms in form generator, you will see a new icon (form/users icon) next to the edit buttons. This button will allow you to view the form table data. Once you have some submitted data, the data will appear in spreadsheet data format (almost) with no headings (it assumes you know the headings in the form).<br />
* here you can now edit the data, if an event admin wants to change the booking for a person (mistaken booking, etc).<br />
* here you can also delete the entry (again, for mistakes/admin)<br />
* the IP and date is also recorded<br />
* You can also export the raw data to a CSV file (at the top)</div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsGalleryContao.Dev ExtensionsGallery2011-12-28T13:39:29Z<p>Webseven: /* Gallery List Module */</p>
<hr />
<div>{{stub}}<br />
= Gallery Module =<br />
The Gallery module allows you to manage image galleries grouped by gallery archives, outside of an Article. This Module works similar to the Gallery CE, but its uses its own separate database and uses modules (similar to news) to create a gallery list, viewer and single gallery.<br />
<br />
== Installation ==<br />
* Download and Install from [http://www.contao.org/extension-list/tags/Gallery.html Extension Repository]<br />
** [http://www.thyon.com/files/typolight/gallery/gallery-0.6.4-de.zip German language files] by manfred<br />
== Create a Gallery Archive ==<br />
You can create and edit new Gallery Archives, e.g. Wallpapers, Nature, Travel, Modern. These will then contain many galleries creating a theme grouping.<br />
<br />
[[File:gallery-archive-edit.jpg|200px|thumb|none|gallery archive edit]]<br />
<br />
== Gallery Edit Screen ==<br />
Inside a Gallery archive, create several galleries, each with its own settings.<br />
<br />
[[File:gallery-edit.jpg|200px|thumb|none|gallery edit]]<br />
<br />
When you've added a few galleries, this is what they will look like in the item list.<br />
<br />
[[File:gallery-items.jpg|200px|thumb|none|gallery items]]<br />
<br />
== Gallery List Module ==<br />
The gallery list module (with '''gallery_short.tpl''') shows all the galleries in an archive each with a small 1-line image preview, clicks through to gallery viewer below.<br />
{{Hint|Use the '''gallery_short.tpl''' template for the gallery list, and either '''gallery_fullscreen.tpl''' to support the slimbox fullscreen effect checkbox in the gallery, or '''gallery_default.tpl''' to disable the fullscreen, but still suppoty '''meta.txt''' links (as per regular gallery)}}<br />
[[File:gallery-module-list.jpg|200px|thumb|none|gallery module list]]<br />
<br />
Gallery Viewer, Single Modules<br />
A gallery viewer (like news reader) module to view a single gallery using the id/alias as parameter.<br />
<br />
[[File:gallery-module-viewer.jpg|200px|thumb|none|gallery module viewer]]<br />
<br />
== Gallery Single Module ==<br />
Gallery Single Module looks identical to this but does not require an ID/alias in the URL, as this is predefined in the module. This can then be used in a news item, event, or added to an article.</div>Websevenhttps://en.contaowiki.org/File:Gallery-archive-edit.jpgFile:Gallery-archive-edit.jpg2011-12-28T13:35:35Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Gallery-edit.jpgFile:Gallery-edit.jpg2011-12-28T13:35:20Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Gallery-items.jpgFile:Gallery-items.jpg2011-12-28T13:35:05Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Gallery-module-list.jpgFile:Gallery-module-list.jpg2011-12-28T13:34:53Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/File:Gallery-module-viewer.jpgFile:Gallery-module-viewer.jpg2011-12-28T13:34:40Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsGalleryContao.Dev ExtensionsGallery2011-12-28T13:34:03Z<p>Webseven: Created page with '{{stub}} = Gallery Module = The Gallery module allows you to manage image galleries grouped by gallery archives, outside of an Article. This Module works similar to the Gallery C…'</p>
<hr />
<div>{{stub}}<br />
= Gallery Module =<br />
The Gallery module allows you to manage image galleries grouped by gallery archives, outside of an Article. This Module works similar to the Gallery CE, but its uses its own separate database and uses modules (similar to news) to create a gallery list, viewer and single gallery.<br />
<br />
== Installation ==<br />
* Download and Install from [http://www.contao.org/extension-list/tags/Gallery.html Extension Repository]<br />
** [http://www.thyon.com/files/typolight/gallery/gallery-0.6.4-de.zip German language files] by manfred<br />
== Create a Gallery Archive ==<br />
You can create and edit new Gallery Archives, e.g. Wallpapers, Nature, Travel, Modern. These will then contain many galleries creating a theme grouping.<br />
<br />
[[File:gallery-archive-edit.jpg|200px|thumb|none|gallery archive edit]]<br />
<br />
== Gallery Edit Screen ==<br />
Inside a Gallery archive, create several galleries, each with its own settings.<br />
<br />
[[File:gallery-edit.jpg|200px|thumb|none|gallery edit]]<br />
<br />
When you've added a few galleries, this is what they will look like in the item list.<br />
<br />
[[File:gallery-items.jpg|200px|thumb|none|gallery items]]<br />
<br />
== Gallery List Module ==<br />
The gallery list module (with '''gallery_short.tpl''') shows all the galleries in an archive each with a small 1-line image preview, clicks through to gallery viewer below.<br />
<source>Use the '''gallery_short.tpl''' template for the gallery list, and either '''gallery_fullscreen.tpl''' to support the slimbox fullscreen effect checkbox in the gallery, or '''gallery_default.tpl''' to disable the fullscreen, but still suppoty '''meta.txt''' links (as per regular gallery)</source><br />
[[File:gallery-module-list.jpg|200px|thumb|none|gallery module list]]<br />
<br />
Gallery Viewer, Single Modules<br />
A gallery viewer (like news reader) module to view a single gallery using the id/alias as parameter.<br />
<br />
[[File:gallery-module-viewer.jpg|200px|thumb|none|gallery module viewer]]<br />
<br />
== Gallery Single Module ==<br />
Gallery Single Module looks identical to this but does not require an ID/alias in the URL, as this is predefined in the module. This can then be used in a news item, event, or added to an article.</div>Websevenhttps://en.contaowiki.org/File:Invitation-send.jpgFile:Invitation-send.jpg2011-12-28T13:09:21Z<p>Webseven: </p>
<hr />
<div></div>Websevenhttps://en.contaowiki.org/Contao.Dev_ExtensionsInvitationContao.Dev ExtensionsInvitation2011-12-28T13:08:35Z<p>Webseven: Created page with '{{stub}} = Invitation Module = This module allows you to manage HTML invitations groups, sent from your designer, to send in bulk to a recipient list. This Module works similar t…'</p>
<hr />
<div>{{stub}}<br />
= Invitation Module =<br />
This module allows you to manage HTML invitations groups, sent from your designer, to send in bulk to a recipient list. This Module works similar to the Newsletter module, except the recipient list is configured in a selectable file, the input is also a selectable HTML file (from the e-vite designer) and a text-alternate version is auto-generated (extracted from the HTML).<br />
<br />
The option to send to a list of predefined e-mail addresses for preview is also built into the system.<br />
<br />
== Installation ==<br />
Download and Install from [http://www.contao.org/extension-list/tags/Invitation.html Extension Repository]<br />
== Create an Invitation Group ==<br />
You can create an invitation group first. I design hundreds of invitations for client groups, so I create a group for each Event Company. That way i can assign permissions to each back-end user based on Invitation group. Then that Event Company can only see their invitation designs.<br />
* Add a Group Name<br />
* Add multiple Preview e-mail addresses (for the group, e.g. all possible e-mails in the group, including your own)<br />
[[File:invitation-group-edit.jpg|200px|thumb|none|invitation group edit]]<br />
<br />
== Create an Invitation ==<br />
Always ensure you've uploaded the invitation files into a TL files folder, e.g.<br />
<source> tl_files/events/launch/* </source><br />
Then go to the Invitation Group and add a new Invitation:<br />
* Add Subject for the Invitation e-mail<br />
* Select the Preview e-mail addresses (for the invitation, including yourself)<br />
* Optionally, select the recipient file (1 e-mail entry per line)<br />
* Select the HTML file in the TL folder above<br />
* You can also tick Add attachments and then select multiple attachments if you need to<br />
* Save and exit<br />
[[File:invitation-edit.jpg|200px|thumb|none|invitation edit]]<br />
<br />
== Send the Invitation ==<br />
Click the '''SEND''' button and a preview screen will appear. Here you can:<br />
* Preview the HTML Invitation (in a new window)<br />
* Tick a selection of e-mail addresses to send a preview to (yourself, or the invitation approver)<br />
* Finally when you're ready, you can click Send Invitation, which sends the invitation to all the recipients on the list as well as all the preview names. The sending process will be 10 e-mails per cycle by default, or whatever you entered in the box.<br />
[[File:invitation-send.jpg|200px|thumb|none|invitation send]]</div>Websevenhttps://en.contaowiki.org/File:Quickpoll-results.jpgFile:Quickpoll-results.jpg2011-12-28T12:52:52Z<p>Webseven: uploaded a new version of "File:Quickpoll-results.jpg":&#32;Reverted to version as of 12:51, 28 December 2011</p>
<hr />
<div></div>Webseven