Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaking: #98437 - Workspace TSConfig swapMode and changeStageMode removed #3172

Closed
sabbelasichon opened this issue Oct 2, 2022 · 0 comments · Fixed by #3187
Closed

Breaking: #98437 - Workspace TSConfig swapMode and changeStageMode removed #3172

sabbelasichon opened this issue Oct 2, 2022 · 0 comments · Fixed by #3187

Comments

@sabbelasichon
Copy link
Owner

Breaking: #98437 - Workspace TSConfig swapMode and changeStageMode removed

https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/12.0/Breaking-98437-WorkspaceTSConfigSwapModeAndChangeStageModeRemoved.html
.. include:: /Includes.rst.txt

.. _breaking-98437-1664187644:

==========================================================================
Breaking: #98437 - Workspace TSConfig swapMode and changeStageMode removed

See :issue:98437

Description

The following User TSconfig options related to the system extension "workspaces"
have been removed.

  • :typoscript:options.workspaces.swapMode
  • :typoscript:options.workspaces.changeStageMode

Impact

Setting the above options to :typoscript:any or :typoscript:page in
User TSconfig has no effect anymore: They were used to publish and change
state of more than the selected records in the workspace Backend module, which
was a rather hard to grasp feature for editors and usability wise questionable.

Affected installations

Instances with loaded workspaces extensions using these options in
User TSconfig are affected.

These options were most likely used very seldom and the implementation has
been at least partially broken since TYPO3 core v8.

Migration

No migration path available.

.. index:: Backend, TSConfig, NotScanned, ext:workspaces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants