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