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