[CLEANUP] Remove simulate static from Core
[Packages/TYPO3.CMS.git] / typo3 / sysext / t3editor / res / tsref / tsref.xml
1 <?xml version="1.0" encoding="UTF-8"?>
2 <tsRef>
3 <type id="cObj"/>
4 <type id="array"/>
5 <type id="int"/>
6 <type id="intList"/>
7 <type id="double"/>
8 <type id="boolean"/>
9 <type id="string"/>
10 <type id="ADMPANEL"/>
11 <type id="ARR_languages_strings" name="ARR_languages_strings">
12 <property name="default" type="string"/>
13 <property name="en" type="string"/>
14 <property name="dk" type="string"/>
15 <property name="de" type="string"/>
16 <property name="no" type="string"/>
17 <property name="it" type="string"/>
18 <property name="fr" type="string"/>
19 <property name="nl" type="string"/>
20 <property name="cz" type="string"/>
21 <property name="pl" type="string"/>
22 <property name="si" type="string"/>
23 <property name="fi" type="string"/>
24 <property name="tr" type="string"/>
25 <property name="se" type="string"/>
26 <property name="pt" type="string"/>
27 <property name="ru" type="string"/>
28 <property name="ro" type="string"/>
29 <property name="ch" type="string"/>
30 <property name="sk" type="string"/>
31 <property name="lt" type="string"/>
32 <property name="is" type="string"/>
33 <property name="hr" type="string"/>
34 <property name="hu" type="string"/>
35 <property name="gl" type="string"/>
36 <property name="th" type="string"/>
37 <property name="gr" type="string"/>
38 <property name="hk" type="string"/>
39 <property name="eu" type="string"/>
40 <property name="bg" type="string"/>
41 <property name="br" type="string"/>
42 <property name="et" type="string"/>
43 <property name="ar" type="string"/>
44 <property name="he" type="string"/>
45 <property name="ua" type="string"/>
46 <property name="lv" type="string"/>
47 <property name="jp" type="string"/>
48 <property name="vn" type="string"/>
49 <property name="ca" type="string"/>
50 <property name="ba" type="string"/>
51 <property name="kr" type="string"/>
52 <property name="eo" type="string"/>
53 <property name="my" type="string"/>
54 <property name="hi" type="string"/>
55 </type>
56 <type id="CARRAY" extends="stdWrap" name="CARRAY">
57 <property name="1" type="cObj">
58 <description><![CDATA[This is a numerical "array" of content-objects (cObjects). The order by which you specific the objects is not important as the array will be sorted before it's parsed!
59
60 ]]></description>
61 </property>
62 <property name="2" type="cObj">
63 <description><![CDATA[This is a numerical "array" of content-objects (cObjects). The order by which you specific the objects is not important as the array will be sorted before it's parsed!
64
65 ]]></description>
66 </property>
67 <property name="3" type="cObj">
68 <description><![CDATA[This is a numerical "array" of content-objects (cObjects). The order by which you specific the objects is not important as the array will be sorted before it's parsed!
69
70 ]]></description>
71 </property>
72 <property name="4" type="cObj">
73 <description><![CDATA[This is a numerical "array" of content-objects (cObjects). The order by which you specific the objects is not important as the array will be sorted before it's parsed!
74
75 ]]></description>
76 </property>
77 </type>
78 <type id="CARRAY+TDParams" extends="CARRAY" name="CARRAY+TDParams">
79 <property name="TDParams" type="string">
80 <description><![CDATA[<TD>-params
81 NOTE: This applies ONLY if "CARRAY +TDParams" is set to be data type
82 This property is used only in some cases where CARRAY is used. Please look out for a note about that in the various cases.
83 ]]></description>
84 <default><![CDATA[
85 ]]></default>
86 </property>
87 </type>
88 <type id="CASE" extends="cObjArray" name="CASE">
89 <property name="default" type="cObj">
90 <description><![CDATA[The default object, if not defined, nothing is returned in the default case.
91 ]]></description>
92 </property>
93 <property name="if" type="if">
94 <description><![CDATA[if "if" returns false nothing is returned
95
96 ]]></description>
97 </property>
98 <property name="key" type="stdWrap">
99 <description><![CDATA[If the value of this key is defined, that object will be returned, otherwise the default-object will be returned.
100 <pre>key = helloWorld
101 helloWorld = <a href="/index.php/TSref/TEXT" title="TSref/TEXT">TEXT</a>
102
103 helloWorld.value = this item will be returned
104 </pre>
105 ]]></description>
106 </property>
107 <property name="setCurrent" type="stdWrap">
108 <description><![CDATA[Sets the "current"-value.
109
110 ]]></description>
111 </property>
112 <property name="stdWrap" type="stdWrap">
113 <description><![CDATA[stdwrap properties, applied on the returned object.
114 ]]></description>
115 </property>
116 </type>
117 <type id="CLEARGIF" name="CLEARGIF">
118 <property name="height" type="stdWrap">
119 <description><![CDATA[<img>-data:height /stdWrap
120 ]]></description>
121 <default><![CDATA[1]]></default>
122 </property>
123 <property name="width" type="stdWrap">
124 <description><![CDATA[<img>-data:width /stdWrap
125 ]]></description>
126 <default><![CDATA[1]]></default>
127 </property>
128 <property name="wrap" type="stdWrap">
129 <description><![CDATA[wrap/stdWrap
130 ]]></description>
131 <default><![CDATA[ | <BR>]]></default>
132 </property>
133 </type>
134 <type id="cObjArray">
135 <property name="1" type="cObj">
136 <description><![CDATA[This is a numerical "array" of content-objects (cObjects).
137 ]]></description>
138 </property>
139 <property name="2" type="cObj">
140 <description><![CDATA[This is a numerical "array" of content-objects (cObjects).
141 ]]></description>
142 </property>
143 <property name="3" type="cObj">
144 <description><![CDATA[This is a numerical "array" of content-objects (cObjects).
145 ]]></description>
146 </property>
147 <property name="4" type="cObj">
148 <description><![CDATA[This is a numerical "array" of content-objects (cObjects).
149 ]]></description>
150 </property>
151 </type>
152 <type id="COBJ_ARRAY" extends="cObjArray">
153 <property name="if" type="if">
154 <description><![CDATA[if "if" returns false the COA is NOT rendered]]></description>
155 <default><![CDATA[
156 ]]></default>
157 </property>
158 <property name="stdWrap" type="stdWrap">
159 <description><![CDATA[
160 ]]></description>
161 <default><![CDATA[
162 ]]></default>
163 </property>
164 <property name="wrap" type="stdWrap">
165 <description><![CDATA[wrap/stdWrap
166 ]]></description>
167 <default><![CDATA[
168 ]]></default>
169 </property>
170 </type>
171 <type id="COA" extends="COBJ_ARRAY">
172 </type>
173 <type id="COA_INT" extends="COBJ_ARRAY">
174 <property name="includeLibs" type="stdWrap">
175 <description><![CDATA[list of resources/stdWrap
176 (This property is used only if the object is COA_INT!, See introduction.)
177 This is a comma-separated list of resources that are included as PHP-scripts (with include_once() function) if this script is included.
178 This is possible to do because any include-files will be known before the scripts are included. That's not the case with the regular PHP_SCRIPT cObject.]]></description>
179 <default><![CDATA[
180 ]]></default>
181 </property>
182 </type>
183 <type id="COLUMNS">
184 <property name="TDparams" type="stdWrap">
185 <description><![CDATA[<TD>-params/stdWrap
186 ]]></description>
187 <default><![CDATA[valign=top]]></default>
188 </property>
189 <property name="1" type="cObj">
190 <description><![CDATA[This is the content-object for each column!!]]></description>
191 <default><![CDATA[
192 ]]></default>
193 </property>
194 <property name="2" type="cObj">
195 <description><![CDATA[This is the content-object for each column!!]]></description>
196 <default><![CDATA[
197 ]]></default>
198 </property>
199 <property name="3" type="cObj">
200 <description><![CDATA[This is the content-object for each column!!]]></description>
201 <default><![CDATA[
202 ]]></default>
203 </property>
204 <property name="4" type="cObj">
205 <description><![CDATA[This is the content-object for each column!!]]></description>
206 <default><![CDATA[
207 ]]></default>
208 </property>
209 <property name="after" type="cObj">
210 <description><![CDATA[This is a cObject placed after the columns-table!!]]></description>
211 <default><![CDATA[
212 ]]></default>
213 </property>
214 <property name="gapBgCol" type="stdWrap">
215 <description><![CDATA[HTML-color /stdWrap
216 background-color for the gap-tablecells]]></description>
217 <default><![CDATA[
218 ]]></default>
219 </property>
220 <property name="gapLineCol" type="stdWrap">
221 <description><![CDATA[HTML-color /stdWrap
222 Line color]]></description>
223 <default><![CDATA[black]]></default>
224 </property>
225 <property name="gapLineThickness" type="stdWrap">
226 <description><![CDATA[int /stdWrap
227 lineThickness of the dividerline in the gap between cells
228 0 = no line]]></description>
229 <default><![CDATA[
230 ]]></default>
231 </property>
232 <property name="gapWidth" type="stdWrap">
233 <description><![CDATA[int /stdWrap
234 Width of the gap between columns.
235 0 = no gap]]></description>
236 <default><![CDATA[
237 ]]></default>
238 </property>
239 <property name="if" type="if">
240 <description><![CDATA[if "if" returns false the columns are not rendered!]]></description>
241 <default><![CDATA[
242 ]]></default>
243 </property>
244 <property name="rows" type="stdWrap">
245 <description><![CDATA[int (Range: 2-20)/stdWrap
246 The number of rows  in the columns.]]></description>
247 <default><![CDATA[2]]></default>
248 </property>
249 <property name="stdWrap" type="stdWrap">
250 <description><![CDATA[
251 ]]></description>
252 <default><![CDATA[
253 ]]></default>
254 </property>
255 <property name="tableParams" type="stdWrap">
256 <description><![CDATA[<TABLE>-params/stdWrap
257 ]]></description>
258 <default><![CDATA[border=0 cellspacing=0 cellpadding=0]]></default>
259 </property>
260 <property name="totalWidth" type="stdWrap">
261 <description><![CDATA[int/stdWrap
262 The total-width of the columns+gaps]]></description>
263 <default><![CDATA[
264 ]]></default>
265 </property>
266 </type>
267 <type id="CONFIG">
268 <property name="ATagParams" type="string">
269 <description><![CDATA[<A>-params
270 Additional parameters to all links in TYPO3 (excluding menu-links)
271
272 Example:
273 To blur links, insert:
274 onFocus="blurLink(this)"]]></description>
275 <default><![CDATA[
276 ]]></default>
277 </property>
278 <property name="MP_defaults" type="string">
279 <description><![CDATA[Allows you to set a list of page id numbers which will always have a certain "&MP=..." parameter added.
280
281 Syntax:
282 [id],[id],... : [MP-var] | [id],[id],... : [MP-var] | ...
283
284 Example:
285 config.MP_defaults = 36,37,48 : 2-207
286
287 This will by default add "&MP=2-207" to all links pointing to pages 36,37 and 48]]></description>
288 <default><![CDATA[
289 ]]></default>
290 </property>
291 <property name="MP_disableTypolinkClosestMPvalue" type="boolean">
292 <description><![CDATA[If set, the typolink function will not try to find the closest MP value for the id.]]></description>
293 <default><![CDATA[
294 ]]></default>
295 </property>
296 <property name="MP_mapRootPoints" type="string">
297 <description><![CDATA[list of PIDs/string
298 Defines a list of ID numbers from which the MP-vars are automatically calculated for the branch.
299 The result is used just like MP_defaults are used to find MP-vars if none has been specified prior to the call to t3lib_tstemplate::linkData().
300 You can specify "root" as a special keyword in the list of IDs and that will create a map-tree for the whole site (but this may be VERY processing intensive if there are many pages!).
301 The order of IDs specified may have a significance; Any ID in a branch which is processed already (by a previous ID root point) will not be processed again.]]></description>
302 <default><![CDATA[
303 ]]></default>
304 </property>
305 <property name="USERNAME_substToken" type="string">
306 <description><![CDATA[The is the token used on the page, which should be substituted with the current username IF a front-end user is logged in! If no login, the substitution will not happen.]]></description>
307 <default><![CDATA[<!--###USERNAME###-->]]></default>
308 </property>
309 <property name="USERUID_substToken" type="string">
310 <description><![CDATA[The is the token used on the page, which should be substituted with the current users UID IF a front-end user is logged in! If no login, the substitution will not happen.
311 This value has no default value and only if you specify a value for this token will a substitution process take place.]]></description>
312 <default><![CDATA[
313 ]]></default>
314 </property>
315 <property name="absRefPrefix" type="string">
316 <description><![CDATA[If this value is set, then all relative links in TypoScript are prepended with this string. Used to convert relative paths to absolute paths.
317
318 Note: If you're working on a server where you have both internal and external access, you might to yourself a favour and set the absRefPrefix to the url and path of you site, eg. http://www.typo3.org/. If you do not, you risk to render pages to cache from the internal network and thereby prefix image-references and links with a non-accessible path from outside.]]></description>
319 <default><![CDATA[
320 ]]></default>
321 </property>
322 <property name="additionalHeaders" type="string">
323 <description><![CDATA[strings divided by "|"
324 This is additional headers. You separate each header by a vertical line "|".  Normally TYPO3 does not send any headers with the Header()-function in PHP.
325
326 Examples:
327 Content-type: text/vnd.wap.wml
328 (this will sent a content-header for a WAP-site)
329
330 Content-type: image/gif | Expires: Mon, 26 Jul 1997 05:00:00 GMT
331 (this will sent a content-header for a GIF-file and a Expires header)
332
333 Location: www.typo3.org
334 (This redirects the page to www.typo3.org)]]></description>
335 <default><![CDATA[
336 ]]></default>
337 </property>
338 <property name="admPanel" type="ADMPANEL">
339 <description><![CDATA[boolean / ADMPANEL properties
340 If set, the admin panel appears in the bottom of pages.
341
342 NOTE: In addition the panel must be enabled for the user as well, using the TSconfig for the user! See adminguide documentation.
343
344 SEE: Admin Panel section]]></description>
345 <default><![CDATA[
346 ]]></default>
347 </property>
348 <property name="baseURL" type="string">
349 <description><![CDATA[This writes the <base> tag in the header of the document. Set this to the value that is expected to be the URL, and append a "/" to the end of the string.
350
351 Example:
352 config.baseURL = http://typo3.org/sub_dir/]]></description>
353 <default><![CDATA[
354 ]]></default>
355 </property>
356 <property name="beLoginLinkIPList" type="string">
357 <description><![CDATA[[IP-number]
358 If set and REMOTE_ADDR matches one of the listed IP-numbers (Wild-card, *, allowed) then a link to the typo3/ login scrip with redirect pointing back to the page is shown.
359
360 NOTE: beLoginLinkIPList_login and/or beLoginLinkIPList_logout (see below) must be defined if the link should show up!]]></description>
361 <default><![CDATA[
362 ]]></default>
363 </property>
364 <property name="beLoginLinkIPList_login" type="string">
365 <description><![CDATA[HTML code wrapped with the login link, see 'beLoginLinkIPList'
366
367 Example:
368 <HR><B>LOGING</B>]]></description>
369 <default><![CDATA[
370 ]]></default>
371 </property>
372 <property name="beLoginLinkIPList_logout" type="string">
373 <description><![CDATA[HTML code wrapped with the logout link, see above]]></description>
374 <default><![CDATA[
375 ]]></default>
376 </property>
377 <property name="cache" type="array">
378 <description><![CDATA[The maximum cache lifetime of a page can not only be determined the start and stop times of content elements on the page itself, but also by arbitrary records on any other page. However, the page has to be configured so that TYPO3 knows, which records' start and stop times to include. Otherwise, the cache entry will be used although a start/stop date already passed by.
379
380 To include records of type <tablename> on page <pid> into the cache lifetime calculation of page <page-id>, add the following TypoScript:
381 config.cache.<page-id> = <tablename>:<pid>
382
383 Thus, if you want to include the fe_users records on page 2 in the cache lifetime calculation for page 10, add the following TypoScript:
384 config.cache.10 = fe_users:2
385
386 Multiple record sources can be added as comma-separated list, e.g.
387 config.cache.10 = fe_users:2,tt_news:11
388
389 In order to consider records for the cache lifetime of all pages, use the *all* keyword:
390 config.cache.all = fe_users:2]]></description>
391 <default><![CDATA[]]></default>
392 </property>
393 <property name="cache_clearAtMidnight" type="boolean">
394 <description><![CDATA[With this setting the cache always expires at midnight of the day, the page is scheduled to expire.]]></description>
395 <default><![CDATA[false]]></default>
396 </property>
397 <property name="cache_period" type="int">
398 <description><![CDATA[int, seconds
399 The number of second a page may remain in cache.
400 This value is overridden by the value set in the page-record (field="cache_timeout") if this value is greater than zero.]]></description>
401 <default><![CDATA[86400 (=24H)]]></default>
402 </property>
403 <property name="compensateFieldWidth" type="double">
404 <description><![CDATA[this floating point value will be used by the FORMS cObject to compensate the length of the formfields text and input.
405 This feature is useful, if the page-option "smallFormFields" is set. In that case Netscape renders formfields much longer than IE. If you want the two browsers to display the same size formfields, use a value of approx "0.6" for netscape-browsers.
406
407 Example:
408 [browser = netscape]
409   config.compensateFieldWidth = 0.6
410 [global]
411
412 This option may be overridden in the FORMS-cObject.]]></description>
413 <default><![CDATA[
414 ]]></default>
415 </property>
416 <property name="content_from_pid_allowOutsideDomain" type="boolean">
417 <description><![CDATA[Using the "Show content from this page instead" feature allows you to insert content from the current domain only. Setting this option will allow content included from anywhere in the page tree!]]></description>
418 <default><![CDATA[
419 ]]></default>
420 </property>
421 <property name="debug" type="boolean">
422 <description><![CDATA[If set any debug-information in the TypoScript code is output. Currently this applies only to the menu-objects]]></description>
423 <default><![CDATA[
424 ]]></default>
425 </property>
426 <property name="defaultGetVars" type="array">
427 <description><![CDATA[Allows to set default values for GET parameters. Default value is taken only if the GET parameter isn't defined. Array notation is done with dots, e.g.:
428
429 test[var1] will be written as text.var1
430
431 Example:
432
433 config.defaultgetVars {
434 test.var1.var2.p3 = 15
435 L = 3
436 }
437 ]]></description>
438 <default><![CDATA[
439 ]]></default>
440 </property>
441 <property name="disableAllHeaderCode" type="boolean">
442 <description><![CDATA[If this is set, none of the features of the PAGE-object is processed and the content of the page will be the result of the cObject array (1,2,3,4...) of the PAGE-object.  This means that the result of the cObject should include everything from the <HTML> .... to the </HTML> tag !!
443 Use this feature in templates supplying other content-types than HTML. That could be an image or a WAP-page!]]></description>
444 <default><![CDATA[false]]></default>
445 </property>
446 <property name="disableCharsetHeader" type="boolean">
447 <description><![CDATA[By default a header "content-type:text/html; charset..." is sent. This option will disable that.]]></description>
448 <default><![CDATA[
449 ]]></default>
450 </property>
451 <property name="disablePageExternalUrl" type="boolean">
452 <description><![CDATA[If set, pages with doktype "External Url" will not trigger jumpUrl in TSFE. This may help you to have external urls open inside you framesets.]]></description>
453 <default><![CDATA[
454 ]]></default>
455 </property>
456 <property name="disablePrefixComment" type="boolean">
457 <description><![CDATA[If set, the stdWrap property "prefixComment" will be disabled, thus preventing any revealing and spaceconsuming comments in the HTML source code.]]></description>
458 <default><![CDATA[
459 ]]></default>
460 </property>
461 <property name="disablePreviewNotification" type="boolean">
462 <description><![CDATA[Disables the "preview" notification box completely]]></description>
463 <default><![CDATA[
464 ]]></default>
465 </property>
466 <property name="doctype" type="string">
467 <description><![CDATA[If set, then a document type declaration (and an XML prologue) will be generated. The value can either be a complete doctype or one of the following keywords:
468
469 "xhtml_trans" for XHTML 1.0 Transitional doctype.
470 "xhtml_frames" for XHTML 1.0 Frameset doctype.
471 "xhtml_strict" for XHTML 1.0 Strict doctype.
472 "xhtml_basic" for XHTML basic doctype.
473 "xhtml_11" for XHTML 1.1 doctype.
474 "xhtml+rdf_10" for XHTML+RDFa 1.0 doctype.
475 "xhtml_2" for XHTML 2 doctype.
476 "html5" for HTML5
477 "none" for NO doctype at all.
478
479 Note that the keywords also change the way TYPO3 generates some of the XHTML tags to ensure valid XML. If you set doctype to a string, then you must also set config.xhtmlDoctype (see below).
480
481 See "config.htmlTag_setParams" and "config.htmlTag_langKey" for more details on the effect on the html tag.
482 ]]></description>
483 <default><![CDATA[Default is a DOCTYPE like this:
484 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
485 ]]></default>
486 </property>
487 <property name="doctypeSwitch" type="boolean">
488 <description><![CDATA[If set, the order of <?xml...> and <!DOCTYPE...> will be reversed. This is needed for MSIE to be standards compliant with XHTML.
489
490 Background:
491 By default TYPO3 outputs the XML/DOCTYPE in compliance with the standards of XHTML. However a browser like MSIE will still run in "quirks-mode" unless the <?xml> and <DOCTYPE> tags are ordered opposite. But this breaks CSS validation...
492 With this option designers can decide for themselves what they want then.
493
494 If you want to check the compatibility-mode of your webbrowser you can do so with a simple JavaScript that can be inserted on a TYPO3 page like this:
495
496 page.headerData.1 = TEXT
497 page.headerData.1.value = <script>alert(document.compatMode);</script>
498
499 If your browser has detected the DOCTYPE correctly it will report "CSS1Compat"
500 If you are not running in compliance mode you will get some other message. MSIE will report "BackCompat" for instance - this means it runs in quirks-mode, supporting all the old "browser-bugs".]]></description>
501 <default><![CDATA[
502 ]]></default>
503 </property>
504 <property name="enableContentLengthHeader" type="boolean">
505 <description><![CDATA[If set, a header "content-length: [bytes of content]" is sent.
506
507 If a PHP_SCRIPT_EXT object is detected on the page or if the Backend user is logged in, this is disabled. The reason is that the content length header cannot include the lenght of these objects and the content-length will cut of the lenght of the document in some browsers.]]></description>
508 <default><![CDATA[
509 ]]></default>
510 </property>
511 <property name="extTarget" type="string">
512 <description><![CDATA[default external target. Used by typolink if no extTarget is set]]></description>
513 <default><![CDATA[_top]]></default>
514 </property>
515 <property name="fileTarget" type="string">
516 <description><![CDATA[Default file link target. Used by typolink if no fileTarget is set. ]]></description>
517 <default><![CDATA[
518 ]]></default>
519 </property>
520 <property name="forceTypeValue" type="int">
521 <description><![CDATA[Force the &type value of all TYPO3 generated links to a specific value (except if overruled by local forceTypeValue values).
522 Useful if you run a template with special content at - say &type=95 - but still wants to keep your targets neutral. Then you set your targets to blank and this value to the type value you wish.]]></description>
523 <default><![CDATA[
524 ]]></default>
525 </property>
526 <property name="frameReloadIfNotInFrameset" type="boolean">
527 <description><![CDATA[If set, then the current page will check if the page object name (eg. "page" or "frameset") exists as "parent.[name]" (eg. "parent.page") and if not the page will be reloaded in top frame. This secures that links from search engines to pages inside a frameset will load the frameset.
528 Works only with type-values different from zero.]]></description>
529 <default><![CDATA[
530 ]]></default>
531 </property>
532 <property name="ftu" type="boolean">
533 <description><![CDATA[If set, the "&ftu=...." GET-fallback identification is inserted.
534 "&ftu=[hash]" is always inserted in the links on the first page a user hits. If it turns out in the next hit that the user has cookies enabled, this variable is not set anymore as the cookies does the job. If no cookies is accepted the "ftu" remains set for all links on the site and thereby we can still track the user.
535
536 You should not set this feature if grabber-spiders like Teleport are going to grab your site!
537 You should not set this feature if you want search-engines to index your site.
538
539 You can also ignore this feature if you're certain, website users will use cookies.
540  "ftu" means fe_typo_user ("fe" is "frontend").]]></description>
541 <default><![CDATA[false]]></default>
542 </property>
543 <property name="headerComment " type="string">
544 <description><![CDATA[The content is added before the "TYPO3 Content Management Framework" comment in the <head> section of the page. Use this to insert a note like that "Programmed by My-Agency" ...]]></description>
545 <default><![CDATA[
546 ]]></default>
547 </property>
548 <property name="htmlTag_dir" type="string">
549 <description><![CDATA[Sets text direction for whole document (useful for display of Arabic, Hebrew pages).
550
551 Basically the value becomes the attribute value of "dir" for the <html> tag.
552
553 Values:
554 rtl = Right-To-Left (for Arabic / Hebrew)
555 ltr = Left-To-Right (Default for other languages)
556
557 Example:
558 config.htmlTag_dir = rtl]]></description>
559 <default><![CDATA[
560 ]]></default>
561 </property>
562 <property name="htmlTag_langKey" type="string">
563 <description><![CDATA[Allows you to set the language value for the attributes "xml:lang" and "lang" in the <html> tag (when using "config.doctype = xhtml*").
564
565 The values must follow the format specified in IETF RFC 3066
566
567 Example:
568 config.htmlTag_langKey = en-US]]></description>
569 <default><![CDATA[en]]></default>
570 </property>
571 <property name="htmlTag_setParams" type="string">
572 <description><![CDATA[Sets the attributes for the <html> tag on the page. If you set "config.doctype" to a keyword enabling XHTML then some attributes are already set. This property allows you to override any preset attributes with you own content if needed.
573
574 Special: If you set it to "none" then no attributes will be set at any event.
575
576 Example:
577 config.htmlTag_setParams =  xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US"]]></description>
578 <default><![CDATA[
579 ]]></default>
580 </property>
581 <property name="incT3Lib_htmlmail " type="boolean">
582 <description><![CDATA[Include t3lib/class.t3lib_htmlmail.php]]></description>
583 <default><![CDATA[
584 ]]></default>
585 </property>
586 <property name="includeLibrary" type="string">
587 <description><![CDATA[This includes a phpfile.]]></description>
588 <default><![CDATA[
589 ]]></default>
590 </property>
591 <property name="index_descrLgd" type="int">
592 <description><![CDATA[This indicates how many chars to preserve as description for an indexed page. This may be used in the search result display.]]></description>
593 <default><![CDATA[200]]></default>
594 </property>
595 <property name="index_enable" type="boolean">
596 <description><![CDATA[Enables cached pages to be indexed.]]></description>
597 <default><![CDATA[
598 ]]></default>
599 </property>
600 <property name="index_externals" type="boolean">
601 <description><![CDATA[If set, external media linked to on the pages is indexed as well.]]></description>
602 <default><![CDATA[
603 ]]></default>
604 </property>
605 <property name="inlineStyle2TempFile" type="boolean">
606 <description><![CDATA[If set, the inline styles TYPO3 controls in the core are written to a file,  typo3temp/stylesheet_[hashstring].css, and the header will only contain the link to the stylesheet.
607 The file hash is based solely on the content of the styles.
608
609 Depends on the compatibility mode (see Tools>Install>Update wizard):
610 compatibility mode < 4.0:   0
611 compatibility mode >= 4.0:   1
612
613 Example:
614 config.inlineStyle2TempFile = 1]]></description>
615 <default><![CDATA[
616 ]]></default>
617 </property>
618 <property name="insertDmailerBoundaries" type="boolean">
619 <description><![CDATA[If set, boundary marks will be set around all records inserted on the page with cObjects CONTENT and RECORD. They are inserted as HTML-comments and do no harm.
620 Used by the Direct Mail module in TYPO3 to segmentize a page by categories.]]></description>
621 <default><![CDATA[
622 ]]></default>
623 </property>
624 <property name="intTarget" type="string">
625 <description><![CDATA[default internal target. Used by typolink if no target is set]]></description>
626 <default><![CDATA[
627 ]]></default>
628 </property>
629 <property name="jumpurl_enable" type="boolean">
630 <description><![CDATA[Jumpurl is a concept where external links are redirected from the index_ts.php script, which first logs which url it was. This logging of external links is only interesting if you use the internal stat-table in TYPO3.]]></description>
631 <default><![CDATA[0]]></default>
632 </property>
633 <property name="jumpurl_mailto_disable" type="boolean">
634 <description><![CDATA[Disables the use of jumpUrl when linking to email-adresses.]]></description>
635 <default><![CDATA[0]]></default>
636 </property>
637 <property name="language" type="string">
638 <description><![CDATA[Language key. See stdWrap.lang for more information.
639 Select between:
640 English  (default) = [empty]
641 Danish = dk
642 German = de
643 Norwegian = no
644 Italian = it
645 etc...
646
647 Value must correspond with the key used for backend system language if there is one. See inside config_default.php or look at the translation page on TYPO3.org for the official 2-byte key for a given language. Notice that selecting the official key is important if you want labels in the correct language from "locallang" files.
648 If the language you need is not yet a system language in TYPO3 you can use an artificial string of your choice and provide values for it via the TypoScript template where the property "_LOCAL_LANG" for most plugins will provide a way to override/add values for labels. The keys to use must be looked up in the locallang-file used by the plugin of course.]]></description>
649 <default><![CDATA[
650 ]]></default>
651 </property>
652 <property name="language_alt" type="string">
653 <description><![CDATA[If "config.language" (above) is used, this can be set to another language key which will be used for labels if a label was not found for the main language. For instance a brazil portuguese website might specify "pt" as alternative language which means the portuguese label will be shown if none was available in the main language, brazil portuguese. This feature makes sense if one language is incompletely translated and close to another language.]]></description>
654 <default><![CDATA[
655 ]]></default>
656 </property>
657 <property name="linkVars" type="string">
658 <description><![CDATA[HTTP_GET_VARS, which should be passed on with links in TYPO3. This is compiled into a string stored in $GLOBALS["TSFE"]->linkVars
659
660 The values are rawurlencoded in PHP.
661
662 You can specify a range of valid values by appending a () after each value. If this range does not match, the variable won't be appended to links. This is very important to prevent that the cache system gets flooded with forged values.
663
664 The range may containing one of these values:
665 [a]-[b] - A range of allowed integer valuesint - Only integer values are allowed[a]|[b]|[c] - A list of allowed strings (whitespaces will be removed)/[regex]/ - Match against a regular expression (PCRE style)
666
667 Example:
668 config.linkVars = L, print
669 This will add "&L=[L-value]&print=[print-value]" to all links in TYPO3.
670
671 config.linkVars = L(1-3), print
672 Same as above, but "&L=[L-value]" will only be added if the current value is 1, 2 or 3.
673 ]]></description>
674 <default><![CDATA[
675 ]]></default>
676 </property>
677 <property name="locale_all" type="string">
678 <description><![CDATA[PHP: setlocale("LC_ALL", [value]);
679 value-examples: deutsch, de_DE, danish, portuguese, spanish, french, norwegian, italian. See www.php.net for other value. Also on linux, look at /usr/share/locale/
680
681 TSFE->localeCharset is intelligently set to the assumed charset of the locale strings. This is used in stdWrap.strftime to convert locale strings to the renderCharset of the frontend.
682
683 Example:
684 This will render dates in danish made with stdWrap/strftime:
685 locale_all = danish
686 locale_all = da_DK]]></description>
687 <default><![CDATA[
688 ]]></default>
689 </property>
690 <property name="lockFilePath" type="string">
691 <description><![CDATA[This is used to lock paths to be "inside" this path.
692 Used by "filelist" in stdWrap]]></description>
693 <default><![CDATA[fileadmin/]]></default>
694 </property>
695 <property name="mainScript" type="string">
696 <description><![CDATA[This lets you specify an alternative "mainScript" which is the document that TYPO3 expects to be the default doc. This is used in form-tags and other places where TYPO3 needs to refer directly to the main-script of the application]]></description>
697 <default><![CDATA[index.php]]></default>
698 </property>
699 <property name="meaningfulTempFilePrefix" type="boolean">
700 <description><![CDATA[If set it will try to render a meaningful prefix before temporary image files.
701 Works with GIFBUILDER files (taking content from the Gifbuilder TEXT objects), menus (taking the title of the menu item) and scaled images (using original filename base).]]></description>
702 <default><![CDATA[
703 ]]></default>
704 </property>
705 <property name="message_page_is_being_generated" type="string">
706 <description><![CDATA[Alternative HTML message that appears if a page is being generated.
707 Normally when a page is being generated a temporary copy is stored in the cache-table with an expire-time of 30 seconds.
708
709 It is possible to use some keywords that are replaced with the corresponding values. Possible keywords are: ###TITLE###, ###REQUEST_URI###]]></description>
710 <default><![CDATA[
711 ]]></default>
712 </property>
713 <property name="message_preview" type="string">
714 <description><![CDATA[Alternative message in HTML that appears when the preview function is active!]]></description>
715 <default><![CDATA[
716 ]]></default>
717 </property>
718 <property name="message_preview_workspace" type="string ">
719 <description><![CDATA[Alternative message in HTML that appears when the preview function is active in a draft workspace. You can use sprintf() placeholders for Workspace title (first) and number (second).
720
721 Examples:
722 config.message_preview_workspace = <div class="previewbox">Displaying workspace named "%s" (number %s)!</div>
723 config.message_preview_workspace = <div class="previewbox">Displaying workspace number %2$s named "%1$s"!</div>]]></description>
724 <default><![CDATA[
725 ]]></default>
726 </property>
727 <property name="metaCharset" type="string">
728 <description><![CDATA[Charset used for the output document. For example in the meta tag:
729 <meta http-equiv="Content-Type" content="text/html; charset=...>
730
731 Is used for a) HTML meta-tag, b) HTTP header (unless disabled with .disableCharsetHeader) and c) xhtml prologues (if available)
732
733 If renderCharset and metaCharset are different the output content is automatically converted to metaCharset before output and likewise are values posted back to the page converted from metaCharset to renderCharset for internal processing. This conversion takes time of course so there is another good reason to use the same charset for both.]]></description>
734 <default><![CDATA[value of ".renderCharset"]]></default>
735 </property>
736 <property name="moveJsFromHeaderToFooter" type="boolean">
737 <description><![CDATA[
738 If set, all Javascript (includes and inline) will be moved to the bottom of the HTML document, which is after content and before the closing body tag
739 ]]></description>
740 <default><![CDATA[
741 ]]></default>
742 </property>
743 <property name="namespaces" type="array">
744 <description><![CDATA[array of strings
745 This property enables you to add xml namespaces (xmlns) to the html tag. The configuration
746
747 namespaces.dc = http://purl.org/dc/elements/1.1/
748 namespaces.foaf = http://xmlns.com/foaf/0.1/
749
750 will result in a html tag like
751
752 <html xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/">
753
754 This is especially useful if you want to add RDFa or microformats to your html.
755 ]]></description>
756 <default><![CDATA[
757 ]]></default>
758 </property>
759 <property name="noPageTitle" type="int">
760 <description><![CDATA[If you only want to have the sitename (from the template record) in your <title> tag, set this to 1. If the value is 2 then the <title> tag is not printed at all.
761 Please take note that this tag is required for XHTML compliant output, so you should only disable this tag if you generate it manually already.]]></description>
762 <default><![CDATA[0]]></default>
763 </property>
764 <property name="noScaleUp" type="boolean">
765 <description><![CDATA[Normally images are scaled to the size specified via TypoScript. This also forces small images to be scaled to a larger size. This is not always a good thing.
766 If this property is set, images are not allowed to be scaled up in size. This parameter clears the $this->mayScaleUp var of the class t3lib_stdgraphics (often "gifbuilder").]]></description>
767 <default><![CDATA[
768 ]]></default>
769 </property>
770 <property name="no_cache" type="boolean">
771 <description><![CDATA[If this is set to true, the page will not be cached. If set to false, it's ignored. Other parameters may have set it to true of other reasons.]]></description>
772 <default><![CDATA[-]]></default>
773 </property>
774 <property name="notification_email_charset" type="string">
775 <description><![CDATA[Alternative charset for the notification mails.]]></description>
776 <default><![CDATA[utf-8]]></default>
777 </property>
778 <property name="notification_email_encoding" type="string">
779 <description><![CDATA[This sets the encoding of plaintext emails (notification messages). The default encoding is "quoted-printable". But setting this to eg. "base64" will encode the content with base64 encoding.
780
781 Values possible:
782 base64
783 quoted-printable
784 8bit]]></description>
785 <default><![CDATA[
786 ]]></default>
787 </property>
788 <property name="notification_email_urlmode" type="string">
789 <description><![CDATA[This option allows you to handle URL's in plain text emails so long URLS of more than 76 chars are not broken. This option can be either empty or "76" or "all".
790 If the string is blank, all links in plaintext emails are untouched.
791 If it's set to 76 then all links longer then 76 characters are stored in the database and a hash is sent in the GET-var ?RDCT=[md5/20] to the index.php script which finds the proper link in the database and issues a location header (redirection).
792 If the value is "all" then ALL "http://" links in the message are converted.]]></description>
793 <default><![CDATA[
794 ]]></default>
795 </property>
796 <property name="pageGenScript" type="string">
797 <description><![CDATA[Alternative page generation script for applications using index_ts.php for initialization, caching, stating and so on. This script is included in the global scope of index_ts.php-script and thus you may include libraries here. Always use include_once for libraries.
798 Remember not to output anything from such an included script. All content must be set into $TSFE->content. Take a look at typo3/sysext/cms/tslib/pagegen.php
799
800 NOTE: This option is ignored if
801
802 $TYPO3_CONF_VARS["FE"]["noPHPscriptInclude"]=1;
803
804 is set in localconf.php.]]></description>
805 <default><![CDATA[typo3/sysext/cms/tslib/pagegen.php]]></default>
806 </property>
807 <property name="pageRendererTemplateFile" type="string">
808 <description><![CDATA[
809 Sets the template for page renderer class (t3lib_PageRenderer).
810
811 Example:
812
813 pageRendererTemplateFile = fileadmin/test_pagerender.html
814 ]]></description>
815 <default><![CDATA[
816 ]]></default>
817 </property>
818 <property name="pageTitleFirst" type="boolean">
819 <description><![CDATA[If set (and the page title is printed) then the page-title will be printed BEFORE the template title.]]></description>
820 <default><![CDATA[
821 ]]></default>
822 </property>
823 <property name="prefixLocalAnchors" type="string">
824 <description><![CDATA[If set to one of the keywords, the content will have all local anchors in links prefixed with the path of the script. Basically this means that <a href="#"> will be transformed to <a href="path/path/script?params#">. This procedure is necessary if the <base> tag is set in the script (eg. if "realurl" extension is used to produce Speaking URLs).
825
826 Keywords are the same as for "xhtml_cleaning", see above.]]></description>
827 <default><![CDATA[
828 ]]></default>
829 </property>
830 <property name="removeDefaultCss" type="boolean">
831 <description><![CDATA[Remove CSS generated by _CSS_DEFAULT_STYLE configuration of extensions.]]></description>
832 <default><![CDATA[false]]></default>
833 </property>
834 <property name="removeDefaultJS" type="string">
835 <description><![CDATA[If set, the default JavaScript in the header will be removed.
836 The default JavaScript is the blurLink function and browser detection variables.
837
838 Special case: if the value is "external" then the default JavaScript is written to a temporary file and included from that file. See "inlineStyle2TempFile" below.
839
840 Depends on the compatibility mode (see Tools>Install>Update wizard):
841 compatibility mode < 4.0:   0
842 compatibility mode >= 4.0:   1
843
844 Example:
845 config.removeDefaultJS = external
846 config.removeDefaultJS = 1]]></description>
847 <default><![CDATA[
848 ]]></default>
849 </property>
850 <property name="minifyJS" type="boolean">
851 <description><![CDATA[This setting is deprecated and will be removed with TYPO3 4.8! Use config.compressJs instead, which has the same effect.]]></description>
852 <default><![CDATA[false]]></default>
853 </property>
854 <property name="minifyCSS" type="boolean">
855 <description><![CDATA[This setting is deprecated and will be removed with TYPO3 4.8! Use config.compressCss instead, which has the same effect.]]></description>
856 <default><![CDATA[false]]></default>
857 </property>
858 <property name="compressJs" type="boolean">
859 <description><![CDATA[Enabling this option together with $TYPO3_CONF_VARS['FE']['compressionLevel'] in the Install Tool delivers Frontend JavaScript files using GZIP compression.
860
861 This can significantly reduce file sizes of linked JavaScript files and thus decrease loading times.
862
863 Please not that this requires .htaccess to be adjusted, as otherwise the files will not be readable by the user agent. Please see the description of $TYPO3_CONF_VARS['FE']['compressionLevel'] in the Install Tool.
864
865 Example:
866
867 config.compressJs = 1
868 ]]></description>
869 <default><![CDATA[false]]></default>
870 </property>
871 <property name="compressCss" type="boolean">
872 <description><![CDATA[If set, CSS files will be minified and compressed.
873
874 Minification will remove all excess space. The more significant compression step (using Gzip compression) requires $TYPO3_CONF_VARS['FE']['compressionLevel'] to be enabled in the Install Tool together with the gzip-related compressionLevel options in .htaccess, as otherwise the files will not be readable by the user agent.
875
876 Example:
877
878 config.compressCss = 1]]></description>
879 <default><![CDATA[false]]></default>
880 </property>
881 <property name="concatenateJs" type="boolean">
882 <description><![CDATA[Setting config.concatenateJs merges Javascript files referenced in the Frontend together.
883
884 Example:
885
886 config.concatenateJs = 1
887
888 Note: TYPO3 comes with a built-in concatenation handler, but you can also register your own one using $GLOBALS['TYPO3_CONF_VARS']['FE']['jsConcatenateHandler'].
889
890 Example:
891
892 $GLOBALS['TYPO3_CONF_VARS']['FE']['jsConcatenateHandler'] = t3lib_extMgm::extPath($_EXTKEY) . 'Classes/class.tx_myext_jsConcatenateHandler.php:tx_myext_jsConcatenateHandler->concatenateJs';]]></description>
893 <default><![CDATA[false]]></default>
894 </property>
895 <property name="concatenateCss" type="boolean">
896 <description><![CDATA[Setting config.concatenateCss merges Stylesheet files referenced in the Frontend together.
897
898 Example:
899
900 config.concatenateCss = 1
901
902 Note: TYPO3 comes with a built-in concatenation handler, but you can also register your own using $GLOBALS['TYPO3_CONF_VARS']['FE']['cssConcatenateHandler'].
903
904 Example:
905
906 $GLOBALS['TYPO3_CONF_VARS']['FE']['cssConcatenateHandler'] = t3lib_extMgm::extPath($_EXTKEY) . 'Classes/class.tx_myext_cssConcatenateHandler.php:tx_myext_cssConcatenateHandler->concatenateCss';]]></description>
907 <default><![CDATA[false]]></default>
908 </property>
909 <property name="renderCharset" type="string">
910 <description><![CDATA[Charset used for rendering internally of the page content. It is highly recommended that this value is the same as the charset of the content coming from the main data source (eg. the database). Thus you don't need to do any other conversion.
911 All strings from locallang files and locale strings are (and should be) converted to "renderCharset" during rendering.
912
913 If you need another output charset than the render charset, see "metaCharset" below.
914
915 ]]></description>
916 <default><![CDATA[UTF-8]]></default>
917 </property>
918 <property name="sendCacheHeaders" type="boolean">
919 <description><![CDATA[If set, TYPO3 will output cache-control headers to the client based mainly on  whether the page was cached internally. This feature allows client browsers and/or reverse proxies to take load of TYPO3 websites.
920
921 The conditions for allowing client caching are:
922 page was cachedNo *_INT or *_EXT objects were on the page (eg. USER_INT)No frontend user is logged inNo backend user is logged in
923
924 If these conditions are met, the headers sent are:
925 Last-Modified [SYS_LASTCHANGED of page id]Expires [expire time of page cache]Etag [md5 of content]Cache-Control: max-age: [seconds til expiretime]Pragma: public
926
927 In case caching is not allowed, these headers are sent to avoid client caching:
928 Cache-Control: private
929
930 Notice that enabling the browser caches means you have to consider how log files are written. Because when a page is cached on the client it will not invoke a request to the webserver, thus not writing the request to the log. There should be ways to circumvent these problems but they are outside the domain of TYPO3 in any case.
931
932 Tip: Enabling cache-control headers might confuse editors seeing old content served from the browser cache. "Shift-Reload" will bypass both browser- and reverse-proxy caches and even make TYPO3 regenerate the page. Teach them that trick!
933
934 Thanks to Ole Tange, www.forbrug.dk for co-authoring this feature.]]></description>
935 <default><![CDATA[
936 ]]></default>
937 </property>
938 <property name="sendCacheHeaders_onlyWhenLoginDeniedInBranch" type="boolean">
939 <description><![CDATA[If this is set, then cache-control headers allowing client caching is sent only if user-logins are disabled for the branch. This feature makes it easier to manage client caching on sites where you have a mixture of static pages and dynamic sections with user logins.
940
941 The background problem is this: In TYPO3 the same URL can show different content depending on whether a user is logged in or not. If a user is logged in, cache-headers will never allow client caching. But if the same URL was visited without a login prior to the login (allowing caching) the user will still see the page from cache when logged in (and so thinks he is not logged in anyway)! The only general way to prevent this is to have a different URL for pages when users are logged in (which the extension "realurl" can accomplish).
942
943 Another way to solve the problem is using this option in combination with disabling and enabling logins in various sections of the site. In the page records ("Advanced" page types) you can disable frontend user logins for branches of the page tree. Since many sites only needs the login in a certain branch of the page tree, disabling it in all other branches makes it much easier to use cache-headers in combination with logins; Cache-headers should simply be sent when logins are not allowed and never be send when logins are allowed! Then there will never be problems with logins and same-URLs.]]></description>
944 <default><![CDATA[
945 ]]></default>
946 </property>
947 <property name="setJS_mouseOver" type="boolean">
948 <description><![CDATA[If set, the over() and out() JavaScript functions are forced to be included]]></description>
949 <default><![CDATA[
950 ]]></default>
951 </property>
952 <property name="setJS_openPic" type="boolean">
953 <description><![CDATA[If set, the openPic JavaScript function is forced to be included]]></description>
954 <default><![CDATA[
955 ]]></default>
956 </property>
957 <property name="spamProtectEmailAddresses" type="string">
958 <description><![CDATA["ascii" / -10 to 10
959 If set, then all email addresses in typolinks will be encrypted so spam bots cannot detect them.
960
961 If you set this value to a number, then the encryption is simply an
962 offset of character values. If you set this value to "-2" then all
963 characters will have their ASCII value offset by "-2". To make this
964 possible, a little JavaScript code is added to every generated web page!
965 (It is recommended to set the value in the range from -5 to 1 since setting it to >= 2 means a "z" is converted to "|" which is a special character in TYPO3 tables syntax – and that might confuse columns in tables. Now hardcoded range)
966
967 Alternatively you can set this value to the keyword "ascii". This way every
968 character of the "mailto:" address will be translated to a Unicode HTML
969 notation. Have a look at the example to see how this works.
970
971 Example:
972 mailto:a@b.c will be converted to
973 mailto:&#97;&#64;&#98;&#46;&#99;
974 The big advantage of this method is that it doesn't need any JavaScript!]]></description>
975 <default><![CDATA[
976 ]]></default>
977 </property>
978 <property name="spamProtectEmailAddresses_atSubst" type="string">
979 <description><![CDATA[Substitute label for the at-sign (@).]]></description>
980 <default><![CDATA[(at)]]></default>
981 </property>
982 <property name="spamProtectEmailAddresses_lastDotSubst" type="string">
983 <description><![CDATA[Substitute label for the last dot in the email address.
984 Example: (dot)]]></description>
985 <default><![CDATA[Default: . ( <= just a simple dot)]]></default>
986 </property>
987 <property name="stat" type="boolean">
988 <description><![CDATA[Enable stat logging at all.]]></description>
989 <default><![CDATA[true]]></default>
990 </property>
991 <property name="stat_apache" type="boolean">
992 <description><![CDATA[Enable logging to the logfile "stat_apache_logfile"]]></description>
993 <default><![CDATA[false]]></default>
994 </property>
995 <property name="stat_apache_logfile" type="string">
996 <description><![CDATA[This defines the name of the logfile where TYPO3 writes an Apache-style logfile to. The location of the directory is defined by $TYPO3_CONF_VARS["FE"]["logfile_dir"]  which must exist and be writable. It can be relative (to PATH_site) or absolute, but in any case it must be within the regular allowed paths of TYPO3 (meaning for absolute paths that it must be within the "lockRootDir" set up in $TYPO3_CONF_VARS).
997
998 It is also possible to use date markers in the filename as they are provided by the PHP function strftime(). This will enable a natural rotation of the logfiles.
999
1000 Example:
1001 config.stat_apache_logfile = typo3_%Y%m%d.log
1002
1003 This will create daily log files (eg. typo3_20060321.log).]]></description>
1004 <default><![CDATA[
1005 ]]></default>
1006 </property>
1007 <property name="stat_apache_niceTitle" type="string">
1008 <description><![CDATA[boolean / string
1009 If set, the URL will be transliterated from the renderCharset to ASCII (eg ä => ae, à => a, &#945; "alpha" => a), which yields nice and readable page titles in the log. All non-ASCII characters that cannot be converted will be changed to underscores.
1010
1011 If set to "utf-8", the page title will be converted to UTF-8 which results
1012 in even more readable titles, if your log analyzing software supports it.]]></description>
1013 <default><![CDATA[
1014 ]]></default>
1015 </property>
1016 <property name="stat_apache_noHost" type="boolean">
1017 <description><![CDATA[If true the HTTP_HOST is - if available - NOT inserted instead of the IP-address]]></description>
1018 <default><![CDATA[
1019 ]]></default>
1020 </property>
1021 <property name="stat_apache_noRoot" type="boolean">
1022 <description><![CDATA[If set, the root part (level 0) of the path will be removed from the path. This makes a shorter name in case you have only a redundant part like "home" or "my site".]]></description>
1023 <default><![CDATA[
1024 ]]></default>
1025 </property>
1026 <property name="stat_apache_notExtended" type="boolean">
1027 <description><![CDATA[If true the logfile is NOT written in Apache extended format]]></description>
1028 <default><![CDATA[
1029 ]]></default>
1030 </property>
1031 <property name="stat_apache_pagenames" type="string">
1032 <description><![CDATA[The "pagename" simulated for apache.
1033 Default:    "[path][title]--[uid].html"
1034 Codes:
1035 [title] = inserts title, no special characters and shortend to 30 chars.
1036 [uid] = the id
1037 [alias] = any alias
1038 [type] = the type (typeNum)
1039 [path] = the path of the page.]]></description>
1040 <default><![CDATA[
1041 ]]></default>
1042 </property>
1043 <property name="stat_excludeBEuserHits" type="boolean">
1044 <description><![CDATA[If set a pagehit is not logged if a user is logged in into TYPO3.]]></description>
1045 <default><![CDATA[false]]></default>
1046 </property>
1047 <property name="stat_excludeIPList" type="string">
1048 <description><![CDATA[list of strings
1049 If the REMOTE_ADDR is in the list of IP-addresses, it's also not logged.
1050 Can use wildcard, eg. "192.168.1.*"]]></description>
1051 <default><![CDATA[
1052 ]]></default>
1053 </property>
1054 <property name="stat_mysql" type="boolean">
1055 <description><![CDATA[Enable logging to the MySQL table sys_stat.]]></description>
1056 <default><![CDATA[false]]></default>
1057 </property>
1058 <property name="stat_pageLen" type="int">
1059 <description><![CDATA[int 1-100
1060 The length of the page name (at the end of the path) written to the logfile/database.]]></description>
1061 <default><![CDATA[30]]></default>
1062 </property>
1063 <property name="stat_titleLen" type="int">
1064 <description><![CDATA[int 1-100
1065 The length of the page names in the path written to logfile/database]]></description>
1066 <default><![CDATA[20]]></default>
1067 </property>
1068 <property name="stat_typeNumList" type="intList">
1069 <description><![CDATA[List of pagetypes that should be registered in the statistics table, sys_stat.
1070 If no types are listed, all types are logged.
1071 Default is "0,1" which normally logs all hits on framesets and hits on content keeping pages. Of course this depends on the template design.]]></description>
1072 <default><![CDATA[0,1]]></default>
1073 </property>
1074 <property name="sword_noMixedCase" type="boolean">
1075 <description><![CDATA[Used by the parseFunc-substitution of search Words (sword):
1076 If set, the words MUST be the exact same case as the search word was.]]></description>
1077 <default><![CDATA[
1078 ]]></default>
1079 </property>
1080 <property name="sword_standAlone" type="boolean">
1081 <description><![CDATA[Used by the parseFunc-substitution of search Words (sword):
1082 If set, the words MUST be surrounded by whitespace in order to be marked up.]]></description>
1083 <default><![CDATA[
1084 ]]></default>
1085 </property>
1086 <property name="sys_language_mode" type="string">
1087 <description><![CDATA[Setting various modes of handling localization.
1088 The syntax is "[keyword] ; [value]".
1089
1090 Possible keywords are:
1091
1092 [default] - The system will look for a translation of the page (from "Alternative Page Language" table) and if it is not found it will fall back to the default language and display that.
1093
1094 content_fallback - [ Recommended ] The system will always operate with the selected language even if the page is not translated with a page overlay record. This will keep menus etc. translated. However, the content on the page can still fall back to another language, defined by the value of this keyword, eg. "content_fallback ; 1,0" to fall back to the content of sys_language_uid 1 and if that is not present either, to default (0)
1095
1096 strict - The system will report an error if the requested translation does not exist. Basically this means that all pages with gray background in the Web>Info / Localization overview module will fail (they would otherwise fall back to default language in one or another way)
1097
1098 ignore - The system will stay with the selected language even if the page is not translated and there's no content available in this language, so you can handle that situation on your own then.]]></description>
1099 <default><![CDATA[
1100 ]]></default>
1101 </property>
1102 <property name="sys_language_overlay" type="string">
1103 <description><![CDATA[boolean / keyword
1104 If set, records from certain tables selected by the CONTENT cObject using the "languageField" setting will select the default language (0) instead of any language set by sys_language_uid / sys_language_mode. In addition the system will look for a translation of the selected record and overlay configured fields.
1105 The requirements for this is that the table is configured with "languageField" and "transOrigPointerField" in the [ctrl] section of $TCA. Also, exclusion of certain fields can be done with the "l10n_mode" directive in the field-configuration of $TCA.
1106
1107 For backend administration this requires that you configure the "Web>Page" module to display content elements accordingly; That each default element is shown and next to it any translation found. This configuration can be done with Page TSconfig for a section of the website using the object path "mod.web_layout.defLangBinding = 1".
1108
1109 Keyword:
1110 hideNonTranslated : If this keyword is used a record that has no translation will not be shown. The default is that records with no translation will show up in the default language.]]></description>
1111 <default><![CDATA[
1112 ]]></default>
1113 </property>
1114 <property name="sys_language_softExclude" type="string">
1115 <description><![CDATA[Setting additional "exclude" flags for l10n_mode in TCA for frontend rendering. Works exactly like sys_language_softMergeIfNotBlank (see that for details - same Syntax!).
1116
1117 Fields set in this property will override if the same field is set for "sys_language_softMergeIfNotBlank".]]></description>
1118 <default><![CDATA[
1119 ]]></default>
1120 </property>
1121 <property name="sys_language_softMergeIfNotBlank" type="string">
1122 <description><![CDATA[Setting additional "mergeIfNotBlank" fields from TypoScript.
1123
1124 Background:
1125 In TCA you can configure "l10n_mode" - localization mode - for each field. Two of the options affect how the frontend displays content; The values "exclude" and "mergeIfNotBlank" (see "TYPO3 Core API" document for details). The first ("exclude") simply means that the field when found in a translation of a record will not be overlaid the default records field value. The second ("mergeIfNotBlank") means that it will be overlaid only if it has a non-blank value.
1126 Since it might be practical to set up fields for "mergeIfNotBlank" on a per-site basis this options allows you to override additional fields from tables.
1127
1128 Syntax:
1129  [table]:[field],  [table]:[field],  [table]:[field], ...
1130
1131 Example:
1132 config.sys_language_softMergeIfNotBlank = tt_content:image , tt_content:header
1133
1134 This setting means that the header and image field of content elements will be used from the translation only if they had a non-blank value. For the image field this might be very practical because it means that the image(s) from the default translation will be used unless other images are inserted!]]></description>
1135 <default><![CDATA[
1136 ]]></default>
1137 </property>
1138 <property name="sys_language_uid" type="int">
1139 <description><![CDATA[This value points to the uid of a record from the "sys_language" table and if set, this means that various parts of the frontend display code will select records which are assigned to this language. See ->SELECT
1140
1141 Internally, the value is depending on whether a Alternative Page Language record can be found with that language. If not, the value will default to zero (default language) except if "sys_language_mode" is set to a value like "content_fallback".]]></description>
1142 <default><![CDATA[
1143 ]]></default>
1144 </property>
1145 <property name="titleTagFunction " type="string">
1146 <description><![CDATA[function-name
1147 Passes the default <title>-tag content to this function. No typoScript parameters are passed though.]]></description>
1148 <default><![CDATA[
1149 ]]></default>
1150 </property>
1151 <property name="typolinkCheckRootline" type="boolean">
1152 <description><![CDATA[If set, then every "typolink" is checked whether it's linking to a page within the current rootline of the site.
1153 If not, then TYPO3 searches for the first found domain record (without redirect) in that rootline from out to in.
1154 If found (another domain), then that domain is prepended the link, the external target is used instead and thus the link jumps to the page in the correct domain.]]></description>
1155 <default><![CDATA[
1156 ]]></default>
1157 </property>
1158 <property name="typolinkEnableLinksAcrossDomains" type="boolean">
1159 <description><![CDATA[This option enables to create links across domains using current domain's linking scheme.
1160
1161 If this option is not set, then all cross-domain links will be generated as
1162
1163 "http://domain.tld/index.php?id=12345" (where 12345 is page id). Setting this option requires that domains, where pages are linked, have the same configuration for:
1164
1165 - linking scheme (i.e. all use RealURL or CoolURI but not any mixture)
1166 - all domains have identical localization settings (config.sys_language_XXX directives)
1167 - all domains have the same set of languages defined
1168
1169 This option implies "config.typolinkCheckRootline=1", which will be activated automatically. Setting value of "config. typolinkCheckRootline" inside TS template will have no effect.
1170
1171 Disclaimer: it must be understood that while link is generated to another domain, it is still generated in the context of current domain. No side effects are known at the time of writing of this documentation but they may exist. If any side effects are found, this documentation will be updated to include them.]]></description>
1172 <default><![CDATA[
1173 ]]></default>
1174 </property>
1175 <property name="typolinkLinkAccessRestrictedPages" type="string">
1176 <description><![CDATA[integer (page id) / keyword "NONE"
1177 If set, typolinks pointing to access restricted pages will still link to the page even though the page cannot be accessed. If the value of this setting is an integer it will be interpreted as a page id to which the link will be directed.
1178 If the value is "NONE" the original link to the page will be kept although it will generate a page-not-found situation (which can of course be picked up properly by the page-not-found handler and present a nice login form).
1179
1180 See "showAccessRestrictedPages" for menu objects as well (similar feature for menus)
1181
1182 Example:
1183 config.typolinkLinkAccessRestrictedPages = 29
1184 config.typolinkLinkAccessRestrictedPages_addParams = &return_url=###RETURN_URL###&pageId=###PAGE_ID###
1185
1186 Will create a link to page with id 29 and add GET parameters where the return URL and original page id is a part of it.]]></description>
1187 <default><![CDATA[
1188 ]]></default>
1189 </property>
1190 <property name="typolinkLinkAccessRestrictedPages_addParams" type="string">
1191 <description><![CDATA[See "typolinkLinkAccessRestrictedPages" above]]></description>
1192 <default><![CDATA[
1193 ]]></default>
1194 </property>
1195 <property name="uniqueLinkVars" type="boolean">
1196 <description><![CDATA[It might happen that TYPO3 generates links with the same parameter twice or more. This is no problem because only the last parameter is used, thus the problem is just a cosmetical one.]]></description>
1197 <default><![CDATA[0]]></default>
1198 </property>
1199 <property name="xhtmlDoctype" type="string">
1200 <description><![CDATA[Sets the document type for the XHTML version of the generated page.
1201
1202 If config.doctype is set to a string then config.xhtmlDoctype must be set to one of these keywords:
1203
1204 "xhtml_trans" for XHTML 1.0 Transitional doctype.
1205 "xhtml_frames" for XHTML 1.0 Frameset doctype.
1206 "xhtml_strict" for XHTML 1.0 Strict doctype.
1207 "xhtml_basic" for XHTML basic doctype.
1208 "xhtml_11" for XHTML 1.1 doctype.
1209 "xhtml_2" for XHTML 2 doctype.
1210
1211
1212 This is an example to use MathML 2.0 in an XHTML 1.1 document:
1213
1214 config.doctype (
1215 <!DOCTYPE html
1216 PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0//EN"
1217 "http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd">
1218 )
1219 config.xhtmlDoctype = xhtml_11
1220
1221 Default:
1222 same as config.doctype if set to a keyword]]></description>
1223 <default><![CDATA[
1224 ]]></default>
1225 </property>
1226 <property name="xhtml_cleaning" type="string">
1227 <description><![CDATA[Tries to clean up the output to make it XHTML compliant and a bit more. THIS IS NOT COMPLETE YET, but a "pilot" to see if it makes sense anyways. For now this is what is done:
1228
1229 What it does at this point:
1230 - All tags (img,br,hr) is ended with "/>" - others?
1231 - Lowercase for elements and attributes
1232 - All attributes in quotes
1233 - Add "alt" attribute to img-tags if it's not there already.
1234
1235 What it does NOT do (yet) according to XHTML specs.:
1236 - Wellformedness: Nesting is NOT checked
1237 - name/id attribute issue is not observed at this point.
1238 - Certain nesting of elements not allowed. Most interesting, <PRE> cannot contain img, big,small,sub,sup ...
1239 - Wrapping scripts and style element contents in CDATA - or alternatively they should have entitites converted.
1240 - Setting charsets may put some special requirements on both XML declaration/ meta-http-equiv. (C.9)
1241 - UTF-8 encoding is in fact expected by XML!!
1242 - stylesheet element and attribute names are NOT converted to lowercase
1243 - ampersands (and entities in general I think) MUST be converted to an entity reference! (&amps;). This may mean further conversion of non-tag content before output to page. May be related to the charset issue as a whole.
1244 - Minimized values not allowed: Must do this: selected="selected"
1245
1246 Please see the class t3lib_parsehtml for details.
1247 You can enable this function by the following values:
1248
1249 all = the content is always processed before it may be stored in cache.
1250 cached = only if the page is put into the cache,
1251 output = only the output code just before it's echoed out.]]></description>
1252 <default><![CDATA[
1253 ]]></default>
1254 </property>
1255 <property name="xmlprologue" type="string">
1256 <description><![CDATA[If empty (not set) then the default XML 1.0 prologue is set, when the doctype is set to a known keyword (eg xhtml_11):
1257
1258 <?xml version="1.0" encoding="[config.renderCharset]">
1259
1260 If set to one of the know keywords then a standard prologue will be set:
1261 "xml_10" XML 1.0 prologue (see above)
1262 "xml_11" XML 1.1 prologue
1263
1264 If "none" then the default XML prologue is not set.
1265 Any other string is used as the XML prologue itself.]]></description>
1266 <default><![CDATA[
1267 ]]></default>
1268 </property>
1269 </type>
1270 <type id="CONTENT">
1271 <property name="renderObj" type="cObj">
1272 <description><![CDATA[
1273 ]]></description>
1274 <default><![CDATA[< [tablename]]]></default>
1275 </property>
1276 <property name="select" type="select">
1277 <description><![CDATA[The SQL-statement is set here!]]></description>
1278 <default><![CDATA[
1279 ]]></default>
1280 </property>
1281 <property name="slide" type="slide">
1282 <description><![CDATA[int/stdWrap
1283 If set and no content element is found by the select command, then the rootLine will be traversed back until some content is found.
1284
1285 Possible values are "-1" (slide back up to the siteroot), "1" (only the current level) and "2" (up from one level back).
1286
1287 Use -1 in combination with collect.
1288
1289 .collect (integer/stdWrap): If set, all content elements found on current and parent pages will be collected. Otherwise, the sliding would stop after the first hit. Set this value to the amount of levels to collect on, or use "-1" to collect up to the siteroot.
1290 .collectFuzzy (boolean/stdWrap): Only useful in collect mode. If no content elements have been found for the specified depth in collect mode, traverse further until at least one match has occurred.
1291 .collectReverse (boolean/stdWrap): Change order of elements in collect mode. If set, elements of the current page will be on the bottom.]]></description>
1292 <default><![CDATA[
1293 ]]></default>
1294 </property>
1295 <property name="stdWrap" type="stdWrap">
1296 <description><![CDATA[
1297 ]]></description>
1298 <default><![CDATA[
1299 ]]></default>
1300 </property>
1301 <property name="table" type="stdWrap">
1302 <description><![CDATA[TableName/stdWrap
1303 The table, the content should come from.
1304 In standard-configurations this will be "tt_content"
1305 NOTE: Only tables allowed are "pages" or tables prefixed with one of these: "tt_", "tx_", "ttx_", "fe_", "user_" or "static_"]]></description>
1306 <default><![CDATA[
1307 ]]></default>
1308 </property>
1309 <property name="wrap" type="stdWrap">
1310 <description><![CDATA[wrap/stdWrap
1311 Wrap the whole content-story...]]></description>
1312 <default><![CDATA[
1313 ]]></default>
1314 </property>
1315 </type>
1316 <type id="slide" extends="stdWrap">
1317 <property name="collect" type="stdWrap">
1318 <description><![CDATA[int/stdWrap
1319 If set, all content elements found on current and parent pages will be collected. Otherwise, the sliding would stop after the first hit. Set this value to the amount of levels to collect on, or use “-1” to collect up to the siteroot.
1320 ]]></description>
1321 <default><![CDATA[
1322 ]]></default>
1323 </property>
1324 <property name="collectFuzzy" type="stdWrap">
1325 <description><![CDATA[boolean/stdWrap
1326 Only useful in collect mode. If no content elements have been found for the specified depth in collect mode, traverse further until at least one match has occurred.
1327 ]]></description>
1328 <default><![CDATA[
1329 ]]></default>
1330 </property>
1331 <property name="collectReverse" type="stdWrap">
1332 <description><![CDATA[boolean/stdWrap
1333 Change order of elements in collect mode. If set, elements of the current page will be at the bottom.
1334 ]]></description>
1335 <default><![CDATA[
1336 ]]></default>
1337 </property>
1338 </type>
1339 <type id="CTABLE">
1340 <property name="bm" type="stdWrap">
1341 <description><![CDATA[CARRAY + TDParams/stdWrap
1342 bottomMenu]]></description>
1343 <default><![CDATA[
1344 ]]></default>
1345 </property>
1346 <property name="c" type="stdWrap">
1347 <description><![CDATA[CARRAY + TDParams/stdWrap
1348 content-cell ]]></description>
1349 <default><![CDATA[
1350 ]]></default>
1351 </property>
1352 <property name="cMargins" type="stdWrap">
1353 <description><![CDATA[margins/stdWrap
1354 Distance around the content-cell "c"]]></description>
1355 <default><![CDATA[0,0,0,0]]></default>
1356 </property>
1357 <property name="cWidth" type="stdWrap">
1358 <description><![CDATA[pixels/stdWrap
1359 Width of the content-cell "c"]]></description>
1360 <default><![CDATA[
1361 ]]></default>
1362 </property>
1363 <property name="lm" type="stdWrap">
1364 <description><![CDATA[CARRAY+TDParams/stdWrap
1365 leftMenu]]></description>
1366 <default><![CDATA[
1367 ]]></default>
1368 </property>
1369 <property name="offset" type="stdWrap">
1370 <description><![CDATA[x,y/stdWrap
1371 Offset from upper left corner]]></description>
1372 <default><![CDATA[0,0 = intet]]></default>
1373 </property>
1374 <property name="rm" type="stdWrap">
1375 <description><![CDATA[CARRAY+TDParams/stdWrap
1376 rightMenu]]></description>
1377 <default><![CDATA[
1378 ]]></default>
1379 </property>
1380 <property name="tableParams" type="stdWrap">
1381 <description><![CDATA[<TABLE>-params/stdWrap
1382 ]]></description>
1383 <default><![CDATA[border=0 cellspacing=0 cellpadding=0]]></default>
1384 </property>
1385 <property name="tm" type="stdWrap">
1386 <description><![CDATA[CARRAY+TDParams/stdWrap
1387 topMenu]]></description>
1388 <default><![CDATA[
1389 ]]></default>
1390 </property>
1391 <property name="stdWrap" type="stdWrap">
1392 <description><![CDATA[
1393 ]]></description>
1394 <default><![CDATA[
1395 ]]></default>
1396 </property>
1397 </type>
1398 <type id="EDITPANEL">
1399 <property name="allow" type="string">
1400 <description><![CDATA[Define which functions are accessible. Further this list may be reduced, if the BE_USER does not have permission to perform the action
1401 Values should be listed separated by comma. This is the options you can choose between:
1402 toolbar,edit,new,delete,move,hide
1403 (toolbar is a general list of icons regarding the page, so use this for pagerecords only)]]></description>
1404 <default><![CDATA[
1405 ]]></default>
1406 </property>
1407 <property name="edit.displayRecord" type="boolean">
1408 <description><![CDATA[If set, then the record edited is displayed above the editing form.]]></description>
1409 <default><![CDATA[
1410 ]]></default>
1411 </property>
1412 <property name="innerWrap" type="wrap">
1413 <description><![CDATA[Wraps the edit panel]]></description>
1414 <default><![CDATA[
1415 ]]></default>
1416 </property>
1417 <property name="label" type="string">
1418 <description><![CDATA[Title for the panel. You can insert the record title with %s
1419
1420 Example:
1421 Section: <B>%s</B>]]></description>
1422 <default><![CDATA[
1423 ]]></default>
1424 </property>
1425 <property name="line" type="int">
1426 <description><![CDATA[boolean / int
1427 If set, a black line will appear after the panel. This value will indicate the distance from the black line to the panel]]></description>
1428 <default><![CDATA[
1429 ]]></default>
1430 </property>
1431 <property name="newRecordFromTable" type="string">
1432 <description><![CDATA[Will display a panel for creation of new element (in the top of list) on the page from that table.]]></description>
1433 <default><![CDATA[
1434 ]]></default>
1435 </property>
1436 <property name="newRecordInPid" type="int">
1437 <description><![CDATA[Define a page ID where new records (except new pages) will be created.]]></description>
1438 <default><![CDATA[
1439 ]]></default>
1440 </property>
1441 <property name="onlyCurrentPid" type="boolean">
1442 <description><![CDATA[If set, only records with a pid matching the current id (TSFE->id) will be shown with the panel.]]></description>
1443 <default><![CDATA[
1444 ]]></default>
1445 </property>
1446 <property name="outerWrap" type="wrap">
1447 <description><![CDATA[Wraps the whole edit panel including the black line (if configured)]]></description>
1448 <default><![CDATA[
1449 ]]></default>
1450 </property>
1451 <property name="previewBorder" type="int">
1452 <description><![CDATA[boolean / int
1453 If set, the hidden/starttime/endtime/fe_user elements which are previewed will have a border around.
1454 The integer value denotes the thickness of the border]]></description>
1455 <default><![CDATA[
1456 ]]></default>
1457 </property>
1458 <property name="previewBorder.innerWrap" type="string">
1459 <description><![CDATA[wrap / HTML color
1460 innerWrap wraps the content elements (including the icons) inside the preview border (an HTML table).
1461
1462 outerWrap wraps the whole content element including the border.
1463
1464 color denotes the color of the border.]]></description>
1465 <default><![CDATA[
1466 ]]></default>
1467 </property>
1468 </type>
1469 <type id="FE_TABLE">
1470 <property name="allowEdit" type="string">
1471 <description><![CDATA[allowEdit.[field]
1472 Same as above ("allowNew") but this controls which fields that may be written in case of an update of a record (and not a new submission)
1473 Please pay attension to the property below!  ("overrideEdit")]]></description>
1474 <default><![CDATA[
1475 ]]></default>
1476 </property>
1477 <property name="allowNew" type="string">
1478 <description><![CDATA[allowNew.[field]
1479 This property is in charge of which fields that may be written from the frontend.
1480
1481 Example:
1482 This defines that subject is a field, that may be submitted from the frontend. If a value is not submitted, subject is filled with the default value (see above).
1483 The field "hidden" on the other hand cannot be changed from the frontend. "hidden" will gain the value from the default definition (see above). If fields are set to "0" (zero) it's the same as if they were not defined in this array.
1484
1485 allowNew {
1486   subject = 1
1487   hidden = 0
1488 }]]></description>
1489 <default><![CDATA[
1490 ]]></default>
1491 </property>
1492 <property name="autoInsertPID" type="boolean">
1493 <description><![CDATA[Works with new records: Insert automatically the PID of the page, where the submitted data is sent to. Any "pid" supplied from the submitted data will override. This is for convenience.]]></description>
1494 <default><![CDATA[
1495 ]]></default>
1496 </property>
1497 <property name="default" type="string">
1498 <description><![CDATA[default.[field] This property is in charge of which default-values is used for the table:
1499
1500 Example:
1501 This defines the default values used for new records. These values will be overridden with any value submitted instead (as long as the submitted fields are allowed due to "allowNew")
1502 default {
1503   subject = This is the default subject value!
1504   hidden = 1
1505   parent = 0
1506 }]]></description>
1507 <default><![CDATA[
1508 ]]></default>
1509 </property>
1510 <property name="doublePostCheck" type="string">
1511 <description><![CDATA[string (fieldname)
1512 Specifies a fieldname (integer) into which an integer-hash compiled of the submitted data is inserted. If the field is set, then submissions are checked whether another record with this value already exists. If so, the record is NOT inserted, because it's expected to be a "double post" (posting the same data more than once)]]></description>
1513 <default><![CDATA[
1514 ]]></default>
1515 </property>
1516 <property name="overrideEdit" type="string">
1517 <description><![CDATA[This works like default-values above but is values inserted after the submitted values has beed processed. This means that opposite to default-values overwritten by the submitted values, these values override the submitted values.
1518
1519 Example:
1520 In this case overrideEdit secures that if a user updates his record (if he "own" it) the "hidden"-field will be set no matter what.
1521
1522 overrideEdit {
1523   hidden = 1
1524 }]]></description>
1525 <default><![CDATA[
1526 ]]></default>
1527 </property>
1528 <property name="processScript" type="string">
1529 <description><![CDATA[Include-script to be used for processing of incoming data to the table. The script is included from a function in the class tslib_fetce
1530 This is the really important option, because whether or not you are going to utilize the "cleaning"/"authorization" features of the properties above depend on how you write your script to process data and put it in the database.
1531 A very good example is to look at "media/scripts/guest_submit.inc"]]></description>
1532 <default><![CDATA[
1533 ]]></default>
1534 </property>
1535 <property name="separator" type="string">
1536 <description><![CDATA[Separator character used when the submitted data is an array from eg. a multiple selector box.]]></description>
1537 <default><![CDATA[chr(10) (linebreak)]]></default>
1538 </property>
1539 <property name="userIdColumn" type="string">
1540 <description><![CDATA[string (field)
1541 This is a string that points to the column of a record where the user-id of the current fe_user should be inserted. This fe_user-uid is inserted/updated both by "new" and "edit"]]></description>
1542 <default><![CDATA[
1543 ]]></default>
1544 </property>
1545 </type>
1546 <type id="FILE">
1547 <property name="altText" type="stdWrap">
1548 <description><![CDATA[For <img> output only!
1549
1550 If no alttext is specified, it will use an empty alttext]]></description>
1551 <default><![CDATA[
1552 ]]></default>
1553 </property>
1554 <property name="emptyTitleHandling" type="string">
1555 <description><![CDATA[Value can be "keepEmpty" to preserve an empty title attribute, or "useAlt" to use the alt attribute instead.
1556 ]]></description>
1557 <default><![CDATA[useAlt
1558 ]]></default>
1559 </property>
1560 <property name="file" type="stdWrap">
1561 <description><![CDATA[resource/stdWrap
1562 If the resource is jpg,gif,jpeg,png the image is inserted as an image-tag. Al other formats is read and inserted into the HTML-code.
1563 The maximum filesize of documents to be read is set to 1024 kb internally!]]></description>
1564 <default><![CDATA[
1565 ]]></default>
1566 </property>
1567 <property name="linkWrap" type="stdWrap">
1568 <description><![CDATA[wrap/stdWrap
1569 (before ".wrap")]]></description>
1570 <default><![CDATA[
1571 ]]></default>
1572 </property>
1573 <property name="longdescURL" type="stdWrap">
1574 <description><![CDATA[For <img> output only!
1575
1576 "longdesc" attribute (URL pointing to document with extensive details about image).]]></description>
1577 <default><![CDATA[
1578 ]]></default>
1579 </property>
1580 <property name="stdWrap" type="stdWrap">
1581 <description><![CDATA[
1582 ]]></description>
1583 <default><![CDATA[
1584 ]]></default>
1585 </property>
1586 <property name="wrap" type="stdWrap">
1587 <description><![CDATA[wrap/stdWrap
1588 ]]></description>
1589 <default><![CDATA[
1590 ]]></default>
1591 </property>
1592 </type>
1593 <type id="FORM_dataArray">
1594 <property name="10" type="FORM_dataArray_element">
1595 <description><![CDATA[alternative way to define form Elements]]></description>
1596 <default><![CDATA[]]></default>
1597 </property>
1598 <property name="20" type="FORM_dataArray_element">
1599 <description><![CDATA[alternative way to define form Elements]]></description>
1600 <default><![CDATA[]]></default>
1601 </property>
1602 <property name="30" type="FORM_dataArray_element">
1603 <description><![CDATA[alternative way to define form Elements]]></description>
1604 <default><![CDATA[]]></default>
1605 </property>
1606 <property name="40" type="FORM_dataArray_element">
1607 <description><![CDATA[alternative way to define form Elements]]></description>
1608 <default><![CDATA[]]></default>
1609 </property>
1610 </type>
1611 <type id="FORM_dataArray_element">
1612 <property name="label" type="string">
1613 <description><![CDATA[]]></description>
1614 <default><![CDATA[]]></default>
1615 </property>
1616 <property name="type" type="string">
1617 <description><![CDATA[]]></description>
1618 <default><![CDATA[]]></default>
1619 </property>
1620 <property name="name" type="string">
1621 <description><![CDATA[]]></description>
1622 <default><![CDATA[]]></default>
1623 </property>
1624 <property name="value" type="string">
1625 <description><![CDATA[]]></description>
1626 <default><![CDATA[]]></default>
1627 </property>
1628 <property name="required" type="boolean">
1629 <description><![CDATA[]]></description>
1630 <default><![CDATA[]]></default>
1631 </property>
1632 </type>
1633 <type id="FORM">
1634 <property name="CHECK.layout" type="string">
1635 <description><![CDATA[Alternative layout for checkboxes]]></description>
1636 <default><![CDATA[the "layout"-property]]></default>
1637 </property>
1638 <property name="COMMENT.layout" type="string">
1639 <description><![CDATA[Alternative layout for comments.]]></description>
1640 <default><![CDATA[the "layout"-property]]></default>
1641 </property>
1642 <property name="LABEL.layout" type="string">
1643 <description><![CDATA[Alternative layout for label types]]></description>
1644 <default><![CDATA[the "layout"-property]]></default>
1645 </property>
1646 <property name="RADIO.layout" type="string">
1647 <description><![CDATA[Alternative layout for radiobuttons]]></description>
1648 <default><![CDATA[the "layout"-property]]></default>
1649 </property>
1650 <property name="REQ" type="REQ">
1651 <description><![CDATA[boolean
1652 Defines if required-fields should be checked and marked up]]></description>
1653 <default><![CDATA[
1654 ]]></default>
1655 </property>
1656 <property name="accessibility" type="boolean">
1657 <description><![CDATA[If set, then the form will be compliant with accessibility guidelines (XHTML compliant). This includes:
1658
1659 label string will be wrapped in <label for="formname[fieldname-hash]"> ... </label>All form elements will have an id-attribute carrying the formname with the md5-hashed fieldname appended
1660
1661 Notice: In TYPO3 4.0 and later, CSS Styled Content is configured to produce accessible forms by default.]]></description>
1662 <default><![CDATA[
1663 ]]></default>
1664 </property>
1665 <property name="arrayReturnMode" type="boolean">
1666 <description><![CDATA[If set, the <form> tags and the form content will be returned in an array as separate elements including other pratical values. This mode is for use in extensions where the array return value can be more useful.]]></description>
1667 <default><![CDATA[
1668 ]]></default>
1669 </property>
1670 <property name="badMess" type="string">
1671 <description><![CDATA[Prefixed Message for the formevaluation in case of missing required fields.
1672 This message is shown above the list of fields.
1673
1674 NOTE: May be overridden by the property override feature of the formdata (see above)]]></description>
1675 <default><![CDATA[No message]]></default>
1676 </property>
1677 <property name="commentWrap" type="stdWrap">
1678 <description><![CDATA[Comments: Wrap for comments IF you use ###COMMENT###]]></description>
1679 <default><![CDATA[
1680 ]]></default>
1681 </property>
1682 <property name="compensateFieldWidth" type="double">
1683 <description><![CDATA[Overriding option to the config-value of the same name. See "CONFIG" above.]]></description>
1684 <default><![CDATA[
1685 ]]></default>
1686 </property>
1687 <property name="data" type="stdWrap">
1688 <description><![CDATA[This is the data that sets up the form. See above.
1689 "||" can be used instead of linebreaks]]></description>
1690 <default><![CDATA[
1691 ]]></default>
1692 </property>
1693 <property name="dataArray" type="FORM_dataArray">
1694 <description><![CDATA[This is an alternative way to define the form-fields. Instead of using the syntax with vertical separator bars suggested by the .data property, you can define the elements in regular TypoScript style arrays.
1695 .dataArray is added to the input in .data if any.
1696 Every entry in the dataArray is numeric and has three main properties, label, type, value and required. 'label' and 'value' has stdWrap properties.
1697 There is an alternative property to .value, which is .valueArray. This is also an array in the same style with numeric entries which has properties label, value and selected. 'label' has stdWrap properties.
1698
1699 Example:
1700   dataArray {
1701     10.label = Name:
1702     10.type = name=input
1703     10.value = [Enter name]
1704     10.required = 1
1705     20.label = Eyecolor
1706     20.type = eyecolor=select
1707     20.valueArray {
1708       10.label = Blue
1709       10.value = 1
1710       20.label = Red
1711       20.value = 2
1712       20.selected = 1
1713     }
1714     40.type = submit=submit
1715     40.value = Submit
1716   }
1717
1718
1719 This is the same as this line in the .data property:
1720
1721 Name: | *name=input | [Enter name]
1722 Eyecolor: | eyecolor=select | Blue=1, *Red=2
1723 | submit=submit | Submit
1724
1725 Why do it this way?  Good question, but doing it this way has a tremendous advantage because labels are all separated from the codes. In addition it's much easier to pull out or insert new elements in the form.
1726 Inserting an email-field after the name field would be like this:
1727   dataArray {
1728     15.label = Email:
1729     15.type = input
1730     15.value = your@email.com
1731     15.specialEval = EMAIL
1732   }
1733
1734 Or translating the form to danish (setting config.language to 'dk'):
1735
1736   dataArray {
1737     10.label.lang.dk = Navn:
1738     10.value.lang.dk = [Indtast dit navn]
1739     20.label.lang.dk = Øjenfarve
1740     20.valueArray {
1741       10.label.lang.dk = Blå
1742       20.label.lang.dk = Rød
1743     }
1744     40.value.lang.dk = Send
1745   }
1746 ]]></description>
1747 <default><![CDATA[
1748 ]]></default>
1749 </property>
1750 <property name="dontMd5FieldNames" type="boolean">
1751 <description><![CDATA[The IDs generated for all elements in a form are md5 hashes from the fieldname. Setting this to true will disable this behaviour and use a cleaned fieldname, prefixed with the form name as the ID, instead.
1752 This can be useful to style specifically named fields with CSS.]]></description>
1753 <default><![CDATA[
1754 ]]></default>
1755 </property>
1756 <property name="emailMess" type="string">
1757 <description><![CDATA[Message if a field evaluated to be an email adresse did not validate.
1758
1759 NOTE: May be overridden by the property override feature of the formdata (see above)]]></description>
1760 <default><![CDATA[
1761 ]]></default>
1762 </property>
1763 <property name="fieldPrefix" type="string">
1764 <description><![CDATA[Alternative prefix for the name of the fields in this form. Otherwise, all fields are prefixed with the form name (either a unique hash or the name set in the "formName" property). If set to "0", there will be no prefix at all.]]></description>
1765 <default><![CDATA[
1766 ]]></default>
1767 </property>
1768 <property name="fieldWrap" type="stdWrap">
1769 <description><![CDATA[Field: Wraps the fields]]></description>
1770 <default><![CDATA[
1771 ]]></default>
1772 </property>
1773 <property name="formName" type="string">
1774 <description><![CDATA[An alternative name for this form. Default will be a unique (random) hash.
1775
1776 <form name="...">]]></description>
1777 <default><![CDATA[
1778 ]]></default>
1779 </property>
1780 <property name="goodMess" type="string">
1781 <description><![CDATA[Message for the formevaluation function in case of correctly filled form.
1782
1783 NOTE: May be overridden by the property override feature of the formdata (see above)]]></description>
1784 <default><![CDATA[No message]]></default>
1785 </property>
1786 <property name="hiddenFields" type="cObjArray">
1787 <description><![CDATA[Used to set hiddenFields from TS.
1788
1789 Example:
1790 hiddenFields.pid = TEXT
1791 hiddenFields.pid.value = 2
1792
1793 This makes a hidden-field with the name "pid" and value "2".]]></description>
1794 <default><![CDATA[
1795 ]]></default>
1796 </property>
1797 <property name="image" type="IMAGE">
1798 <description><![CDATA[If this is a valid image the submitbutton is rendered as this image!!
1799
1800 NOTE: CurrentValue is set to the caption-label before generating the image.]]></description>
1801 <default><![CDATA[
1802 ]]></default>
1803 </property>
1804 <property name="labelWrap" type="stdWrap">
1805 <description><![CDATA[Labels: Wraps the label]]></description>
1806 <default><![CDATA[
1807 ]]></default>
1808 </property>
1809 <property name="layout" type="string">
1810 <description><![CDATA[This defines how the label and the field are placed towards each other.
1811
1812 Example:
1813 This substitutes the "###FIELD###" with the field data and the "###LABEL###' with labeldata.
1814
1815 <tr><td>###FIELD###</td><td> ###LABEL###</td></tr>
1816
1817 You can also use the marker ###COMMENT### which is ALSO the label value inserted, but wrapped in .commentWrap stdWrap-properties (see below)]]></description>
1818 <default><![CDATA[
1819 ]]></default>
1820 </property>
1821 <property name="locationData" type="string">
1822 <description><![CDATA[boolean / string
1823 If this value is true, then a hidden-field called "locationData" is added to the form. This field wil be loaded with a value like this:
1824 [page id]:[current record table]:[current record id]
1825 For example, if a formfield is inserted on page with uid = "100", as a page-content item from the table "tt_content" with id "120", then the value would be "100:tt_content:120".
1826 The value is use by eg. the cObject SEARCHRESULT. If the value $GLOBALS["HTTP_POST_VARS"]["locationData"] is detected here, the search is done as if it was performed on this page! This is very usefull if you want a search functionality implemented on a page with the "stype" field set to "L1" which means that the search is carried out from the first level in the rootline.
1827 Suppose you want the search to submit to a dedicated searchpage where ever. This page will then know - because of locationData - that the search was submittet from another place on the website.
1828 If "locationData" is not only true but also set to "HTTP_POST_VARS" then the value will insert the content of $GLOBALS["HTTP_POST_VARS"]["locationData"] instead of the true location data of the page. This should be done with search-fields as this will carry the initial searching start point with.
1829 NOTE: May be overridden by the property override feature of the formdata (see above)]]></description>
1830 <default><![CDATA[
1831 ]]></default>
1832 </property>
1833 <property name="method" type="string">
1834 <description><![CDATA[form-method
1835
1836 Example:
1837 GET]]></description>
1838 <default><![CDATA[POST]]></default>
1839 </property>
1840 <property name="noValueInsert" type="boolean">
1841 <description><![CDATA[By default values that are submitted to the same page (and thereby same form, eg. at searchforms) are re-inserted in the form instead of any default-data that might be set up.
1842 This, however, applies ONLY if the "no_cache=1" is set! (a page being cached may not include user-specific defaults in the fields of course...)
1843 If you set this flag, "noValueInsert", the content will always be the default content.]]></description>
1844 <default><![CDATA[
1845 ]]></default>
1846 </property>
1847 <property name="noWrapAttr" type="boolean">
1848 <description><![CDATA[If this value is true then all wrap attributes of textarea elements are suppressed. This is needed for XHTML-compliancy.
1849
1850 The wrap attributes can also be disabled on a per-field basis by using the special keyword "disabled" as the value of the wrap attribute.]]></description>
1851 <default><![CDATA[
1852 ]]></default>
1853 </property>
1854 <property name="no_cache" type="string">
1855 <description><![CDATA[Default no_cache-option]]></description>
1856 <default><![CDATA[
1857 ]]></default>
1858 </property>
1859 <property name="params" type="string">
1860 <description><![CDATA[form-element tag parameters
1861 Extra parameters to form elements
1862
1863 Example:
1864 params = style="width:200px;"
1865 params.textarea = style="width:300px;"
1866 params.check =
1867
1868 This sets the default to 200 px width, but excludes check-boxes and sets textareas to 300.]]></description>
1869 <default><![CDATA[
1870 ]]></default>
1871 </property>
1872 <property name="radioWrap" type="stdWrap">
1873 <description><![CDATA[Wraps the labels for radiobuttons]]></description>
1874 <default><![CDATA[
1875 ]]></default>
1876 </property>
1877 <property name="radioWrap.accessibilityWrap" type="wrap">
1878 <description><![CDATA[Defines how radio buttons are wrapped when accessibility mode is turned on (see below “accessibility” property)
1879 default:
1880
1881 <fieldset###RADIO_FIELD_ID###><legend>###RADIO_GROUP_LABEL###</legend>|</fieldset>
1882 ]]></description>
1883 <default><![CDATA[<fieldset###RADIO_FIELD_ID###><legend>###RADIO_GROUP_LABEL###</legend>|</fieldset>
1884 ]]></default>
1885 </property>
1886 <property name="radioInputWrap" type="stdWrap">
1887 <description><![CDATA[Wraps the input element and label of a radio button.]]></description>
1888 <default><![CDATA[
1889 ]]></default>
1890 </property>
1891 <property name="recipient" type="stdWrap">
1892 <description><![CDATA[(list of) string /stdWrap
1893 Email recipient of the formmail content (generates the hiddenfield "recipient")]]></description>
1894 <default><![CDATA[No email]]></default>
1895 </property>
1896 <property name="redirect" type="stdWrap">
1897 <description><![CDATA[URL to redirect to (generates the hidden field "redirect")
1898
1899 Integer: this is regarded to be a page in TYPO3
1900 String: this is regarded to be a normal url
1901 Empty; the current page is chosen.
1902
1903 NOTE: If this value is set the target of this overriddes the target of the "type".]]></description>
1904 <default><![CDATA[
1905 ]]></default>
1906 </property>
1907 <property name="stdWrap" type="stdWrap">
1908 <description><![CDATA[Wraps the hole form (before formtags is added)]]></description>
1909 <default><![CDATA[
1910 ]]></default>
1911 </property>
1912 <property name="target" type="string">
1913 <description><![CDATA[target
1914 Default target of the form. ]]></description>
1915 <default><![CDATA[
1916 ]]></default>
1917 </property>
1918 <property name="type" type="int">
1919 <description><![CDATA[Type (action="" of the form):
1920
1921 Integer: this is regarded to be a page in TYPO3
1922 String: this is regarded to be a normal URL (eg. "formmail.php" or "fe_tce_db.php")
1923 Empty: the current page is chosen.
1924
1925 NOTE: If type is integer/empty the form will be submitted to a page in TYPO3 and if this page has a value for target/no_cache, then this will be used instead of the default target/no_cache below.
1926
1927 NOTE: If the redirect-value is set, the redirect-target overrides the target set by the action-url
1928
1929 NOTE: May be overridden by the property override feature of the formdata (see above)]]></description>
1930 <default><![CDATA[
1931 ]]></default>
1932 </property>
1933 <property name="wrapFieldName" type="wrap">
1934 <description><![CDATA[This wraps  the fieldnames before they are applied to the form-field tags.
1935
1936 Example:
1937 If value is tx_myextension[input][  |  ]  then the fieldname "email" would be wrapped to this value: tx_myextension[input][email]]]></description>
1938 <default><![CDATA[
1939 ]]></default>
1940 </property>
1941 </type>
1942 <type id="REQ">
1943 <property name="fieldWrap" type="stdWrap">
1944 <description><![CDATA[Field: Wraps the fields, but for reuired fields]]></description>
1945 <default><![CDATA[the "fieldWrap"-property]]></default>
1946 </property>
1947 <property name="labelWrap" type="stdWrap">
1948 <description><![CDATA[Labels: Wraps the label, but for reuired fields]]></description>
1949 <default><![CDATA[the "labelWrap"-property]]></default>
1950 </property>
1951 <property name="layout" type="string">
1952 <description><![CDATA[The same as "layout" above, but for reuired fields]]></description>
1953 <default><![CDATA[the "layout"-property]]></default>
1954 </property>
1955 </type>
1956 <type id="FRAMESET">
1957 <property name="1" type="FRAME">
1958 <description><![CDATA[Configuration of frames and nested framesets.]]></description>
1959 <default><![CDATA[
1960 ]]></default>
1961 </property>
1962 <property name="2" type="FRAME">
1963 <description><![CDATA[Configuration of frames and nested framesets.]]></description>
1964 <default><![CDATA[
1965 ]]></default>
1966 </property>
1967 <property name="3" type="FRAME">
1968 <description><![CDATA[Configuration of frames and nested framesets.]]></description>
1969 <default><![CDATA[
1970 ]]></default>
1971 </property>
1972 <property name="4" type="FRAME">
1973 <description><![CDATA[Configuration of frames and nested framesets.]]></description>
1974 <default><![CDATA[
1975 ]]></default>
1976 </property>
1977 <property name="cols" type="string">
1978 <description><![CDATA[<frameset>-data:cols
1979 Cols]]></description>
1980 <default><![CDATA[
1981 ]]></default>
1982 </property>
1983 <property name="params" type="string">
1984 <description><![CDATA[<frameset>-params
1985 Example:
1986 border="0" framespacing="0" frameborder="NO"]]></description>
1987 <default><![CDATA[
1988 ]]></default>
1989 </property>
1990 <property name="rows" type="string">
1991 <description><![CDATA[<frameset>-data:rows
1992 Rows]]></description>
1993 <default><![CDATA[
1994 ]]></default>
1995 </property>
1996 </type>
1997 <type id="FRAME">
1998 <property name="name" type="string">
1999 <description><![CDATA[<frame>-data:name
2000 Manually set name of frame
2001
2002 NOTE: Is set automatically and should not be overridden under normal conditions!]]></description>
2003 <default><![CDATA[value of ".obj"]]></default>
2004 </property>
2005 <property name="obj" type="string">
2006 <description><![CDATA[pointer to toplevel object-name
2007 toplevel object-name of a PAGE / FRAMESET
2008
2009 Example:
2010 "left", "page", "frameset"]]></description>
2011 <default><![CDATA[
2012 ]]></default>
2013 </property>
2014 <property name="options" type="string">
2015 <description><![CDATA[url-parameters
2016 Example:
2017 print=1&othervar=anotherthing
2018 would add '&print=1&othervar=anotherthing' to the ".src"-content (if not ".src" is set manually!!)]]></description>
2019 <default><![CDATA[
2020 ]]></default>
2021 </property>
2022 <property name="params" type="string">
2023 <description><![CDATA[<frame>-params
2024 Example:
2025 scrolling="AUTO" noresize frameborder="NO"]]></description>
2026 <default><![CDATA[
2027 ]]></default>
2028 </property>
2029 <property name="src" type="string">
2030 <description><![CDATA[<frame>-data:src
2031 Manually set the src of the frame
2032
2033 NOTE: Is set automatically and should not be overridden under normal conditions!]]></description>
2034 <default><![CDATA[could be index.php?$id&$type ]]></default>
2035 </property>
2036 </type>
2037 <type id="GifBuilderObj">
2038 <property name="if" type="if">
2039 <description><![CDATA[.if (->if) is a property of all gifbuilder-objects. If the property is present and NOT set, the object is NOT rendered! This corresponds to the functionallity of ".if" of the stdWrap-function.]]></description>
2040 </property>
2041 </type>
2042 <type id="GIFBUILDER">
2043 <property name="1" type="GifBuilderObj">
2044 <description><![CDATA[.if (->if) is a property of all gifbuilder-objects. If the property is present and NOT set, the object is NOT rendered! This corresponds to the functionallity of ".if" of the stdWrap-function.]]></description>
2045 <default><![CDATA[
2046 ]]></default>
2047 </property>
2048 <property name="2" type="GifBuilderObj">
2049 <description><![CDATA[.if (->if) is a property of all gifbuilder-objects. If the property is present and NOT set, the object is NOT rendered! This corresponds to the functionallity of ".if" of the stdWrap-function.]]></description>
2050 <default><![CDATA[
2051 ]]></default>
2052 </property>
2053 <property name="3" type="GifBuilderObj">
2054 <description><![CDATA[.if (->if) is a property of all gifbuilder-objects. If the property is present and NOT set, the object is NOT rendered! This corresponds to the functionallity of ".if" of the stdWrap-function.]]></description>
2055 <default><![CDATA[
2056 ]]></default>
2057 </property>
2058 <property name="4" type="GifBuilderObj">
2059 <description><![CDATA[.if (->if) is a property of all gifbuilder-objects. If the property is present and NOT set, the object is NOT rendered! This corresponds to the functionallity of ".if" of the stdWrap-function.]]></description>
2060 <default><![CDATA[
2061 ]]></default>
2062 </property>
2063 <property name="XY" type="string">
2064 <description><![CDATA[x,y +calc
2065 Size of the gif-file. ]]></description>
2066 <default><![CDATA[100,20]]></default>
2067 </property>
2068 <property name="backColor" type="string">
2069 <description><![CDATA[GraphicColor
2070 Background color for the gif]]></description>
2071 <default><![CDATA[white]]></default>
2072 </property>
2073 <property name="format" type="string">
2074 <description><![CDATA["gif" / "jpg"
2075 Output type.
2076 "jpg"/"jpeg" = jpg-image]]></description>
2077 <default><![CDATA[gif]]></default>
2078 </property>
2079 <property name="maxHeight" type="int">
2080 <description><![CDATA[pixels
2081 Maximal heigth of gif-file]]></description>
2082 <default><![CDATA[
2083 ]]></default>
2084 </property>
2085 <property name="maxWidth" type="int">
2086 <description><![CDATA[pixels
2087 Maximal width of gif-file]]></description>
2088 <default><![CDATA[
2089 ]]></default>
2090 </property>
2091 <property name="offset" type="string">
2092 <description><![CDATA[x,y +calc
2093 Offset all objects on the gif.]]></description>
2094 <default><![CDATA[0,0]]></default>
2095 </property>
2096 <property name="quality" type="int">
2097 <description><![CDATA[posint (10-100)
2098 JPG-quality (if ".format" = jpg/jpeg)]]></description>
2099 <default><![CDATA[
2100 ]]></default>
2101 </property>
2102 <property name="reduceColors" type="int">
2103 <description><![CDATA[posint (1-255)
2104 Reduce the number of colors (if gif-file)]]></description>
2105 <default><![CDATA[
2106 ]]></default>
2107 </property>
2108 <property name="transparentBackground" type="boolean">
2109 <description><![CDATA[Set this flag to render the background transparent. TYPO3 makes the color found at position 0,0 of the image (upper left corner) transparent.
2110 If you render text you should leave the niceText option OFF as the result with probably be more precise without the niceText antialiasing hack]]></description>
2111 <default><![CDATA[
2112 ]]></default>
2113 </property>
2114 <property name="transparentColor" type="stdWrap">
2115 <description><![CDATA[HTMLColor /stdWrap
2116 Specify a color that should be transparent
2117
2118 Example-values:
2119 #ffffcc
2120 red
2121 255,255,127
2122
2123 Option:
2124 transparentColor.closest = 1
2125 This will allow for the closest color to be matched instead. You may need this if you image is not garanteed "clean".
2126
2127 NOTE: You may experience that this doesn't work if you use reduceColors-option or render text with niceText-option.]]></description>
2128 <default><![CDATA[
2129 ]]></default>
2130 </property>
2131 <property name="workArea" type="string">
2132 <description><![CDATA[x,y,w,h + calc
2133 Define the workarea on the giffile. All the GifBuilderObj's will see this as the dimensions of the gif-file regarding alignment, overlaying of images an so on. Only will TEXT-objects exceeding the boundaries of the workarea print outside this area.]]></description>
2134 <default><![CDATA[
2135 ]]></default>
2136 </property>
2137 </type>
2138 <type id="ADJUST" extends="GifBuilderObj">
2139 <property name="value" type="string">
2140 <description><![CDATA[This lets you adjust the input-levels like in Photoshops "levels"-dialog. If you need to adjust gamma, look at the EFFECT-object.
2141 Example:
2142
2143 20 = ADJUST
2144 20.value = inputLevels = 13,230
2145
2146 properties:
2147
2148 inputLevels: low,high
2149 outputLevels: low, high
2150 autoLevels: -
2151 ]]></description>
2152 <default><![CDATA[
2153 ]]></default>
2154 </property>
2155 </type>
2156 <type id="BOX" extends="GifBuilderObj">
2157 <property name="align" type="string">
2158 <description><![CDATA[VHalign
2159 ]]></description>
2160 <default><![CDATA[
2161 ]]></default>
2162 </property>
2163 <property name="color" type="string">
2164 <description><![CDATA[GraphicColor
2165 fill-color]]></description>
2166 <default><![CDATA[black]]></default>
2167 </property>
2168 <property name="dimensions" type="string">
2169 <description><![CDATA[x,y,w,h +calc
2170 Dimensions of a filled box.
2171 x,y    is the offset.
2172 w,h    is the dimensions. Dimensions of 1 will result in 1-pixel wide lines!]]></description>
2173 <default><![CDATA[
2174 ]]></default>
2175 </property>
2176 <property name="opacity" type="int">
2177 <description><![CDATA[pos-int (1-100)
2178 Dimensions of a filled box.
2179 Opacity (i.e. inverse of transparency, e.g. 100% opacity = 0% transparency)]]></description>
2180 <default><![CDATA[100
2181 ]]></default>
2182 </property>
2183 </type>
2184 <type id="CROP" extends="GifBuilderObj">
2185 <property name="align" type="string">
2186 <description><![CDATA[VHalign
2187 ]]></description>
2188 <default><![CDATA[
2189 ]]></default>
2190 </property>
2191 <property name="backColor" type="string">
2192 <description><![CDATA[GraphicColor
2193 ]]></description>
2194 <default><![CDATA[The original backColor]]></default>
2195 </property>
2196 <property name="crop" type="string">
2197 <description><![CDATA[x,y,v,h + calc
2198 x,y is offset of the crop-frame,
2199 v,h  is the dimensions]]></description>
2200 <default><![CDATA[
2201 ]]></default>
2202 </property>
2203 </type>
2204 <type id="ELLIPSE" extends="GifBuilderObj">
2205 <property name="dimensions" type="string">
2206 <description><![CDATA[x,y,w,h +calc
2207 Dimensions of a filled ellipse.
2208 x,y is the offset.
2209 w,h is the dimensions. Dimensions of 1 will result in 1-pixel wide lines!
2210
2211 Example:
2212 file = GIFBUILDER
2213 file {
2214 XY = 200,200
2215 format = jpg
2216 quality = 100
2217 10 = ELLIPSE
2218 10.dimensions = 100,100,50,50
2219 10.color = red
2220
2221 ]]></description>
2222 <default><![CDATA[
2223 ]]></default>
2224 </property>
2225 <property name="color" type="string">
2226 <description><![CDATA[GraphicColor
2227 fill-color
2228
2229 Example:
2230 file = GIFBUILDER
2231 file {
2232 XY = 200,200
2233 format = jpg
2234 quality = 100
2235 10 = ELLIPSE
2236 10.dimensions = 100,100,50,50
2237 10.color = red
2238
2239 ]]></description>
2240 <default><![CDATA[
2241 ]]></default>
2242 </property>
2243 </type>
2244 <type id="EFFECT" extends="GifBuilderObj">
2245 <property name="value" type="string">
2246 <description><![CDATA[.value = [Varnavn] = [value] | [Varnavn] = [value]
2247
2248 Example:
2249 20 = EFFECT
2250 20.value = gamme=1.3 | flip | rotate=180
2251
2252
2253 gamma: 0.5 - 3.0
2254 blur: 1-99
2255 sharpen: 1-99
2256 solarize: 0-99
2257 swirl: 0-100
2258 wave: ampli , length
2259 charcoal: 0-100
2260 gray: -
2261 edge: 0-99
2262 emboss: -
2263 flip: - (Vertical flipping)
2264 flop: - (Horizontal flipping)
2265 rotate: 0-360 (Rotation)
2266 colors: 2-255
2267 shear: -90 - 90 (Horizontal shearing)
2268 invert: - (invert the colors)
2269 ]]></description>
2270 <default><![CDATA[
2271 ]]></default>
2272 </property>
2273 </type>
2274 <type id="EMBOSS" extends="GifBuilderObj">
2275 <property name="blur" type="int">
2276 <description><![CDATA[posint (1-99)
2277 Blurring of the shadow. Above 40 only values of 40,50,60,70,80,90 means something.]]></description>
2278 <default><![CDATA[
2279 ]]></default>
2280 </property>
2281 <property name="highColor" type="string">
2282 <description><![CDATA[GraphicColor
2283 Upper border-color]]></description>
2284 <default><![CDATA[
2285 ]]></default>
2286 </property>
2287 <property name="intensity" type="int">
2288 <description><![CDATA[posint(0-100)
2289 How "massive" the emboss is. This value can - if it has a high value combined with a blurred shadow - create a kind of soft-edged outline.]]></description>
2290 <default><![CDATA[
2291 ]]></default>
2292 </property>
2293 <property name="lowColor" type="string">
2294 <description><![CDATA[GraphicColor
2295 lower border-color]]></description>
2296 <default><![CDATA[
2297 ]]></default>
2298 </property>
2299 <property name="offset" type="string">
2300 <description><![CDATA[x,y
2301 Offset of the emboss]]></description>
2302 <default><![CDATA[
2303 ]]></default>
2304 </property>
2305 <property name="opacity" type="int">
2306 <description><![CDATA[posint (1-100)
2307 Opacity (transparency^-1)
2308 100% opacity = 0% transparency). Only active with a value for blur.]]></description>
2309 <default><![CDATA[
2310 ]]></default>
2311 </property>
2312 <property name="textObjNum" type="int">
2313 <description><![CDATA[pos-int
2314 Must point to the TEXT-object if these shadow-properties are not properties to a TEXT-object directly ("stand-alone-shadow"). Then the shadow needs to know which TEXT-object it should be a shadow of!
2315 If - on the other hand - the shadow is a property to a text-object, this property is not needed.]]></description>
2316 <default><![CDATA[
2317 ]]></default>
2318 </property>
2319 </type>
2320 <type id="GB_IMAGE" extends="GifBuilderObj">
2321 <property name="align" type="string">
2322 <description><![CDATA[VHalign
2323 ]]></description>
2324 <default><![CDATA[
2325 ]]></default>
2326 </property>
2327 <property name="file" type="imgResource">
2328 <description><![CDATA[The imagefile]]></description>
2329 <default><![CDATA[
2330 ]]></default>
2331 </property>
2332 <property name="mask" type="imgResource">
2333 <description><![CDATA[Optional mask-image for the imagefile.]]></description>
2334 <default><![CDATA[
2335 ]]></default>
2336 </property>
2337 <property name="offset" type="string">
2338 <description><![CDATA[x,y +calc
2339 Offset ]]></description>
2340 <default><![CDATA[0,0]]></default>
2341 </property>
2342 <property name="tile" type="string">
2343 <description><![CDATA[x,y
2344 tile x,y times.
2345 Maximum times is 20 each direction. If you need more, use a larger image.]]></description>
2346 <default><![CDATA[
2347 ]]></default>
2348 </property>
2349 </type>
2350 <type id="OUTLINE" extends="GifBuilderObj">
2351 <property name="color" type="string">
2352 <description><![CDATA[GraphicColor
2353 Outline color]]></description>
2354 <default><![CDATA[
2355 ]]></default>
2356 </property>
2357 <property name="textObjNum" type="int">
2358 <description><![CDATA[pos-int
2359 Must point to the TEXT-object if these shadow-properties are not properties to a TEXT-object directly ("stand-alone-shadow"). Then the shadow needs to know which TEXT-object it should be a shadow of!
2360 If - on the other hand - the shadow is a property to a text-object, this property is not needed.]]></description>
2361 <default><![CDATA[
2362 ]]></default>
2363 </property>
2364 <property name="thickness" type="string">
2365 <description><![CDATA[x,y
2366 Thickness in each direction, range 1-2]]></description>
2367 <default><![CDATA[
2368 ]]></default>
2369 </property>
2370 </type>
2371 <type id="SCALE" extends="GifBuilderObj">
2372 <property name="height" type="string">
2373 <description><![CDATA[pixels + calc
2374 ]]></description>
2375 <default><![CDATA[
2376 ]]></default>
2377 </property>
2378 <property name="params" type="string">
2379 <description><![CDATA[ImageMagickParams
2380 ]]></description>
2381 <default><![CDATA[
2382 ]]></default>
2383 </property>
2384 <property name="width" type="string">
2385 <description><![CDATA[pixels + calc
2386 ]]></description>
2387 <default><![CDATA[
2388 ]]></default>
2389 </property>
2390 </type>
2391 <type id="SHADOW" extends="GifBuilderObj">
2392 <property name="blur" type="int">
2393 <description><![CDATA[posint (1-99)
2394 Blurring of the shadow. Above 40 only values of 40,50,60,70,80,90 means something.
2395
2396 NOTE: Unfortunately the blurring capabilities of ImageMagick is not very mature in the version 4.2.9. This is addressed in the later version 5.2.0 where a gaussian blur-function is added. BUT as we do cannot use the latest ImageMagick development yet, this is not utilized so far.]]></description>
2397 <default><![CDATA[
2398 ]]></default>
2399 </property>
2400 <property name="color" type="string">
2401 <description><![CDATA[GraphicColor
2402 Shadow color]]></description>
2403 <default><![CDATA[
2404 ]]></default>
2405 </property>
2406 <property name="intensity" type="int">
2407 <description><![CDATA[posint(0-100)
2408 How "massive" the shadow is. This value can - if it has a high value combined with a blurred shadow - create a kind of soft-edged outline.]]></description>
2409 <default><![CDATA[
2410 ]]></default>
2411 </property>
2412 <property name="offset" type="string">
2413 <description><![CDATA[x,y
2414 Shadow offset]]></description>
2415 <default><![CDATA[
2416 ]]></default>
2417 </property>
2418 <property name="opacity" type="int">
2419 <description><![CDATA[posint (1-100)
2420 Opacity (transparency^-1)
2421 100% opacity = 0% transparency). Only active with a value for blur.]]></description>
2422 <default><![CDATA[
2423 ]]></default>
2424 </property>
2425 <property name="textObjNum" type="int">
2426 <description><![CDATA[pos-int
2427 Must point to the TEXT-object if these shadow-properties are not properties to a TEXT-object directly ("stand-alone-shadow"). Then the shadow needs to know which TEXT-object it should be a shadow of!
2428 If - on the other hand - the shadow is a property to a text-object, this property is not needed.]]></description>
2429 <default><![CDATA[
2430 ]]></default>
2431 </property>
2432 </type>
2433 <type id="GB_TEXT" extends="GifBuilderObj">
2434 <property name="align" type="string">
2435 <description><![CDATA[align
2436 Alignment of the text]]></description>
2437 <default><![CDATA[left]]></default>
2438 </property>
2439 <property name="angle" type="string">
2440 <description><![CDATA[degree
2441 Rotation degrees of the text.
2442
2443 NOTE: Angle is not available if spacing/wordSpacing is set.]]></description>
2444 <default><![CDATA[0
2445 Range: -90 til 90]]></default>
2446 </property>
2447 <property name="antiAlias" type="boolean">
2448 <description><![CDATA[FreeType antialiasing. Notice, the default mode is "on"!
2449
2450 Note: This option is not available if .niceText is enabled]]></description>
2451 <default><![CDATA[1]]></default>
2452 </property>
2453 <property name="breakWidth" type="int">
2454 <description><![CDATA[Defines the maximum width for an object, overlapping elements will force an automatic line break.
2455 ]]></description>
2456 <default><![CDATA[
2457 ]]></default>
2458 </property>
2459 <property name="breakSpace" type="float">
2460 <description><![CDATA[Defines a value that is multiplied by the line height of the current element.
2461 ]]></description>
2462 <default><![CDATA[1.0]]></default>
2463 </property>
2464 <property name="doNotStripHTML" type="boolean">
2465 <description><![CDATA[If set, HTML-tags in the string inserted are NOT removed. Any other way HTML-code is removed by default!]]></description>
2466 <default><![CDATA[0]]></default>
2467 </property>
2468 <property name="emboss" type="EMBOSS">
2469 <description><![CDATA[
2470 ]]></description>
2471 <default><![CDATA[
2472 ]]></default>
2473 </property>
2474 <property name="fontColor" type="stdWrap">
2475 <description><![CDATA[GraphicColor /stdWrap
2476 Font color]]></description>
2477 <default><![CDATA[black]]></default>
2478 </property>
2479 <property name="fontFile" type="string">
2480 <description><![CDATA[Font face (truetype font you can upload!!)]]></description>
2481 <default><![CDATA[Nimbus (Arial-clone)]]></default>
2482 </property>
2483 <property name="fontSize" type="int">
2484 <description><![CDATA[posint
2485 Font size]]></description>
2486 <default><![CDATA[12]]></default>
2487 </property>
2488 <property name="hide" type="boolean">
2489 <description><![CDATA[If this is true, the text is NOT printed.
2490 This feature may be used if you need a shadow-object to base a shadow on the text, but do not want the text to print.]]></description>
2491 <default><![CDATA[0]]></default>
2492 </property>
2493 <property name="hideButCreateMap" type="boolean">
2494 <description><![CDATA[If this option is set, the text will not be rendered. Shadows and emboss will, though, so don't apply these!! But this feature is also meant only to enable a text to generate the imageMap coordinates without rendering itself.]]></description>
2495 <default><![CDATA[
2496 ]]></default>
2497 </property>
2498 <property name="imgMap" type="IMGMAP">
2499 <description><![CDATA[
2500 ]]></description>
2501 <default><![CDATA[
2502 ]]></default>
2503 </property>
2504 <property name="iterations" type="int">
2505 <description><![CDATA[posint
2506 How many times the text should be "printed" onto it self. This will add the effect of bold text.
2507
2508 Note: This option is not available if .niceText is enabled]]></description>
2509 <default><![CDATA[1]]></default>
2510 </property>
2511 <property name="maxWidth" type="int">
2512 <description><![CDATA[pixels
2513 Sets the maximum width in pixels, the text must be. Reduces the fontSize if the text does not fit within this width.
2514
2515 Does not support setting alternative fontSizes in splitRendering options.
2516
2517 (By Rene Fritz <r.fritz@colorcube.de>)]]></description>
2518 <default><![CDATA[
2519 ]]></default>
2520 </property>
2521 <property name="niceText" type="boolean">
2522 <description><![CDATA[This is a very popular feature that helps to render small letters much nicer than the freetype library can normally do. But it also loads the system very much!
2523 The principle of this function is to create a black/white giffile in twice or more times the size of the actual gif-file and then print the text onto this is a scaled dimension. Afterwards ImageMagick (IM) scales down the mask and masks the font color down on the original gif-file through the temporary mask.
2524 The fact that the font  is  actually rendered in the double size and scaled down adds a more homogenous shape to the lettes. Some fonts are more critical than others though.  If you do not need the quality, then don't use the function.
2525
2526 Some properties:
2527 .before = IM-params before scale
2528 .after = IM-params after scale
2529 .sharpen = sharpen-value for the mask (after scaling), integer 0-99 (this enables you to make the text crisper if it's too blurred!)
2530 .scaleFactor = scaling-factor, int 2-5]]></description>
2531 <default><![CDATA[
2532 ]]></default>
2533 </property>
2534 <property name="offset" type="string">
2535 <description><![CDATA[x,y +calc
2536 Offset of the text]]></description>
2537 <default><![CDATA[0,0]]></default>
2538 </property>
2539 <property name="outline" type="OUTLINE">
2540 <description><![CDATA[
2541 ]]></description>
2542 <default><![CDATA[
2543 ]]></default>
2544 </property>
2545 <property name="shadow" type="SHADOW">
2546 <description><![CDATA[
2547 ]]></description>
2548 <default><![CDATA[
2549 ]]></default>
2550 </property>
2551 <property name="spacing" type="int">
2552 <description><![CDATA[posint
2553 Pixel-distance between letters. This may render ugly!]]></description>
2554 <default><![CDATA[0]]></default>
2555 </property>
2556 <property name="splitRendering.compX" type="string">
2557 <description><![CDATA[Split the rendering of a string into separate processes with individual configurations. By this method a certain range of characters can be rendered with another font face or size. This is very useful if you want to use separate fonts for strings where you have latin characters combined with eg. Japanese and there is a separate font file for each.
2558 You can also render keywords in another font/size/color.
2559
2560 Properties:
2561 splitRendering.compX = Additional pixelspace between parts, x direction
2562 splitRendering.compY = Additional pixelspace between parts, y direction
2563 splitRendering.[array] = keyword  [charRange, highlightWord]
2564 splitRendering.[array] {
2565   fontFile = Alternative font file for this rendering
2566   fontSize = Alternative font size for this rendering
2567   color = Alternative color for this rendering, works ONLY without "niceText"
2568   xSpaceBefore = x-Space before this part
2569   xSpaceAfter = x-Space after this part
2570   ySpaceBefore = y-Space before this part
2571   ySpaceAfter =  y-Space after this part
2572 }
2573
2574 Keyword: charRange
2575 splitRendering.[array].value = Commaseparated list of character ranges (eg. "100-200") given as Unicode character numbers. The list accepts optional starting and ending points, eg. " - 200" or " 200 -" and single values, eg. "65, 66, 67"
2576
2577 Keyword: highlightWord
2578 splitRendering.[array].value = Word to highlight, makes a case sensitive search for this.
2579
2580 Limitations:
2581 The pixelcompensation values are not corrected for scale factor used with niceText. Basically this means that when niceText is used, these values will have only the half effect.When word spacing is used the "highlightWord" mode doesn't work.The color override works only without "niceText".
2582
2583 Example:
2584   10.splitRendering.compX = 2
2585   10.splitRendering.compY = -2
2586   10.splitRendering.10 = charRange
2587   10.splitRendering.10 {
2588     value = 200-380 , 65, 66
2589     fontSize = 50
2590     fontFile =  t3lib/fonts/nimbus.ttf
2591     xSpaceBefore = 30
2592   }
2593   10.splitRendering.20 = highlightWord
2594   10.splitRendering.20 {
2595     value = TheWord
2596     color = red
2597   }]]></description>
2598 <default><![CDATA[
2599 ]]></default>
2600 </property>
2601 <property name="splitRendering.compY" type="string">
2602 <description><![CDATA[Split the rendering of a string into separate processes with individual configurations. By this method a certain range of characters can be rendered with another font face or size. This is very useful if you want to use separate fonts for strings where you have latin characters combined with eg. Japanese and there is a separate font file for each.
2603 You can also render keywords in another font/size/color.
2604
2605 Properties:
2606 splitRendering.compX = Additional pixelspace between parts, x direction
2607 splitRendering.compY = Additional pixelspace between parts, y direction
2608 splitRendering.[array] = keyword  [charRange, highlightWord]
2609 splitRendering.[array] {
2610   fontFile = Alternative font file for this rendering
2611   fontSize = Alternative font size for this rendering
2612   color = Alternative color for this rendering, works ONLY without "niceText"
2613   xSpaceBefore = x-Space before this part
2614   xSpaceAfter = x-Space after this part
2615   ySpaceBefore = y-Space before this part
2616   ySpaceAfter =  y-Space after this part
2617 }
2618
2619 Keyword: charRange
2620 splitRendering.[array].value = Commaseparated list of character ranges (eg. "100-200") given as Unicode character numbers. The list accepts optional starting and ending points, eg. " - 200" or " 200 -" and single values, eg. "65, 66, 67"
2621
2622 Keyword: highlightWord
2623 splitRendering.[array].value = Word to highlight, makes a case sensitive search for this.
2624
2625 Limitations:
2626 The pixelcompensation values are not corrected for scale factor used with niceText. Basically this means that when niceText is used, these values will have only the half effect.When word spacing is used the "highlightWord" mode doesn't work.The color override works only without "niceText".
2627
2628 Example:
2629   10.splitRendering.compX = 2
2630   10.splitRendering.compY = -2
2631   10.splitRendering.10 = charRange
2632   10.splitRendering.10 {
2633     value = 200-380 , 65, 66
2634     fontSize = 50
2635     fontFile =  t3lib/fonts/nimbus.ttf
2636     xSpaceBefore = 30
2637   }
2638   10.splitRendering.20 = highlightWord
2639   10.splitRendering.20 {
2640     value = TheWord
2641     color = red
2642   }]]></description>
2643 <default><![CDATA[
2644 ]]></default>
2645 </property>
2646 <property name="text" type="stdWrap">
2647 <description><![CDATA[This is text text-string on the gif-file. The item is rendered only if this string is not empty.
2648 The cObj->data-array is loaded with the page-record, if for example the GIFBUILDER-object is used by GMENU or IMGMENU]]></description>
2649 <default><![CDATA[
2650 ]]></default>
2651 </property>
2652 <property name="textMaxLength" type="int">
2653 <description><![CDATA[The maximum length of the text.  This is just a natural break that prevents incidental rendering of very long texts!]]></description>
2654 <default><![CDATA[100]]></default>
2655 </property>
2656 <property name="wordSpacing" type="int">
2657 <description><![CDATA[posint
2658 Pixel-distance between words.]]></description>
2659 <default><![CDATA[= ".spacing"*2]]></default>
2660 </property>
2661 </type>
2662 <type id="WORKAREA" extends="GifBuilderObj">
2663 <property name="clear" type="string">(isset)
2664 <description><![CDATA[
2665 ]]></description>
2666 <default><![CDATA[
2667 ]]></default>
2668 </property>
2669 <property name="set" type="string">
2670 <description><![CDATA[x,y,w,h + calc
2671 Sets another workarea
2672 ]]></description>
2673 <default><![CDATA[
2674 ]]></default>
2675 </property>
2676 </type>
2677 <type id="HMENU">
2678 <property name="1" type="mObj">
2679 <description><![CDATA[Required!
2680 Defines which menuObj that should render the menuitems on the various levels.
2681 1 is the first level, 2 is the second level, 3 is the third level, 4 is ....
2682
2683 Example:
2684 temp.sidemenu = HMENU
2685 temp.sidemenu.1 = GMENU  ]]></description>
2686 <default><![CDATA[ (no menu)]]></default>
2687 </property>
2688 <property name="2" type="mObj">
2689 <description><![CDATA[Defines which menuObj that should render the menuitems on the various levels.
2690 1 is the first level, 2 is the second level, 3 is the third level, 4 is ....
2691
2692 Example:
2693 temp.sidemenu = HMENU
2694 temp.sidemenu.1 = GMENU  ]]></description>
2695 <default><![CDATA[ (no menu)]]></default>
2696 </property>
2697 <property name="3" type="mObj">
2698 <description><![CDATA[Defines which menuObj that should render the menuitems on the various levels.
2699 1 is the first level, 2 is the second level, 3 is the third level, 4 is ....
2700
2701 Example:
2702 temp.sidemenu = HMENU
2703 temp.sidemenu.1 = GMENU  ]]></description>
2704 <default><![CDATA[ (no menu)]]></default>
2705 </property>
2706 <property name="4" type="mObj">
2707 <description><![CDATA[Defines which menuObj that should render the menuitems on the various levels.
2708 1 is the first level, 2 is the second level, 3 is the third level, 4 is ....
2709
2710 Example:
2711 temp.sidemenu = HMENU
2712 temp.sidemenu.1 = GMENU  ]]></description>
2713 <default><![CDATA[ (no menu)]]></default>
2714 </property>
2715 <property name="addQueryString" type="string">
2716 <description><![CDATA[see typolink.addQueryString
2717
2718 Notice: This works only for special=language.]]></description>
2719 <default><![CDATA[
2720 ]]></default>
2721 </property>
2722 <property name="alwaysActivePIDlist" type="stdWrap">
2723 <description><![CDATA[List of Integers /stdWrap
2724 This is a list of page UID numbers that will always be regarded as active menu items and thereby automatically opened regardless of the rootline.]]></description>
2725 <default><![CDATA[
2726 ]]></default>
2727 </property>
2728 <property name="begin" type="int">
2729 <description><![CDATA[int +calc
2730 The first item in the menu.
2731
2732 Example:
2733 This results in a menu, where the first two items are skipped starting with item number 3:
2734   begin = 3  
2735
2736 Notice: Affects all sub menus as well. (See "minItems" for notice)]]></description>
2737 <default><![CDATA[
2738 ]]></default>
2739 </property>
2740 <property name="entryLevel" type="int">
2741 <description><![CDATA[Defines at which level in the rootLine, the menu should start.
2742 Default is "0" which gives us a menu of the very first pages on the site.
2743 If the value is < 0, entryLevel is chosen from "behind" in the rootLine. Thus "-1" is a menu with items from the outermost level, "-2" is the level before the outermost...]]></description>
2744 <default><![CDATA[0]]></default>
2745 </property>
2746 <property name="excludeDoktypes" type="intList">
2747 <description><![CDATA[list of integers
2748 Enter the list of page document types (doktype) to exclude from menus. By default pages that are "not in menu" (5) are excluded and those marked for backend user access only (6). ]]></description>
2749 <default><![CDATA[5,6]]></default>
2750 </property>
2751 <property name="excludeUidList" type="int">
2752 <description><![CDATA[list of integers
2753 This is a list of page uid's to exclude when the select statement is done. Comma-separated. You may add "current" to the list to exclude the current page.
2754
2755 Example:
2756 The pages with these uid-number will NOT be within the menu!! Additionally the current page is always excluded too.
2757   excludeUidList = 34,2,current]]></description>
2758 <default><![CDATA[
2759 ]]></default>
2760 </property>
2761 <property name="if" type="if">
2762 <description><![CDATA[If "if" returns false, the menu is not generated]]></description>
2763 <default><![CDATA[
2764 ]]></default>
2765 </property>
2766 <property name="includeNotInMenu" type="boolean">
2767 <description><![CDATA[If set, pages with type "Not in menu" will be included in menus.
2768 The number "5" will simply be removed from the current dok-type list (which is by default "5,6" but can be changed by "excludeDoktypes", see above).]]></description>
2769 <default><![CDATA[
2770 ]]></default>
2771 </property>
2772 <property name="maxItems" type="int">
2773 <description><![CDATA[The maximum items in the menu. More items will be ignored.
2774
2775 Notice: Affects all sub menus as well. (See "minItems" for notice)]]></description>
2776 <default><![CDATA[
2777 ]]></default>
2778 </property>
2779 <property name="minItems" type="int">
2780 <description><![CDATA[The minimum items in the menu. If the number of pages does not reach this level, a dummy-page with the title "..." and uid=[currentpage_id] is inserted.
2781
2782 Notice: Affects all sub menus as well. To set the value for each menu level individually, set the properties in the menu objects (see "Common properties" table).]]></description>
2783 <default><![CDATA[
2784 ]]></default>
2785 </property>
2786 <property name="protectLvar" type="string">
2787 <description><![CDATA[boolean / keyword
2788 If set, then for each page in the menu it will be checked if an Alternative Page Language record for the language defined in "config.sys_language_uid" (typically defined via &L) exists for the page. If that is not the case and the pages "Localization settings" have the "Hide page if no translation for current language exists" flag set, then the menu item will link to a non accessible page that will yield an error page to the user. Setting this option will prevent that situation by simply adding "&L=0" for such pages, meaning that they will switch to the default language rather than keeping the current language.
2789 The check is only carried out if a translation is requested ("config.sys_language_uid" is not zero).
2790
2791 Keyword: "all"
2792 When set to "all" the same check is carried out but it will not look if "Hide page if no translation for current language exists" is set - it always reverts to default language if no translation is found.
2793
2794 For these options to make sense, they should only be used when "config.sys_language_mode" is not set to "content_fallback".]]></description>
2795 <default><![CDATA[
2796 ]]></default>
2797 </property>
2798 <property name="special" type="HMENU_SPECIAL">
2799 <description><![CDATA["directory" / "list" / "updated" / "browse" / "rootline" / "keywords" / "language"
2800 (See tsref for details:
2801 <a href="http://typo3.org/documentation/document-library/references/doc_core_tsref/4.1.0/view/8/11/#id4080403">
2802 http://typo3.org/documentation/document-library/references/doc_core_tsref/4.1.0/view/8/11/#id4080403</a> )]]></description>
2803 <default><![CDATA[
2804 ]]></default>
2805 </property>
2806 <property name="stdWrap" type="stdWrap">
2807 <description><![CDATA[
2808 ]]></description>
2809 <default><![CDATA[
2810 ]]></default>
2811 </property>
2812 <property name="wrap" type="stdWrap">
2813 <description>wrap/stdWrap<![CDATA[
2814 ]]></description>
2815 <default><![CDATA[
2816 ]]></default>
2817 </property>
2818 </type>
2819 <type id="HMENU_SPECIAL">
2820 <property name="value" type="stdWrap">
2821 <description><![CDATA[list of page-uid's /stdWrap]]></description>
2822 <default><![CDATA[
2823 ]]></default>
2824 </property>
2825 </type>
2826 <type id="directory" extends="HMENU_SPECIAL"/>
2827 <type id="list" extends="HMENU_SPECIAL"/>
2828 <type id="updated" extends="HMENU_SPECIAL">
2829 <property name="mode" type="string">
2830 <description><![CDATA[Which field in the pages-table to use. Default is "SYS_LASTCHANGED" (which is updated when a page is generated to the youngest tstamp of the records on the page), "manual" or "lastUpdated" will use the field "lastUpdated" (set manually in the page-record) and "tstamp" will use the "tstamp"-field of the pagerecord, which is set automatically when the record is changed. "crdate" will use "crdate"-field of the pagerecord. "starttime" will use the starttime field.
2831
2832 Fields with zero value is not selected anyway.]]></description>
2833 <default><![CDATA[
2834 ]]></default>
2835 </property>
2836 <property name="depth" type="string">
2837 <description><![CDATA[By default (if the value is not an integer) the depth is 20 levels. The range is 1-20. A depth of 1 means only the start id, depth of 2 means start-id + first level. NOTE: depth is relative to beginAtLevel.
2838 ]]></description>
2839 <default><![CDATA[
2840 ]]></default>
2841 </property>
2842 <property name="beginAtLevel" type="int">
2843 <description><![CDATA[Determines starting level for the pagetrees generated based on .value and .depth. Zero is default and includes the start id. 1=starts with the first row of subpages, 2=starts with the second row of subpages. Depth is relative to this starting point.
2844 ]]></description>
2845 <default><![CDATA[
2846 ]]></default>
2847 </property>
2848 <property name="maxAge" type="string">
2849 <description><![CDATA[Seconds+calc.
2850 Pages with update-dates older than currenttime minus this number of seconds will not be shown in the menu no matter what. Default is "not used". You may use +-*/ for calculations.
2851 ]]></description>
2852 <default><![CDATA[
2853 ]]></default>
2854 </property>
2855 <property name="limit" type="int">
2856 <description><![CDATA[Max number of items in the menu. Default is 10, max is 100.
2857 ]]></description>
2858 <default><![CDATA[10
2859 ]]></default>
2860 </property>
2861 <property name="excludeNoSearchPages" type="boolean">
2862 <description><![CDATA[If set, pages marked "No search" is not included into special-menus.
2863 Support for Mount Pages: Yes.
2864 ]]></description>
2865 <default><![CDATA[
2866 ]]></default>
2867 </property>
2868 </type>
2869 <type id="rootline" extends="HMENU_SPECIAL">
2870 <property name="range" type="string">
2871 <description><![CDATA[rootline creates a menu with pages from the "rootline" (see earlier in this reference)
2872
2873 .range = [begin-level] | [end-level] (same way as you reference the .entryLevel for HMENU)
2874
2875 This...
2876
2877 page.2 = HMENU
2878 page.2.special = rootline
2879 page.2.special.range = 1|-2
2880 page.2.special.targets.3 = page
2881 page.2.1 = TMENU
2882 page.2.1.target = _top
2883 page.2.1.wrap = <HR> | <HR>
2884 page.2.1.NO {
2885 linkWrap = | >
2886 }
2887 ... creates a menu like this:
2888
2889 Page level 1 > Page level 2 > Page level 3 > Page level 4 >
2890
2891 (The menu starts at level 1 and does NOT link to the current page (-2 is the level before). Further all pages on level 3 will have "page" as target and all other "_top")
2892 ]]></description>
2893 <default><![CDATA[
2894 ]]></default>
2895 </property>
2896 <property name="reverseOrder" type="boolean">
2897 <description><![CDATA[If set to true, the order of the rootline menu elements will be reversed.
2898 ]]></description>
2899 <default><![CDATA[false]]></default>
2900 </property>
2901 <property name="targets" type="string">
2902 <description><![CDATA[.targets.[0-x] targets
2903
2904 This...
2905
2906 page.2 = HMENU
2907 page.2.special = rootline
2908 page.2.special.range = 1|-2
2909 page.2.special.targets.3 = page
2910 page.2.1 = TMENU
2911 page.2.1.target = _top
2912 page.2.1.wrap = <HR> | <HR>
2913 page.2.1.NO {
2914 linkWrap = | >
2915 }
2916
2917 ... creates a menu like this:
2918
2919 Page level 1 > Page level 2 > Page level 3 > Page level 4 >
2920
2921 (The menu starts at level 1 and does NOT link to the current page (-2 is the level before). Further all pages on level 3 will have "page" as target and all other "_top")
2922
2923 ]]></description>
2924 <default><![CDATA[
2925 ]]></default>
2926 </property>
2927 </type>
2928 <type id="browse" extends="HMENU_SPECIAL">
2929 <property name="items" type="string">
2930 <description><![CDATA[.items ( "|" separated list of "itemnames")
2931 This kind of menu is built of items given by a list from the property ".item". Each element in the list (sep. by "|") is either a reserved itemname (see list) with a predefined function or a userdefined name which you can assign a link to any page. Note that the current page cannot be the root-page of a site.
2932 ]]></description>
2933 <default><![CDATA[
2934 ]]></default>
2935 </property>
2936 <property name="items.prevnextToSection" type="boolean">
2937 <description><![CDATA[items.prevnextToSection (boolean) - if set, the "prev" and "next" navigation will jump to the next section when it reaches the end of pages in the current section.
2938 ]]></description>
2939 <default><![CDATA[
2940 ]]></default>
2941 </property>
2942 <property name="next" type="HMENU_SPECIAL_browseItem">
2943 <description><![CDATA[next / prev : links to next page / previous page. Next and previous pages are from the same "pid" as the current page id (or "value") - that is the next item in a menu with the current page. Also referred to as current level.
2944
2945 If ".prevnextToSection" is set then next/prev will link to the first page of next section / last page of previous section.
2946 ]]></description>
2947 <default><![CDATA[
2948 ]]></default>
2949 </property>
2950 <property name="prev" type="HMENU_SPECIAL_browseItem">
2951 <description><![CDATA[next / prev : links to next page / previous page. Next and previous pages are from the same "pid" as the current page id (or "value") - that is the next item in a menu with the current page. Also referred to as current level.
2952
2953 If ".prevnextToSection" is set then next/prev will link to the first page of next section / last page of previous section.
2954 ]]></description>
2955 <default><![CDATA[
2956 ]]></default>
2957 </property>
2958 <property name="nextsection" type="HMENU_SPECIAL_browseItem">
2959 <description><![CDATA[nextsection / prevsection : links to next section / previous section. A section is defined as the subpages of a page on the same level as the parent (pid) page of the current page. Will not work if parent page of current page is the root page of the site.
2960 ]]></description>
2961 <default><![CDATA[
2962 ]]></default>
2963 </property>
2964 <property name="prevsection" type="HMENU_SPECIAL_browseItem">
2965 <description><![CDATA[nextsection / prevsection : links to next section / previous section. A section is defined as the subpages of a page on the same level as the parent (pid) page of the current page. Will not work if parent page of current page is the root page of the site.
2966 ]]></description>
2967 <default><![CDATA[
2968 ]]></default>
2969 </property>
2970 <property name="nextsection_last" type="HMENU_SPECIAL_browseItem">
2971 <description><![CDATA[Where nextsection/prevsection links to the first page in a section, these links to the last pages. If there is only one page in the section that will be both first and last. Will not work if parent page of current page is the root page of the site.
2972 ]]></description>
2973 <default><![CDATA[
2974 ]]></default>
2975 </property>
2976 <property name="prevsection_last" type="HMENU_SPECIAL_browseItem">
2977 <description><![CDATA[Where nextsection/prevsection links to the first page in a section, these links to the last pages. If there is only one page in the section that will be both first and last. Will not work if parent page of current page is the root page of the site.
2978 ]]></description>
2979 <default><![CDATA[
2980 ]]></default>
2981 </property>
2982 <property name="first" type="HMENU_SPECIAL_browseItem">
2983 <description><![CDATA[First / Last page on current level. If there is only one page on the current level that page will be both first and last.
2984 ]]></description>
2985 <default><![CDATA[
2986 ]]></default>
2987 </property>
2988 <property name="last" type="HMENU_SPECIAL_browseItem">
2989 <description><![CDATA[First / Last page on current level. If there is only one page on the current level that page will be both first and last.
2990 ]]></description>
2991 <default><![CDATA[
2992 ]]></default>
2993 </property>
2994 <property name="up" type="HMENU_SPECIAL_browseItem">
2995 <description><![CDATA[Links to the parent (pid) page of the current page. (up 1 level) Will always be available
2996 ]]></description>
2997 <default><![CDATA[
2998 ]]></default>
2999 </property>
3000 <property name="index" type="HMENU_SPECIAL_browseItem">
3001 <description><![CDATA[Links to the parent of the parent page of the current page (up 2 levels). May not be available if that page is out of the rootline.
3002 ]]></description>
3003 <default><![CDATA[
3004 ]]></default>
3005 </property>
3006 </type>
3007 <type id="HMENU_SPECIAL_browseItem">
3008 <property name="target" type="string">
3009 <description><![CDATA[optional/alternative target of the item]]></description>
3010 <default><![CDATA[
3011 ]]></default>
3012 </property>
3013 <property name="uid" type="int">
3014 <description><![CDATA[. (uid of page) - optional/alternative page-uid to link to
3015 ]]></description>
3016 <default><![CDATA[
3017 ]]></default>
3018 </property>
3019 <property name="fields" type="string">
3020 <description><![CDATA[.[itemnames].fields.[fieldname] (string)
3021 override field "fieldname" in pagerecord.]]></description>
3022 <default><![CDATA[
3023 ]]></default>
3024 </property>
3025 </type>
3026 <type id="keywords" extends="HMENU_SPECIAL">
3027 <property name="mode" type="string">
3028 <description><![CDATA[Which field in the pages-table to use for sorting. Default is "SYS_LASTCHANGED" (which is updated when a page is generated to the youngest tstamp of the records on the page), "manual" or "lastUpdated" will use the field "lastUpdated" (set manually in the page-record) and "tstamp" will use the "tstamp"-field of the pagerecord, which is set automatically when the record is changed. "crdate" will use "crdate"-field of the pagerecord. "starttime" will use the starttime field.
3029 ]]></description>
3030 <default><![CDATA[
3031 ]]></default>
3032 </property>
3033 <property name="depth" type="string">
3034 <description><![CDATA[By default (if the value is not an integer) the depth is 20 levels. The range is 1-20. A depth of 1 means only the start id, depth of 2 means start-id + first level. NOTE: depth is relative to beginAtLevel.
3035 ]]></description>
3036 <default><![CDATA[
3037 ]]></default>
3038 </property>
3039 <property name="beginAtLevel" type="int">
3040 <description><![CDATA[Determines starting level for the pagetrees generated based on .value and .depth. Zero is default and includes the start id. 1=starts with the first row of subpages, 2=starts with the second row of subpages. Depth is relative to this starting point.
3041 ]]></description>
3042 <default><![CDATA[
3043 ]]></default>
3044 </property>
3045 <property name="limit" type="int">
3046 <description><![CDATA[Max number of items in the menu. Default is 10, max is 100.
3047 ]]></description>
3048 <default><![CDATA[10
3049 ]]></default>
3050 </property>
3051 <property name="excludeNoSearchPages" type="boolean">
3052 <description><![CDATA[If set, pages marked "No search" is not included into special-menus.
3053 Support for Mount Pages: Yes.
3054 ]]></description>
3055 <default><![CDATA[
3056 ]]></default>
3057 </property>
3058 <property name="entryLevel" type="string">
3059 <description><![CDATA[.entryLevel = where in the rootline the search begins. Standard rootline syntax (-x to x)]]></description>
3060 <default><![CDATA[
3061 ]]></default>
3062 </property>
3063 <property name="setKeywords" type="stdWrap">
3064 <description><![CDATA[.setKeywords (/stdWrap) = lets you define the keywords manually by defining them as a commaseparated list. If this property is defined, it overrides the default, which is the keywords of the current page.
3065 ]]></description>
3066 <default><![CDATA[
3067 ]]></default>
3068 </property>
3069 <property name="keywordsField" type="string">
3070 <description><![CDATA[.keywordsField = defines the field in the pages-table in which to search for the keywords. Default is the fieldname "keyword". No check is done to see if the field you enter here exists, so enter an existing field, OK?!]]></description>
3071 <default><![CDATA["keyword"
3072 ]]></default>
3073 </property>
3074 <property name="keywordsField.sourceField" type="string">
3075 <description><![CDATA[.keywordsField.sourceField = defines the field from the current page from which to take the keywords being matched. The default is "keyword". (Notice that ".keywordsField" is only setting the page-record field to search in !)]]></description>
3076 <default><![CDATA["keyword"
3077 ]]></default>
3078 </property>
3079 </type>
3080 <type id="language" extends="HMENU_SPECIAL"/>
3081 <type id="userdefined" extends="HMENU_SPECIAL">
3082 <property name="file" type="string">
3083 <description><![CDATA[.file [resource] = filename of the php-file to include. (Just like cObject PHP_SCRIPT)
3084 ]]></description>
3085 <default><![CDATA[
3086 ]]></default>
3087 </property>
3088 </type>
3089 <type id="userfunction" extends="HMENU_SPECIAL">
3090 <property name="userFunc" type="string">
3091 <description><![CDATA[.userFunc = function-name
3092 Calls a user function/method in class which should (as with "userdefined" above) return an array with page records for the menu.
3093 ]]></description>
3094 <default><![CDATA[
3095 ]]></default>
3096 </property>
3097 </type>
3098 <type id="mObj">
3099 <property name="alternativeSortingField" type="string">
3100 <description><![CDATA[Normally the menuitems are sorted by the fields "sorting" in the pages- and tt_content-table. Here you can enter a list of fields that is used in the SQL- "ORDER BY" statement instead.
3101
3102 Examples (for "pages" table):
3103 alternativeSortingField = title desc
3104 (This will render the menu in reversed alphabetical order)
3105
3106 LIMITATIONS:
3107 This property works with normal menus, sectionsIndex menus and special-menus of type "directory".]]></description>
3108 <default><![CDATA[
3109 ]]></default>
3110 </property>
3111 <property name="begin" type="int">
3112 <description><![CDATA[int +calc
3113 The first item in the menu.
3114
3115 Example:
3116 This results in a menu, where the first two items are skipped starting with item number 3:
3117   begin = 3  
3118
3119 Takes precedence over HMENU.begin]]></description>
3120 <default><![CDATA[
3121 ]]></default>
3122 </property>
3123 <property name="imgNameNotRandom" type="boolean">
3124 <description><![CDATA[If set, the image names of menuitems is not randomly assigned. Usefull switch if you're manipulating these images with some external JavaScript
3125
3126 NOTE: Don't set this if you're working with a menu with sectionIndex! In that case you need special unique names of items based on something else than the uid of the parent page of course!]]></description>
3127 <default><![CDATA[
3128 ]]></default>
3129 </property>
3130 <property name="imgNamePrefix" type="string">
3131 <description><![CDATA[prefix for the imagenames. This prefix is appended with the uid of the page.]]></description>
3132 <default><![CDATA["img"]]></default>
3133 </property>
3134 <property name="itemArrayProcFunc" type="string">
3135 <description><![CDATA[function-name
3136 The first variable passed to this function is the "menuArr" array with the menuitems as they are collected based on the type of menu.
3137 You're free to manipulate or add to this array as you like. Just remember to return the array again!
3138
3139 Note:
3140 .parentObj property is hardcoded to be a reference to the calling tslib_menu object. Here you'll find eg. ->id to be the uid of the menu item generating a submenu and such.
3141
3142 Presetting element state
3143 You can override element states like SPC, IFSUB, ACT, CUR or USR by setting the key ITEM_STATE in the page records. See cObject HMENU/special=userdefined for more information.]]></description>
3144 <default><![CDATA[
3145 ]]></default>
3146 </property>
3147 <property name="maxItems" type="int">
3148 <description><![CDATA[The maximum items in the menu. More items will be ignored.
3149
3150 Takes precedence over HMENU.maxItems]]></description>
3151 <default><![CDATA[
3152 ]]></default>
3153 </property>
3154 <property name="minItems" type="int">
3155 <description><![CDATA[The minimum items in the menu. If the number of pages does not reach this level, a dummy-page with the title "..." and uid=[currentpage_id] is inserted.
3156
3157 Takes precedence over HMENU.minItems]]></description>
3158 <default><![CDATA[
3159 ]]></default>
3160 </property>
3161 <property name="sectionIndex" type="string">
3162 <description><![CDATA[This is a property that all menuObj's share. If it's set, then the menu will not consist of links to pages on the "next level" but rather links to the parent page to the menu, but in addition "#"-links to the cObjects rendered on the page. In other words, the menuitems will be links to the content elements (with colPos=0!) on the page. A section index.
3163
3164 .sectionIndex = [boolean]
3165
3166 If you set this, all content elements (from tt_content table) of "Column" = "Normal" and the "Index"-check box clicked are selected. This corresponds to the "Menu/Sitemap" content element when "Section index" is selected as type.
3167
3168 .sectionIndex.type = "all" / "header"
3169
3170 If you set this additional property to "all", then the "Index"-checkbox is not considered and all content elements with colPos=0 is selected.
3171
3172 If this property is "header" then only content elements with a visible header-layout (and a non-empty 'header'-field!) is selected. In other words, if the header layout of an element is set to "Hidden" then the page will not appear in the menu.
3173
3174 The data-record /Behind the scene:
3175
3176 When the menu-records are selected it works like this: The parent page record is used as the "base" for the menu-record. That means that any "no_cache" or "target"-properties of the parent page is used for the whole menu.
3177
3178 But of course some fields from the tt_content records are transfered: This is how it mapped:
3179
3180 $temp[$row[uid]]=$basePageRow;
3181
3182 $temp[$row[uid]]["title"]=$row["header"];
3183
3184 $temp[$row[uid]]["subtitle"]=$row["subheader"];
3185
3186 $temp[$row[uid]]["starttime"]=$row["starttime"];
3187
3188 $temp[$row[uid]]["endtime"]=$row["endtime"];
3189
3190 $temp[$row[uid]]["fe_group"]=$row["fe_group"];
3191
3192 $temp[$row[uid]]["media"]=$row["media"];
3193
3194 $temp[$row[uid]]["header_layout"]=$row["header_layout"];
3195
3196 $temp[$row[uid]]["bodytext"]=$row["bodytext"];
3197
3198 $temp[$row[uid]]["image"]=$row["image"];
3199
3200 $temp[$row[uid]]["sectionIndex_uid"]=$row["uid"];
3201
3202 Basically this shows that
3203
3204 - the field "header" and "subheader" from tt_content are mapped to "title" and "subtitle" in the pages-record. Thus you shouldn't need to change your standard menu-objects to fit this thing...
3205
3206 - the fields "starttime", "endtime", "fe_group", "media" from tt_content are mapped to the same fields in a pages-record.
3207
3208 - the fields "header_layout", "bodytext" and "image" are mapped to non-existing fields in the page-record
3209
3210 - a new field, "sectionIndex_uid" is introduced in the page-record which is detected by the function t3lib_tstemplate->linkData(). If this field is present in a pagerecord, the linkData()-function will prepend a hash-mark and the number of the field.
3211
3212 NOTE:
3213
3214 You cannot create submenus to sectionIndex-menus. That doesn't make any sense as these elements are not pages and thereby have no "childs".
3215 ]]></description>
3216 <default><![CDATA[
3217 ]]></default>
3218 </property>
3219 <property name="showAccessRestrictedPages" type="string">
3220 <description><![CDATA[integer (page id) / keyword "NONE"
3221 If set, pages in the menu will include pages with frontend user group access enabled.  However the page is of course not accessible and therefore the URL in the menu will be linked to the page with the ID of this value. On that page you could put a login form or other message.
3222 If the value is "NONE" the link will not be changed and the site will perform page-not-found handling when clicked (which can be used to capture the event and act accordingly of course).
3223
3224 Properties:
3225 .addParam = Additional parameter for the URL, which can hold two markers; ###RETURN_URL### which will be substituted with the link the page would have had if it had been accessible and ###PAGE_ID### holding the page id of the page coming from (could be used to look up which fe_groups was required for access.
3226
3227 Example:
3228 showAccessRestrictedPages = 22
3229 showAccessRestrictedPages.addParams = &return_url=###RETURN_URL###&pageId=###PAGE_ID###
3230
3231 The example will link access restricted menu items to page id 22 with the return URL in the GET var "return_url" and the page id in the GET var "pageId".]]></description>
3232 <default><![CDATA[
3233 ]]></default>
3234 </property>
3235 <property name="submenuObjSuffixes" type="string">
3236 <description><![CDATA[Defines a suffix for alternative sub-level menu objects. Useful to create special submenus depending on their parent menu element. See example below.
3237
3238 Example:
3239 This example will generate a menu where the menu objects for the second level will differ depending on the number of the first level item for which the submenu is rendered. The second level objects used are "2" (the default), "2a" and "2b" (the alternatives). Which of them is used is defined by "1.submenuObjSuffixes" which has the configuration "a |*| |*| b". This configuration means that the first menu element will use configuration "2a" and the last will use "2b" while anything in between will use "2" (no suffix applied)
3240
3241 page.200 = HMENU
3242 page.200 {
3243   1 = TMENU
3244   1.wrap = <div style="width:200px; border: 1px solid;">|</div>
3245   1.expAll = 1
3246   1.submenuObjSuffixes = a |*|  |*| b
3247   1.NO.allWrap = <b>|</b><br/>
3248
3249   2 = TMENU
3250   2.NO.allWrap = <div style="background:red;">|</div>
3251
3252   2a = TMENU
3253   2a.NO.allWrap = <div style="background:yellow;">|</div>
3254
3255   2b = TMENU
3256   2b.NO.allWrap = <div style="background:green;">|</div>
3257 }
3258
3259 The result can be seen in the image below (applied on the testsite package):
3260
3261
3262
3263 Applies to GMENU, TMENU, GMENU_LAYERS, TMENU_LAYERS and GMENU_FOLDOUT on >= 2nd level in a menu.]]></description>
3264 <default><![CDATA[
3265 ]]></default>
3266 </property>
3267 </type>
3268 <type id="GMENU">
3269 <property name="ACT" type="GMENU_itemState">
3270 <description><![CDATA[Boolean / (config)
3271 Enable/Configuration for menu items which are found in the rootLine]]></description>
3272 <default><![CDATA[0]]></default>
3273 </property>
3274 <property name="ACTRO" type="GMENU_itemState">
3275 <description><![CDATA[Boolean / (config)
3276 Enable/Configuration for menu items which are found in the rootLine]]></description>
3277 <default><![CDATA[0]]></default>
3278 </property>
3279 <property name="ACTIFSUB" type="GMENU_itemState">
3280 <description><![CDATA[Boolean / (config)
3281 Enable/Configuration for menu items which are found in the rootLine and has subpages]]></description>
3282 <default><![CDATA[0]]></default>
3283 </property>
3284 <property name="ACTIFSUBRO" type="GMENU_itemState">
3285 <description><![CDATA[Boolean / (config)
3286 Enable/Configuration for menu items which are found in the rootLine and has subpages]]></description>
3287 <default><![CDATA[0]]></default>
3288 </property>
3289 <property name="CUR" type="GMENU_itemState">
3290 <description><![CDATA[Boolean / (config)
3291 Enable/Configuration for a menu item if the item is the current page.]]></description>
3292 <default><![CDATA[0]]></default>
3293 </property>
3294 <property name="CURRO" type="GMENU_itemState">
3295 <description><![CDATA[Boolean / (config)
3296 Enable/Configuration for a menu item if the item is the current page.]]></description>
3297 <default><![CDATA[0]]></default>
3298 </property>
3299 <property name="CURIFSUB" type="GMENU_itemState">
3300 <description><![CDATA[Boolean / (config)
3301 Enable/Configuration for a menu item if the item is the current page and has subpages.]]></description>
3302 <default><![CDATA[0]]></default>
3303 </property>
3304 <property name="CURIFSUBRO" type="GMENU_itemState">
3305 <description><![CDATA[Boolean / (config)
3306 Enable/Configuration for a menu item if the item is the current page and has subpages.]]></description>
3307 <default><![CDATA[0]]></default>
3308 </property>
3309 <property name="IFSUB" type="GMENU_itemState">
3310 <description><![CDATA[Boolean / (config)
3311 Enable/Configuration for menu items which has subpages]]></description>
3312 <default><![CDATA[0]]></default>
3313 </property>
3314 <property name="IFSUBRO" type="GMENU_itemState">
3315 <description><![CDATA[Boolean / (config)
3316 Enable/Configuration for menu items which has subpages]]></description>
3317 <default><![CDATA[0]]></default>
3318 </property>
3319 <property name="NO" type="GMENU_itemState">
3320 <description><![CDATA[Boolean / (config)
3321 The default "Normal" state rendering of Item. This is required for all menus.
3322 If you specify properties for the "NO" property you do not have to set it "1". Otherwise with no properties setting "NO=1" will render the menu anyways (for TMENU this may make sense).
3323
3324 The simplest menu TYPO3 can generate is then:
3325
3326 page.20 = HMENU
3327 page.20.1 = TMENU
3328 page.20.1.NO = 1
3329
3330 That will be pure <a> tags wrapped around page titles.]]></description>
3331 <default><![CDATA[1]]></default>
3332 </property>
3333 <property name="SPC" type="GMENU_itemState">
3334 <description><![CDATA[Boolean / (config)
3335 Enable/Configuration for 'Spacer' pages.
3336 Spacers are pages of the doktype "Spacer". These are not viewable pages but "placeholders" which can be used to divide menuitems.
3337
3338 Note: Rollovers doesn't work with spacers, if you use GMENU!]]></description>
3339 <default><![CDATA[0]]></default>
3340 </property>
3341 <property name="USERDEF1" type="GMENU_itemState">
3342 <description><![CDATA[Boolean / (config)
3343 Userdefined, see .itemArrayProcFunc for details on how to use this.
3344 You can set the ITEM_STATE values USERDEF1 and USERDEF2 (+...RO) from a script/userfunction processing the menu item array. See HMENU/special=userdefined or the property .itemArrayProcFunc of the menu objects.]]></description>
3345 <default><![CDATA[
3346 ]]></default>
3347 </property>
3348 <property name="USERDEF1RO" type="GMENU_itemState">
3349 <description><![CDATA[Boolean / (config)
3350 Userdefined, see .itemArrayProcFunc for details on how to use this.
3351 You can set the ITEM_STATE values USERDEF1 and USERDEF2 (+...RO) from a script/userfunction processing the menu item array. See HMENU/special=userdefined or the property .itemArrayProcFunc of the menu objects.]]></description>
3352 <default><![CDATA[
3353 ]]></default>
3354 </property>
3355 <property name="USERDEF2" type="GMENU_itemState">
3356 <description><![CDATA[Boolean / (config)
3357 (See above)]]></description>
3358 <default><![CDATA[
3359 ]]></default>
3360 </property>
3361 <property name="USERDEF2RO" type="GMENU_itemState">
3362 <description><![CDATA[Boolean / (config)
3363 (See above)]]></description>
3364 <default><![CDATA[
3365 ]]></default>
3366 </property>
3367 <property name="USR" type="GMENU_itemState">
3368 <description><![CDATA[Boolean / (config)
3369 Enable/Configuration for menu items which are access restricted pages that a user has access to.]]></description>
3370 <default><![CDATA[0]]></default>
3371 </property>
3372 <property name="USRRO" type="GMENU_itemState">
3373 <description><![CDATA[Boolean / (config)
3374 Enable/Configuration for menu items which are access restricted pages that a user has access to.]]></description>
3375 <default><![CDATA[0]]></default>
3376 </property>
3377 <property name="addParams" type="string">
3378 <description><![CDATA[Additional parameter for the menu-links.
3379 Example:
3380 "&some_var=some%20value"
3381 Must be rawurlencoded.
3382 Applies to GMENU, TMENU, IMGMENU]]></description>
3383 <default><![CDATA[
3384 ]]></default>
3385 </property>
3386 <property name="IProcFunc" type="string">
3387 <description><![CDATA[The internal array "I" is passed to this function and expected returned as well. Subsequent to this function call the menu item is compiled by implode()'ing the array $I[parts] in the passed array. Thus you may modify this if you need to.
3388 See example on the testsite and in media/scripts/example_itemArrayProcFunc.php]]></description>
3389 <default><![CDATA[
3390 ]]></default>
3391 </property>
3392 <property name="RO" type="boolean">
3393 <description><![CDATA[RollOver configuration enabled / disabled.
3394 If this is true, RO becomes a GIFBUILDER-object defining the layout of the menuitem when the mouse rolls over it]]></description>
3395 <default><![CDATA[0]]></default>
3396 </property>
3397 <property name="[Common Item States, see above]" type="GIFBUILDER">
3398 <description><![CDATA[This is the GIFBUILDER-options for each category of menuitem that can be generated.
3399
3400 NOTE: For the GMENU series you can also define the RollOver configuration for the item states. This means that you define the GIFBUILDER object for the 'Active' state by ACT and the RollOver GIFBUILDER object for the 'Active' state by ACTRO.
3401 This pattern goes for ALL the states except the SPC state.
3402
3403 SPECIAL:
3404 The ->OptionSplit function is run on the whole GIFBUILDER-configuration before the items are generated.]]></description>
3405 <default><![CDATA[
3406 ]]></default>
3407 </property>
3408 <property name="accessKey" type="boolean">
3409 <description><![CDATA[If set access-keys are set on the menu-links]]></description>
3410 <default><![CDATA[
3411 ]]></default>
3412 </property>
3413 <property name="applyTotalH" type="string">
3414 <description><![CDATA[objNumsList (offset)
3415
3416 This adds the total height of the previously generated menuitems to the offset of the GifBuilderObj's mentioned in this list.
3417
3418 Example:
3419 This is useful it you want to create a menu with individual items but a common background image that extends to the whole area behind the menu. Then you should setup the background image in each GIFBUILDER-object and include the object-number in this list.
3420 Look at the implementation in static_template "styles.gmenu.bug"]]></description>
3421 <default><![CDATA[
3422 ]]></default>
3423 </property>
3424 <property name="applyTotalW" type="string">
3425 <description><![CDATA[objNumsList (offset)
3426 This adds the total width of the previously generated menuitems to the offset of the GifBuilderObj's mentioned in this list.]]></description>
3427 <default><![CDATA[
3428 ]]></default>
3429 </property>
3430 <property name="collapse" type="boolean">
3431 <description><![CDATA[If set, "active" menuitems that has expanded the next level on the menu will now collapse that menu again.]]></description>
3432 <default><![CDATA[
3433 ]]></default>
3434 </property>
3435 <property name="debugItemConf" type="string">
3436 <description><![CDATA[Outputs (by the debug()-function) the configuration arrays for each menuitem. Useful to debug optionSplit things and such...
3437 Applies to GMENU, TMENU, IMGMENU]]></description>
3438 <default><![CDATA[