Feature #88087
closed
Visual environment indicator in TYPO3 Backend
Added by Tim Schreiner over 5 years ago.
Updated almost 5 years ago.
Category:
Backend User Interface
Description
Speaking from my own experience, TYPO3 backend users might confound backends from different environments.
This can lead to really worse results. Started from flushing caches in wrong environment or even delete pages/content elements.
It would be nice, if there were a visual indicator that help backend users prevent this mistakes. This indicator should be visible in the backend but also in the login mask.
As an example, the header could get a custom backend color, that can be set via backend extension configuration. But this solution will not work for backend login mask.
So please use this issue to gather more ideas.
Files
Overriding logos and colors via .env isn't sufficient?
Why not simply define our own (very small) skin dependent on ApplicationContext?
if (!\TYPO3\CMS\Core\Utility\GeneralUtility::getApplicationContext()->isProduction()
) {
$GLOBALS['TBE_STYLES']['skins']['my_skin'] = [];
$GLOBALS['TBE_STYLES']['skins']['my_skin']['name'] = 'My Skin';
$GLOBALS['TBE_STYLES']['skins']['my_skin']['stylesheetDirectories'] = [
'css' => 'EXT:my_extension/Resources/Public/Css/Backend/',
];
}
Mathias Schreiber wrote:
Overriding logos and colors via .env isn't sufficient?
I can just talk for myself, but when I'm parallel logged into two backend (dev and prod), just the logo is not enough, because it is often overseen. When working in TYPO3 backend, my eyes doesn't look in the top right corner very often. And to recognise the logo just from canthus, it is too small. Something like a colored header would be more recognisable.
For the login mask, you can set of course a cool background image that punches you the current environment into your face. But to keep the system stringent, maybe a solution that helps the users in both cases with central configuration would be nice.
- Status changed from New to Under Review
- Status changed from Under Review to Rejected
As mentioned by Julian already, this is possible by using an own CSS style and loading that as skin depending on the context. Currently, the indicator color of the top bar is used for workspaces, that would probably also clash with a colored header for context.
As the use case is pretty specific and the feature may be achieved already, I'm closing this ticket here.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 