Project

General

Profile

Actions

Task #76799

closed

Update workspaces documentation

Added by Francois Suter almost 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Category:
Documentation
Target version:
Start date:
2016-06-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
7.0
Tags:
Complexity:
easy
Sprint Focus:

Description

While working on updating the Inside TYPO3 reference, I realised that its chapter about workspaces had been used as the basis for the "Administration" chapter of the workspaces system extension manual. That's fine, but now this manual also needs to be updated. I'll take care of it as part of my work on Inside TYPO3 (so that I feel good about referring readers to the workspaces manual ;-) ).


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #12712: Generate preview link in documentationClosedFrancois Suter2011-02-01

Actions
Actions #1

Updated by Gerrit Code Review almost 8 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #2

Updated by Gerrit Code Review almost 8 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #3

Updated by Oliver Hader almost 8 years ago

Questions by François taken from the change-set on review.typo3.org:

  • which group can do which actions, i.e. what is the difference between owners, members and the workspace creator?
  • notification settings: when choosing which users to check by default for notification, the list includes owners, members and editors. What are editors (since there are only owners and members fields in the custom workspace definition)?
  • is the "Freeze editing" setting still used (at least I could find no trace in the Core source code)?
  • not all modules used to appear in workspaces. Now they all seem to appear no matter what. Is that right (i.e. is the $MCONF['workspaces'] configuration indeed obsolete)?
  • I found the following User TSconfig option to be not used anymore: options.workspaces.allowed_languages.workspaceId. Right?
  • I found the following Page TSconfig option to be not used anymore: tx_version.workspaces.stageNotificationEmail.additionalHeaders. Right?
Actions #4

Updated by Oliver Hader almost 8 years ago

Oliver Hader wrote:

Questions by François taken from the change-set on review.typo3.org:

  • which group can do which actions, i.e. what is the difference between owners, members and the workspace creator?
  • owner
    • basically the workspace administrator which always can publish changes to the live workspace
  • members
    • "workers" or "editors" that take care about manipulating the content of a workspace
    • if the flag "only workspace owner can publish" is enabled on the "other" tab, members cannot publish to the live workspace
  • responsible persons
    • a sub-selection of the group of all members and owners, that are "responsible" for a particular state
    • useful to limit notifications to those responsible persons of e.g. marketing department or legal department
  • notification settings: when choosing which users to check by default for notification, the list includes owners, members and editors. What are editors (since there are only owners and members fields in the custom workspace definition)?

This behavior has been introduced during development of TYPO3 CMS 7, see http://review.typo3.org/31160. In that regard the term "editors" are those, that initially created a new version for that particular workspace (by creating, modifying, moving, ...). The purpose was to notify only about relevant changes where a backend user has been active as "editor". Of course, the "editor" needs to have access to a particular workspace as being member or owner.

  • is the "Freeze editing" setting still used (at least I could find no trace in the Core source code)?

The DataHandler (core, in general) is still validating that prior to actually execute uploads, data-maps and command-maps.

  • not all modules used to appear in workspaces. Now they all seem to appear no matter what. Is that right (i.e. is the $MCONF['workspaces'] configuration indeed obsolete)?

Some still disappear, like "configuration" or "DB check" in the admin section. Unfortunately I don't know whether that was on purpose or just forgotten when rewriting the backend modules (Extbase, routing, ...)

  • I found the following User TSconfig option to be not used anymore: options.workspaces.allowed_languages.workspaceId. Right?

This settings is applied in BackendUserAuthentication directly and thus overrides the current $BE_USER. It's still there in TYPO3 CMS 8.2

  • I found the following Page TSconfig option to be not used anymore: tx_version.workspaces.stageNotificationEmail.additionalHeaders. Right?

This option has been removed without any substitution during 6.1 development, see https://review.typo3.org/#/c/19739/

Actions #5

Updated by Gerrit Code Review almost 8 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #6

Updated by Gerrit Code Review almost 8 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #7

Updated by Gerrit Code Review almost 8 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #8

Updated by Gerrit Code Review almost 8 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #9

Updated by Gerrit Code Review almost 8 years ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48696

Actions #10

Updated by Francois Suter almost 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #11

Updated by Gerrit Code Review almost 8 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49326

Actions #12

Updated by Francois Suter almost 8 years ago

  • Status changed from Under Review to Resolved
Actions #13

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF