Feature #88087

Visual environment indicator in TYPO3 Backend

Added by Tim Schreiner about 2 months ago. Updated about 2 months ago.

Status:
Under Review
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2019-04-05
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

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.

screenshot-example.ddev.local-2019.04.05-10-33-13.png View (11.4 KB) Julian Hofmann, 2019-04-05 10:36

History

#1 Updated by Mathias Schreiber about 2 months ago

Overriding logos and colors via .env isn't sufficient?

#2 Updated by Julian Hofmann about 2 months ago

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/',
    ];
}

#3 Updated by Tim Schreiner about 2 months ago

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.

#4 Updated by Gerrit Code Review about 2 months 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/c/Packages/TYPO3.CMS/+/60408

Also available in: Atom PDF