<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallang>
	<meta type="array">
		<description>CSH for Frontend Users</description>
		<type>CSH</type>
		<csh_table>fe_users</csh_table>
	</meta>
	<data type="array">
		<languageKey index="default" type="array">
			<label index="username.description">Enter the username of the website user. This is needed to login.</label>
			<label index="username.syntax">A username is required and must be in lowercase without spaces in it. The username must be unique among other usernames in the page where it's saved. If it is not unique a number will be prepended automatically.</label>
			<label index="_username.seeAlso">Creating Frontend Users and Groups | http://typo3.org/documentation/document-library/doc_tut_quickstart/Create_users_group/</label>
			<label index="password.description">Enter the password for the username above. This is needed to login.</label>
			<label index="password.syntax">A password is required and must be in lowercase without spaces in it.</label>
			<label index="usergroup.description">Select a user group for the username.</label>
			<label index="usergroup.details">When a user logs in he is able to view all content which is access restricted to the user &lt;em&gt;group(s)&lt;/em&gt; the user is a member of. Therefore the user login primarily makes sense with regard to the member groups.</label>
			<label index="lockToDomain.description">Enter the host name from which the user is forced to login.</label>
			<label index="lockToDomain.details">A TYPO3 system may have multiple domains pointing to it. Therefore this option secures that users can login only from a certain host name.</label>
			<label index="lockToDomain.syntax">Either a domain name, &quot;www.typo3.com&quot; or an IP address, &quot;10.34.222.83&quot;</label>
			<label index="_lockToDomain.seeAlso">fe_groups:lockToDomain</label>
			<label index="name.description">Enter the regular name of the user, both first- and surname.</label>
			<label index="address.description">Enter the street address of the user.</label>
			<label index="www.description">Enter the homepage URL</label>
			<label index="title.description">Enter the job title, eg. 'Director' or 'Accountant'.</label>
			<label index="company.description">Enter the name of the company in which the user is employed.</label>
			<label index="image.description">Insert a photo of the user.</label>
			<label index="disable.description">This option will temporarily disable the user from logging in.</label>
			<label index="_disable.seeAlso">fe_users:starttime,fe_users:endtime</label>
			<label index="starttime.description">Enter the date from which the account is active.</label>
			<label index="starttime.syntax">The syntax is dd-mm-yy, but you can just enter a &quot;d&quot; in the field to insert todays date. Or &quot;d+10&quot; to insert the date 10 days from now etc.
The field will re-format any input to fit the format it understands so you can just experiment and you will be able to clearly see how dates should be entered.</label>
			<label index="_starttime.seeAlso">fe_users:disable,fe_users:endtime</label>
			<label index="endtime.description">Enter the date from which the account is disabled.</label>
			<label index="endtime.syntax">See &quot;Start&quot;</label>
			<label index="_endtime.seeAlso">fe_users:disable,fe_users:starttime</label>
			<label index="TSconfig.description">Enter additional TSconfig for the user (advanced).</label>
			<label index="TSconfig.details">This field allows you to enter TypoScript style configuration values for the user. Currently there are no system defined keys. If there ever will be, they will be described in detail in the administrative documentation.

The primary use of this field (as well as the 'sister'-field in the Website usergroup table) is for custom purposes. In this case, you should use the root-key &quot;user&quot; for your customly defined values. Thus you don't risk any future system keys to interfere with your configuration.

You access the values of the configuration from your frontend plugins by calling the function &lt;em&gt;$GLOBALS[&quot;TSFE&quot;]-&gt;fe_user-&gt;getUserTSconf()&lt;/em&gt; which will return an array with the valuetree in it.

&lt;b&gt;Warning:&lt;/b&gt; You should use Website user/group TSconfig in your PHP-scripts ONLY if your resulting content is NOT being cached! So call it from TypoScript USER_INT cObjects or disable caching from your PHP-code by calling &lt;em&gt;$GLOBALS[&quot;TSFE&quot;]-&gt;set_no_cache();&lt;/em&gt;

&lt;b&gt;TSconfig from Website usergroups:&lt;/b&gt;
Notice that the configuration from the field TSconfig in the member groups of the user is accumulated and prepended to the TSconfig of the user before it's parsed. This means for instance that a key defined in the TSconfig of the user (this field) will override the same key defined in the last (bottom) usergroup in the list which will again override the same key defined in the first (top) usergroup in the list.

&lt;b&gt;Example:&lt;/b&gt;
Let's imagine you want to define for a user that his name is printed in the bottom of the webpages when he is logged in. First of all you must write a PHP-function and insert the result from it as a USER_INT cObject in the bottom of the page. But your function needs to know, whether or not this user is configured to have his name printed. So you decide to use a custom TSconfig key, 'user.printUserName':

&lt;em&gt;In the TSconfig field of the user or usergroup:&lt;/em&gt;

user.printUserName = 1


&lt;em&gt;In your PHP-function:&lt;/em&gt;

$userTSConfig = $GLOBALS[&quot;TSFE&quot;]-&gt;fe_user-&gt;getUserTSconf();
if ($userTSConfig[&quot;user.&quot;][&quot;printUserName&quot;]) {
  return $GLOBALS[&quot;TSFE&quot;]-&gt;fe_user-&gt;user[&quot;name&quot;];
}</label>
			<label index="TSconfig.syntax">TypoScript syntax, without conditions and constants.</label>
			<label index="_TSconfig.seeAlso">TSconfig for TSFE | http://typo3.org/documentation/document-library/doc_core_tsconfig/TCEMAIN/
pages:TSconfig,
fe_groups:TSconfig,
be_users:TSconfig,
be_groups:TSconfig</label>
			<label index=".description">A website login user.</label>
			<label index=".details">These are users with a username and password who are allowed specific access to otherwise restricted areas on your website.</label>
			<label index="_.seeAlso">fe_groups
be_users</label>
			<label index="_.image">EXT:context_help/cshimages/feusers_1.png,
EXT:context_help/cshimages/feusers_2.png,</label>
			<label index=".image_descr">Part of the form for editing a frontend user.
A typical login box (standard) on the website where frontend users can login.</label>
		</languageKey>
	</data>
</T3locallang>