Template title

` -tags with either class or id attribute set will be wrapped on the inside. - (9) All relative paths found in the file will be prefixed with “fileadmin/html/” So lets look at a real world example. This is the “fileadmin/html/index.html” file: *(All green parts are displaying the interesting parts. All writing in red is my comments here, not a part of the output!)* :: Template title You are here: First level > Second level > Third level

Nothing in this table.

This table has the class, "my-class", and the id, "my-id"

This table has the class, "mainTable_class"

This table has the id, "mainTable_id"

This table has the id, "mainTable_id" AND the class "mainTable_class"

Content here...

Menu item 1
Menu itme 2
Menu item 3

This is a header

In principio creavit Deus caelum et terram terra autem erat inanis et vacua et tenebrae super faciem abyssi et spiritus Dei ferebatur super aquas dixitque Deus fiat lux et facta est lux et vidit Deus lucem quod esset bona et divisit lucem ac...

**Output:** And this is the output from the plugin after parsing the file based on the configuration above: *(My comments in red)* :: As expected the -tag was wrapped on the inside with ###DOCUMENT_HEADER###. Notice that the -tag has been removed as well. Typo3 sets the title-tag (along with a lot of additional header-information as needed.) <head> <style> BODY {font-size:12px; font-family: verdana;} .sitepath {color: blue;} </style> </HEAD> The <BODY>-tag has also been wrapped: <body bgcolor="#eeeeee"> <SPAN>-tags with the class-attribute value set to “sitepath” was configured to be wrapped with the default subpartmarker (which is the value itself surrounded by triple-# marks) thus it has happend. You are here: <span class="sitepath">First level > Second level > Third level</SPAN><br> *Any <DIV> tag having either id or class attribute set should be wrapped as well:* :: <DIV class="allTheTables"> *Just for the record: This <TABLE>-tag has NOT been wrapped in anything because it didn't provide neither id nor class attributes. Therefore no action is taken.* :: <table> <tr><td>Nothing in this table.</TD></tr> </TABLE> *But here something happens. Looking at the TypoScript configuration the values for class and id does NOT match any of the explicitly configured values (which are “mainTable\_id” and “mainTable\_class”). However <TABLE>-tags in general are instructed to be wrapped if one of these values exists (TABLE.all = 1). In this cas both class AND id exists and therefore the id-attribute takes precedence and so the table is wrapped in ###my-id### markers.* Finally notice that the <TABLE>-tags are wrapped on the OUTSIDE. This is because of the TS configuration “TABLE.all.includeWrappingTag = 1” :: <table class="my-class" id="my-id"> <tr><td>This table has the class, "my-class", and the id, "my-id"</TD></tr> </TABLE> Now the class attribute matches the specifically configured value “mainTable\_class” and is wrapped on the INSIDE (default) accordingly :: <table class="mainTable_class"> <tr><td>This table has the class, "mainTable_class"</TD></tr> </TABLE> In this case the id attribute matches the configured value “mainTable\_id”. Because “mainTable\_id” was configured in TS like this: “TABLE.id.mainTable\_id.doubleWrap = 1” the <TABLE>-tags are wrapped both on the inside AND the outside. The outside-wrap is prefixed “\_PRE” :: <table id="mainTable_id"> <tr><td>This table has the id, "mainTable_id"</TD></tr> </TABLE> In this case the exact same thing happens as above. The interesting part is that now the class-attribute did also exist, but we see once again that the id-attribute takes precedence in cases with both values existing. :: <table class="mainTable_class" id="mainTable_id"> <tr><td>This table has the id, "mainTable_id" AND the class "mainTable_class"</TD></tr> </TABLE> <table> <tr> Looking at the TS configuration we see that <TD>-tags are wrapped in case the id attribute matches “header” OR the class attribute matches “content\_column”. In these cases only the second <TD> tag from the top matches and is wrapped. :: <td class="header">Content here...</TD> <td id="header">Content here...</TD> <td class="another_header">Content here...</TD> <td id="another_header">Content here...</TD> <td>Content here...</TD> </tr> </TABLE> *A most interesting feature is that this images was in the original file references as “images/apache\_pb.gif”. Now the file - being a relative reference - is prefixed with “fileadmin/html”. Thus viewing the template file directly with a browser or HTML-editor from the path fileadmin/html/index.html will STILL show the correct image as when the file is used as template for the actual Typo3 page which is viewed from the site root.* :: <IMG src="fileadmin/html/images/apache_pb.gif" width="259" height="32" border="0" alt=""> </DIV> <table> <tr> *This is a real world example where we have a table on a page with a cell for a menu and a cell for page content. Probably we intended both columns to be wrapped on the inside with subpart markers, but only the “content\_column” has been wrapped. The obvious error is that in the TS configuration of the plugin, we should have added “TD.class.menu\_column = 1” in order to get the menu column wrapped as well. Another option - for the lazy - is to configured TD like this “TD.all=1” - so all TD cells with an id or class attribute would be wrapped.* :: <td class="menu_column"> Menu item 1<br> Menu itme 2<br> Menu item 3<br> </TD> <td class="content_column"> <H3>This is a header</H3> <P>In principio creavit Deus caelum et terram terra autem erat inanis et vacua et tenebrae super faciem abyssi et spiritus Dei ferebatur super aquas dixitque Deus fiat lux et facta est lux et vidit Deus lucem quod esset bona et divisit lucem ac...</P> </TD> </tr> </TABLE> *Finally the action-attribute of the <FORM>-tags are just like the src-attribute of image tags analysed for relative paths. In this case the template file might simply refer to the CORRECT search page in Typo3 from it's position in fileadmin/html/. Thus in the original file “../../index.php?....” would be the correct, working path to any Typo3 page, but when parsed, this path would be prefixed as usual with “fileadmin/html/” so that it works from the site-root out-of-the box.* :: <FORM action="fileadmin/html/../../index.php?id=search_result_page"> <input type="text" name="search_word"> <input type="submit" value="Search now!"> </form> </BODY> </html> .. _Using-this-to-build-a-site: Using this to build a site: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ This TypoScript configuration of a page object will *in addition* to the plugin configuration listed above make use of some of the subpart markers in the output of the plugin. *(My comments in red, italics)* :: # Default PAGE object: page = PAGE page.typeNum = 0 *This retrieves the <BODY>-tag from the template:* :: # Getting body tag from template page.bodyTagCObject =< plugin.tx_automaketemplate_pi1 page.bodyTagCObject.getBodyTag=1 *Inserting the <HEAD> section (###DOCUMENT\_HEAD### subpart) from the template (without <TITLE>-tag...). Thus all header information in the template file is preserved, including any stylesheet.* :: # Getting header data from template, but excluding title-tag (see object configuration) page.headerData.10 = TEMPLATE page.headerData.10.template =< plugin.tx_automaketemplate_pi1 page.headerData.10.workOnSubpart = DOCUMENT_HEADER *Finally the page content is fetched from the template (###DOCUMENT\_BODY### subpart)* :: # Page content: page.20 = TEMPLATE page.20.template =< plugin.tx_automaketemplate_pi1 page.20.workOnSubpart = DOCUMENT_BODY page.20.subparts { *Here the content of the subpart markers  is substituted with a menu showing the “path” to the current page.* *Originally it looked like this:You are here: <span class="sitepath">First level > Second level > Third level</span><br>After the parsing of this plugin, it would look like this (markers added):You are here: <span class="sitepath">First level > Second level > Third level</SPAN>Now it looks like this (for the rootpage) (subpart section substituted with menu):You are here: <span class="sitepath"><A HREF="index.php?id=1130" onFocus="blurLink(this);">Auto Template </A></SPAN><br>* :: sitepath = HMENU sitepath.special = rootline sitepath.1 = TMENU sitepath.1.NO.linkWrap = | > |*||*| | *Here the dummy-content of the table cell with class “content\_column” is substituted with the true content of the page:* :: content_column < styles.content.get } 9 .. ######CUTTER_MARK_IMAGES###### .. |img-1| image:: img-1.png .. :align: left .. |img-2| image:: img-2.png .. :border: 0 .. :height: 21 .. :hspace: 9 .. :id: Grafik2 .. :name: Grafik2 .. :width: 87