a:1:{s:4:"rows";a:9:{i:0;a:6:{s:8:"property";s:8:"admPanel";s:8:"datatype";s:13:"-&gt;ADMPANEL";s:11:"description";s:43:"Options regarding the front-end admin panel";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:1;a:6:{s:8:"property";s:7:"options";s:8:"datatype";s:12:"-&gt;OPTIONS";s:11:"description";s:29:"Options for the user, various";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:2;a:6:{s:8:"property";s:3:"mod";s:8:"datatype";s:38:"<i>(see -&gt;MOD of Page TSconfig)</i>";s:11:"description";s:91:"Overriding values for the backend modules<br>&nbsp;<b>Deprecated. </b>Use page.mod instead!";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:3;a:6:{s:8:"property";s:32:"setup.defaults<br>setup.override";s:8:"datatype";s:10:"-&gt;SETUP";s:11:"description";s:481:"Default values and override values for the user settings known from the setup module.<br>&nbsp;<b><br>Notice:</b><br>There is a tricky aspect to these settings; If first you have set a value by setup.override and then removes it again you will experience that the value persists to exist. This is because it is saved in the backend users profile. Therefore, if you have once set a value, do <i>not</i> remove it again by rather set it blank if you want to disable the effect again!";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:4;a:6:{s:8:"property";s:31:"TCAdefaults.[tablename].[field]";s:8:"datatype";s:6:"string";s:11:"description";s:754:"Sets default values for records. The order of default values when creating new records in the backend is this:<br>Value from $TCA<br>Value from User TSconfig (these settings)<br>Value from &#x201c;defVals&#x201d; GET vars (see alt_doc.php)<br>Value from previous record based on &#039;useColumnsForDefaultValues&#039;<br>&nbsp;<br>However the order for default values used by tcemain.php if a certain field is not granted access to for user will be:<br>Value from $TCA<br>Value from User TSconfig (these settings)<br>&nbsp;<br>So these values will be authoritative if the user has no access to the field anyway.<br>&nbsp;<b><br>Example:</b><br>This sets the default hidden flag for pages to &#x201c;clear&#x201d;<br>&nbsp;<br>TCAdefaults.pages.hidden = 0";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:5;a:6:{s:8:"property";s:4:"user";s:8:"datatype";s:6:"&nbsp;";s:11:"description";s:87:"This is for custom purposes. <br>Deprecated, use &quot;tx_*&quot; below from extensions";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:6;a:6:{s:8:"property";s:4:"auth";s:8:"datatype";s:6:"&nbsp;";s:11:"description";s:203:"Configuration for authentication services. Currently these are the options:<br>&nbsp;<b><br>auth.BE.redirectToURL</b><br>Specifies a URL to redirect to after login is performed in the backend login form.";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:7;a:6:{s:8:"property";s:4:"page";s:8:"datatype";s:28:"all page TSconfig properties";s:11:"description";s:195:"You can override all page TSconfig properties by putting them into user<br>TSconfig and prefixing them with page.<br>&nbsp;<b><br>Example:</b><br>page.TCEMAIN.table.pages.disablePrependAtCopy = 1";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}i:8;a:6:{s:8:"property";s:37:"tx_[extension key with no underscore]";s:8:"datatype";s:6:"&nbsp;";s:11:"description";s:38:"This is reserved space for extensions.";s:7:"default";s:6:"&nbsp;";s:12:"column_count";i:4;s:16:"is_propertyTable";i:1;}}}