Site-functionality: Adjust enable/disable-functionality
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?
[TASK] Add field pages.hidden to rootline default fields
Adding field 'hidden' to default field list of rootline page requests
ensures more detailed rendering of page status in FLUID using
Tested-by: TYPO3com <email@example.com>
Reviewed-by: Jasmina Ließmann
Tested-by: Jasmina Ließmann <firstname.lastname@example.org>
Reviewed-by: Jürgen Heym <email@example.com>
Tested-by: Jürgen Heym <firstname.lastname@example.org>
Reviewed-by: Benni Mack <email@example.com>
Tested-by: Benni Mack <firstname.lastname@example.org>
#1 Updated by Stefan Neufeind 2 months 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.