TYPO3 Core

### Eclipse Workspace Patch 1.0

#P igeworkspace42

Index: typo3/sysext/lang/locallang_csh_sysws.xml

===================================================================

--- typo3/sysext/lang/locallang_csh_sysws.xml (revision 288)

+++ typo3/sysext/lang/locallang_csh_sysws.xml (working copy)

@@ -23,9 +23,13 @@

&quot;Notify all users on any change&quot; : All users in workspace are notified regardless of change.</label>

<label index="db_mountpoints.description">If one or more DB mounts are specified the page tree of the backend will be locked into these root points during work in the workspace.</label>

<label index="db_mountpoints.details">Any DB mount specified here must be inside the DB mount set for the backend user who logs in. If that is not the case the workspace DB mount will simply not be mounted for the user. If no DB mounts are specified for the workspace the users will access the DB mounts of their user profile.</label>

+ <label index="use_user_db_mounts.description">To use the DB mounts from the user/group configuration activate this option. Then the workspace DB mounts are not used!</label>

+ <label index="use_user_db_mounts.details">If there are several users with different DB mounts but the same workspace, this option is helpful. If this option is activated the DB mounts of the workspace configuration are not used. Instead of them the user/group DB mounts are used.</label>

<label index="file_mountpoints.description">Filemounts available for workspace users. Please see details for security information!</label>

<label index="file_mountpoints.details">IMPORTANT: By default a draft workspace has all filemounts disabled! This is because versioning does not apply to any files edited through filemounts in TYPO3. Hence any access to those files would violate the principle that no content managed in a draft workspace will be live before published.

However, for specific projects this violation might be acceptable or necessary and therefore you can add a filemount. This will be forced upon any user in the workspace regardless of his filemounts inherited from his groups and user profile!</label>

+ <label index="use_user_file_mounts.description">To use the file mounts from the user/group configuration activate this option. Then the workspace file mounts are not used!</label>

+ <label index="use_user_file_mounts.details">If there are several users with different file mounts but the same workspace, this option is helpful. If this option is activated the file mounts of the workspace configuration are not used. Instead of them the user/group file mounts are used.</label>

<label index="publish_time.description">Specify a time of publication of the workspace content.</label>

<label index="publish_time.details">The publish and unpublish times are active only if &quot;mod/user/ws/cli/ws_cli.phpsh&quot; is set up as a cronjob running every minute. Example configuration could be &quot;* * * * * /[ABSOLUTE PATH TO TYPO3 SITE]/typo3/mod/user/ws/cli/ws_cli.phpsh&quot;</label>

<label index="_publish_time.seeAlso">sys_workspace:unpublish_time</label>