ext_tables_static+adt.sql

Typo3, 开源里边最强大的

  appdata blob NOT NULL,
  title tinytext NOT NULL,
  PRIMARY KEY (uid),
  KEY guide (guide,md5hash)
);



#
# ==== Data extracted from CoreDocs/doc_core_api_4.0.0.t3x
#
INSERT INTO static_tsconfig_help VALUES ('1', '', '004ad0c011cac5a5fcbc294774cb0281', '', 'page:RTE', 'a:1:{s:4:"rows";a:2:{i:0;a:6:{s:8:"property";s:133:"default.[...]<br>config.[<i>tablename</i>].[<i>field</i>].[...]<br>config.[<i>tablename</i>].[<i>field</i>].types.[<i>type</i>].[...]";s:8:"datatype";s:12:"-&gt;RTEconf";s:11:"description";s:610:"&nbsp; This is a description of how you can customize in general and override for specific fields/types.<br>&nbsp;<br>&#039;RTE.default&#039; configures the RTE for all tables/fields/types<br>&nbsp;<br>&#039;RTE.config.[<i>tablename</i>].[<i>field</i>]&#039; configures a specific field. The values inherit the values from &#039;RTE.default&#039; in fact this is overriding values.<br>&nbsp;<br>&#039;RTE.config.[<i>tablename</i>].[<i>field</i>].types.[<i>type</i>]&#039; configures a specific field in case the &#039;type&#039;-value of the field matches <i>type</i>. Again this overrides the former settings.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:1;a:6:{s:8:"property";s:24:"[individual RTE options]";s:8:"datatype";s:1:"-";s:11:"description";s:469:"There are other options to set for the RTE toplevel object. These depends on the individual RTEs though! So there can be no further reference in this table to these properties.<br>Generally the &quot;rte&quot; (classic MSIE RTE) will set the standard for configuration options, so you can refer to the documentation for that RTE for more details. On the top level of the RTE object you will normally find that general collections of classes, styles etc. are configured.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}}}', '');
INSERT INTO static_tsconfig_help VALUES ('2', '', 'ccb0322c7d1f7b0e49e1c8b981aacd1e', '', 'page:->RTEconf', 'a:1:{s:4:"rows";a:3:{i:0;a:6:{s:8:"property";s:8:"disabled";s:8:"datatype";s:7:"boolean";s:11:"description";s:128:"If set, the editor is disabled.<br>This option is evaluated in t3lib_TCEforms where it determines if the RTE is rendered or not.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:1;a:6:{s:8:"property";s:4:"proc";s:8:"datatype";s:9:"-&gt;PROC";s:11:"description";s:442:"Customization of the server processing of the content - also called &#039;transformations&#039;. See table below.<br>The transformations are only initialized, if they are configured (&quot;rte_transform&quot; must be set for the field in the types-definition in TCA.)<br>The &quot;-&gt;PROC&quot; object is processed in &quot;t3lib_parsehtml_proc&quot; and is <i>independant</i> of the particular RTE used (like transformations generally is!)";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:2;a:6:{s:8:"property";s:24:"[individual RTE options]";s:8:"datatype";s:1:"-";s:11:"description";s:200:"Each RTE may use additional properties for the RTE. Typically such properties relates to the features of the RTE application. For instance you could configure which tool bar buttons are available etc.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}}}', '');
INSERT INTO static_tsconfig_help VALUES ('3', '', '11acbecfba402c242e0ad130ba3140d1', '', 'page:->PROC', 'a:1:{s:4:"rows";a:28:{i:0;a:6:{s:8:"property";s:12:"overruleMode";s:8:"datatype";s:28:"List of RTE transformations ";s:11:"description";s:171:"This can overrule the RTE transformation set from TCA.<br>&nbsp;<br>Notice, this is a <i>comma list</i> of transformation keys. (Not a &quot;dash-list&quot; like in $TCA).";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:1;a:6:{s:8:"property";s:8:"typolist";s:8:"datatype";s:7:"boolean";s:11:"description";s:290:"<i>(Applies for &quot;ts_transform&quot; only)</i><br>&nbsp;<br>This enables/disables the conversion between &lt;TYPOLIST&gt; and &lt;UL&gt; sections. Default (if unset) is that &quot;typolist&quot; is enabled.<br>&nbsp;<b><br>Example that disables &quot;typolist&quot;:</b><br>typolist = 0";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:2;a:6:{s:8:"property";s:8:"typohead";s:8:"datatype";s:7:"boolean";s:11:"description";s:230:"<i>(Applies for &quot;ts_transform&quot; only)</i><br>&nbsp;<br>This enables/disables the conversion between &lt;TYPOHEAD&gt; and &lt;Hx&gt; sections.<br>&nbsp;<b><br>Example that disables &quot;typohead&quot;:</b><br>typohead = 0";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:3;a:6:{s:8:"property";s:13:"preserveTags ";s:8:"datatype";s:12:"list of tags";s:11:"description";s:843:"(DEPRECATED)<br>&nbsp;<br>Here you may specify a list of tags - possibly user-defined pseudo tags - which you wish to preserve from being removed by the RTE. See the information about preservation in the description of transformations.<br>&nbsp;<b><br>Example:</b><br>In the default TypoScript configuration of content rendering the tags typotags &lt;LINK&gt;, &lt;TYPOLIST&gt; and &lt;TYPOHEAD&gt; are the most widely used. However the &lt;TYPOCODE&gt;-tag is also configured to let you define a section being formatted in monospace. Lets also imaging, you have defined a custom tag, &lt;MYTAG&gt;. In order to preserve these tag from removal by the RTE, you should configure like this.<br>&nbsp;<br>RTE.default.proc {<br>&nbsp;&nbsp;&nbsp;preserveTags = TYPOCODE, MYTAG<br>}<br>&nbsp;<br>Relates to the transformation &#039;ts_preserve&#039;";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:4;a:6:{s:8:"property";s:21:"dontConvBRtoParagraph";s:8:"datatype";s:7:"boolean";s:11:"description";s:293:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>&nbsp;By default &lt;BR&gt; tags in the content are converted to paragraphs. Setting this value will <i>prevent</i> the convertion of &lt;BR&gt;-tags to new-lines (chr(10))";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:5;a:6:{s:8:"property";s:19:"internalizeFontTags";s:8:"datatype";s:7:"boolean";s:11:"description";s:544:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>This splits the content into font-tag chunks. <br>If there are any &lt;P&gt;/&lt;DIV&gt; sections inside of them, the font-tag is wrapped AROUND the content INSIDE of the P/DIV sections and the outer font-tag is removed.<br>This functions seems to be a good choice for pre-processing content if it has been pasted into the RTE from eg. star-office. <br>In that case the font-tags is normally on the OUTSIDE of the sections.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:6;a:6:{s:8:"property";s:16:"allowTagsOutside";s:8:"datatype";s:20:"commalist of strings";s:11:"description";s:286:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>&nbsp;Enter tags which are allowed outside of &lt;P&gt; and &lt;DIV&gt; sections when converted back to database.<br>Default is &quot;img&quot;<br>Example:<br>IMG,HR";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:7;a:6:{s:8:"property";s:20:"allowTagsInTypolists";s:8:"datatype";s:20:"commalist of strings";s:11:"description";s:213:"<i>(Applies for &quot;ts_transform&quot; only)</i><br>&nbsp;<br>Enter tags which are allowed inside of &lt;typolist&gt; tags when content is sent to the database.<br>Default is &quot;br,font,b,i,u,a,img,span&quot;";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:8;a:6:{s:8:"property";s:9:"allowTags";s:8:"datatype";s:20:"commalist of strings";s:11:"description";s:344:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function getKeepTags))</i><br>&nbsp;<br>Tags to allow. Notice, this list is <i>added</i> to the default list, which you see here:<br>b,i,u,a,img,br,div,center,pre,font,hr,sub,sup,p,strong,em,li,ul,ol,blockquote,strike,span<br>If you wish to deny some tags, see below.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:9;a:6:{s:8:"property";s:8:"denyTags";s:8:"datatype";s:20:"commalist of strings";s:11:"description";s:150:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function getKeepTags))</i><br>&nbsp;<br>Tags from above list to disallow.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:10;a:6:{s:8:"property";s:31:"HTMLparser_rte<br>HTMLparser_db";s:8:"datatype";s:15:"-&gt;HTMLparser";s:11:"description";s:939:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function getKeepTags))</i><br>&nbsp;<br>This is additional options to the HTML-parser calls which strips of tags when the content is prepared for the RTE and DB respectively. You can configure additional rules, like which other tags to preserve, which attributes to preserve, which values are allowed as attributes of a certain tag etc.<br>&nbsp;.nestingGlobal for HTMLparser_db is set by default to &quot;b,i,u,a,center,font,sub,sup,strong,em,strike,span&quot; unless another value is set.<br>Also B/I tags are mapped to STRONG/EM tags in the RTE direction and vise versa.<br>This parsing is done on a per-line basis, so you cannot expect the paragraph tags (P or DIV) to be included.<b><br>&nbsp;</b><br>&nbsp;<b>Notice</b> the -&gt;HTMLparser options, &quot;keepNonMatchedTags&quot; and &quot;htmlSpecialChars&quot; is NOT observed. They are preset internally";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:11;a:6:{s:8:"property";s:24:"dontRemoveUnknownTags_db";s:8:"datatype";s:7:"boolean";s:11:"description";s:528:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function HTMLcleaner_db))</i><br>&nbsp;<br>Direction: To database<br>Default is to remove all unknown tags in the content going to the database. (See HTMLparser_db above for default tags). Generally this is a very usefull thing, because all kinds of bogus tags from pasted content like that from Word etc. will be removed to have clean content in the database.<br>However this disables that and allows all tags, that are not in the HTMLparser_db-list.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:12;a:6:{s:8:"property";s:14:"dontUndoHSC_db";s:8:"datatype";s:7:"boolean";s:11:"description";s:331:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function HTMLcleaner_db))</i><br>&nbsp;<br>Direction: To database<br>Default is to re-convert literals to characters (that is &amp;lt; to &lt;) outside of HTML-tags. This is disabled by this boolean. (HSC means HtmlSpecialChars - which is a PHP function)";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:13;a:6:{s:8:"property";s:26:"dontProtectUnknownTags_rte";s:8:"datatype";s:7:"boolean";s:11:"description";s:566:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function setDivTags))</i><br>&nbsp;<br>Direction: To RTE<br>&nbsp;Default is that tags unknown to HTMLparser_rte is &quot;protected&quot; when sent to the RTE. This means they are converted from eg &lt;MYTAG&gt; to &amp;lt;MYTAG&amp;gt;. This is normally very fine, because it can be edited plainly by the editor and when returned to the database the tag is (by default, disabled by .dontUndoHSC_db) converted back.<br>Setting this option will prevent unknown tags from becoming protected.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:14;a:6:{s:8:"property";s:11:"dontHSC_rte";s:8:"datatype";s:7:"boolean";s:11:"description";s:344:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function setDivTags))</i><br>&nbsp;<br>Direction: To RTE<br>Default is that all content outside of HTML-tags is passed through htmlspecialchars(). This will disable that. (opposite to .dontUndoHSC_db)<br>This option disables the default htmlspecialchars() conversion.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:15;a:6:{s:8:"property";s:21:"dontConvAmpInNBSP_rte";s:8:"datatype";s:7:"boolean";s:11:"description";s:295:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function setDivTags))</i><br>&nbsp;<br>Direction: To RTE<br>By default all &amp;nbsp; codes are NOT converted to &amp;amp;nbsp; which they naturally word (unless .dontHSC_rte is set). You can disable that by this flag.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:16;a:6:{s:8:"property";s:17:"allowedFontColors";s:8:"datatype";s:18:"list of HTMLcolors";s:11:"description";s:222:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function getKeepTags))</i><br>&nbsp;<br>Direction: To DB<br>If set, this is the only colors which will be allowed in font-tags! Case insensitive.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:17;a:6:{s:8:"property";s:14:"allowedClasses";s:8:"datatype";s:15:"list of strings";s:11:"description";s:640:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function getKeepTags))</i><br>&nbsp;<br>Direction: To DB<br>&nbsp;Allowed general classnames when content is stored in database. Could be a list matching the number of defined classes you have. Case-insensitive.<br>This might be a really good idea to do, because when pasting in content from MS word for instance there are a lot of &lt;SPAN&gt; and &lt;P&gt; tags which may have class-names in. So by setting a list of allowed classes, such foreign classnames are removed.<br>If a classname is not found in this list, the default is to remove the class-attribute.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:18;a:6:{s:8:"property";s:22:"skipAlign<br>skipClass";s:8:"datatype";s:7:"boolean";s:11:"description";s:368:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>If set, then the align and class attributes of &lt;P&gt;/&lt;DIV&gt; sections (respectively) will be ignored. Normally &lt;P&gt;/&lt;DIV&gt; tags are preserved if one or both of these attributes are present in the tag. Otherwise it&#039;s removed.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:19;a:6:{s:8:"property";s:15:"keepPDIVattribs";s:8:"datatype";s:32:"list of tag attributes (strings)";s:11:"description";s:287:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>&quot;align&quot; and &quot;class&quot; are the only attributes preserved for &lt;P&gt;/&lt;DIV&gt; tags. Here you can specify a list of other attributes to preserve.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:20;a:6:{s:8:"property";s:17:"remapParagraphTag";s:8:"datatype";s:16:"string / boolean";s:11:"description";s:532:"<i>(Applies for &quot;ts_transform&quot; and &quot;css_transform&quot; only (function divideIntoLines))</i><br>&nbsp;<br>When &lt;P&gt;/&lt;DIV&gt; sections are converted to be put into the database, the tag - P or DIV - is preserved. However setting this options to either P or DIV will force the section to be converted to the one or the other.<br>If the value is set true (1), then it works as a general disable-flag for the whole section-convertion stuff here and the result will be no tags preserved what so ever. Just removed.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:21;a:6:{s:8:"property";s:27:"useDIVasParagraphTagForRTE ";s:8:"datatype";s:6:"string";s:11:"description";s:284:"<i>(Applies for &quot;ts_transform&quot; only and &quot;css_transform&quot; (function TS_transform_rte))</i><br>&nbsp;<br>Use &lt;DIV&gt;-tags for sections when converting lines from database to RTE. Default is &lt;P&gt;. Applies only to lines which has NO tag wrapped around already.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:22;a:6:{s:8:"property";s:14:"preserveTables";s:8:"datatype";s:7:"boolean";s:11:"description";s:87:"<i>(Applies for &quot;ts_transform&quot;)</i><br>&nbsp;<br>If set, tables are preserved";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:23;a:6:{s:8:"property";s:20:"dontFetchExtPictures";s:8:"datatype";s:7:"boolean";s:11:"description";s:204:"<i>(Applies for &quot;ts_images&quot;)</i><br>&nbsp;<br>If set, images from external urls are not fetched for the page if content is pasted from external sources. Normally this process of copying is done.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:24;a:6:{s:8:"property";s:14:"plainImageMode";s:8:"datatype";s:14:"boolean/string";s:11:"description";s:1079:"<i>(Applies for &quot;ts_images&quot;)</i><br>&nbsp;<br>If set, all &quot;plain&quot; local images (those that are not magic images) will be cleaned up in some way.<br>If the value is just set, then the style attribute will be removed after detecting any special width/height CSS attributes (which is what the RTE will set if you scale the image manually) and the border attribute is set to zero.<br>You can also configure with special keywords. So setting &quot;plainImageMode&quot; to any of the value below will perform special processing:<br>&nbsp;<br>&quot;lockDimensions&quot; : This will read the real dimensions of the image file and force these values into the &lt;img&gt; tag. Thus this option will prevent any user applied scaling in the image!<br>&quot;lockRatio&quot; : This will allow users to scale the image but will automatically correct the height dimension so the aspect ratio from the original image file is preserved.<br>&quot;lockRatioWhenSmaller&quot; : Like &quot;lockRatio&quot;, but will not allow any scaling larger than the original size of the image.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:25;a:6:{s:8:"property";s:84:"exitHTMLparser_rte<br>exitHTMLparser_db<br>entryHTMLparser_rte<br>entryHTMLparser_db";s:8:"datatype";s:23:"boolean/-&gt;HTMLparser";s:11:"description";s:274:"<i>(Applies for all kinds of processing)</i><br>&nbsp;<br>Allows you to enable/disable the HTMLparser for the content before (entry) and after (exit) the content is processed with the predefined processors (eg. ts_images or ts_transform).<br>There is no default values set. ";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:26;a:6:{s:8:"property";s:22:"disableUnifyLineBreaks";s:8:"datatype";s:7:"boolean";s:11:"description";s:250:"<i>(Applies for all kinds of processing)</i><br>&nbsp;<br>When entering the processor all rn linebreaks are converted to n (13-10 to 10). When leaving the processor all n is reconverted to rn (10 to 13-10).<br>This options disables that processing...";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}i:27;a:6:{s:8:"property";s:43:"usertrans.[user-defined transformation key]";s:8:"datatype";s:1:"-";s:11:"description";s:110:"Custom option-space for userdefined transformations.<br>See example from section about custom transformations.";s:7:"default";N;s:12:"column_count";i:3;s:16:"is_propertyTable";i:1;}}}', '');