Bug #86512
closed
Site-functionality: Adjust enable/disable-functionality
100%
Description
In the "Sites"-module the context-menu of a site allows to enable/disable it. While the status in the context-menu updates, it doesn't seem to have a direct effect.
Do we want to be able to deactivate a site? And if yes, what would a deactivated site behave like? Or should we simply remove the enable-columns for that functionality?
Updated by Stefan Neufeind about 6 years ago
- Tracker changed from Task to Bug
It turned out that the world-icon in front of the site-name has the context-menu of the rootpage of that site. While that makes perfect since, it is some what irritating.
Well, then that world-icon at least should also show the enabled/disabled status, which will show you what page is activated or not.
Updated by Susanne Moog about 6 years ago
- Sprint Focus set to On Location Sprint
Updated by Benni Mack about 6 years ago
If we want to have this, it should disable/enable a page, not the site config
Updated by Gerrit Code Review about 6 years ago
- Status changed from New 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/58727
Updated by Joerg Kummer about 6 years ago
It's just the missing assinged property hidden of pages requested from rootline, which would be considered using IconForRecordViewHelper.
Updated by Joerg Kummer about 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 2b15636365b3ec14803e572b38b84d37e022f409.
Updated by Markus Klein almost 6 years ago
- Related to Bug #87076: Missing icon overlays within usage of BackendRootline added