Project

General

Profile

Actions
Copy link

Bug #72567

closed

Backend Configuration Manager - Workspaces

Added by Millon Antoine almost 9 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2016-01-07
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hello,

On a TYPO3 6.2.17.

Site is using Flux, maybe you'll consider it's a Flux issue.

Site uses workspaces.

All tests were made in LIVE mode.

The pb was the following :
  • We use flux to display a template selection in page properties. At the begining of the week, it disappeared : no template could be selected in pages properties.
  • Flux need TS configuration to work : it uses getTypoScriptSetup() from TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager.
  • Now is the trick : a new site had been created (page set as siteroot) in a specific workspace (not in LIVE).
  • In LIVE, TS configuration was set using this site page id as root. Method TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager::getCurrentPageIdFromCurrentSiteRoot() returned the workspace page as root, not the actual LIVE root page.

Told contributors to not create new sites on workspaces.
But the fact is that it's something they can actually do.
Maybe getCurrentPageIdFromCurrentSiteRoot should take care of current workspace.
Or maybe users should be prevented from creating new site while working in workspace.

Thanks for your time,

Tchuss !

Actions
Copy link

Also available in: Atom PDF