Favicon in backend causes usability glitches #958

kikmedia · 2017-07-12T12:04:36Z

In b311944 a separate icon for the backend was introduced which causes usability glitches.

I am completely fine with an option showing a backend icon, showing love and prideness for Contao, BUT since I often work in multiple backends at the same time, the community forums are open at the same time in browser and still the Contao project page is open more or less generally AND they all use the same icon now, I just find this not only confusing but annoying.

Shouldn't this be configurable?

The text was updated successfully, but these errors were encountered:

fritzmg · 2017-07-12T12:08:57Z

I agree, I also get confused now while having the community forums and multiple contao backends open within the same browser window.

agoat · 2017-07-13T14:57:08Z

Shouldn't this be configurable?

You can simply change the be_main.html5 template (change/delete the favicon link)

Just an idea: Make the contao favicon for the backend without color (a grey icon)?!

fritzmg · 2017-07-13T15:01:01Z

You can simply change the be_main.html5 template (change/delete the favicon link)

You would have to override the complete be_main.html5 template just for this one line. A template block could be introduced for the favicon.

  <?php $this->block('favicon'); ?>
    <link rel="icon" type="image/png" href="<?= TL_ASSETS_URL ?>bundles/contaocore/favicon.ico">
  <?php $this->endblock(); ?>

Just an idea: Make the contao favicon for the backend without color (a grey icon)?!

Yeah, I'd like that too - but also make it configurable (either via a setting or via a template block).

agoat · 2017-07-13T15:10:05Z

You would have to override the complete be_main.html5

Why the 'complete' template? Just the favicon line..

fritzmg · 2017-07-13T15:13:08Z

Why the 'complete' template? Just the favicon line..

No, you have to override the complete template, because there are no template blocks defined. With template blocks your own be_main.html5 template could look like this:

<?php $this->extend('be_main'); ?>

<?php $this->block('favicon'); ?>
  <link rel="icon" type="image/png" href="<?= TL_ASSETS_URL ?>path/to/your/favicon.ico">
<?php $this->endblock(); ?>

agoat · 2017-07-13T16:04:16Z

With template blocks your own be_main.html5 template could look like this

Can I extend the same template (name) itself? I know the way to extend the 'block_searchable' a.s.o. but never extended the origin template itself without changing the name.

fritzmg · 2017-07-13T16:11:56Z

Yes, you can do that (but only in the /templates folder). This is the recommended way of changing the fe_page template too.

agoat · 2017-07-13T16:35:34Z

You never stop learning..

This is the recommended way of changing the fe_page template too.

Is there a source for recommendation?
In general I make a copy (by simply creating a template from fe_page in the contao template editor), rename it and make my changes. In the layout I select then the changed fe_page template.

fritzmg · 2017-07-13T17:57:22Z

It is inherently recommended ;). If you don't have to override a template completely, you won't miss out on any updates to the parent template.

Another example: if you want to add additional meta tags to the <head> in your fe_page, then your fe_page.html5 could look like this:

<?php $this->extend('fe_page'); ?>

<?php $this->block('meta'); ?>
  <?php $this->parent(); ?>
  <meta name="og:type" content="website">
<?php $this->endblock(); ?>

Also you don't need to specifically select the changed template, if the name is the same as the original.

leofeyer · 2017-07-13T18:20:18Z

Removed in ad7b624.

agoat · 2017-07-13T19:05:09Z

Removed in ad7b624.

Why not using a different favicon?

kikmedia · 2017-07-14T09:06:52Z

Why not using a different favicon?

Because three backends mean that there will be three lookalike favicons, which is in fact not useful. You should be able to control this behaviour, setting individual icons. After removing the code, you are able to do so by simply placing an icon at root level and putting another icon for the frontend into your layout.

agoat · 2017-07-16T08:51:19Z

After removing the code, you are able to do so by simply placing an icon at root level and putting another icon for the frontend into your layout.

Ok. I understand. IMO that looks like the easiest way to do.
A config setting for a backend favicon is somehow too much. Maybe the be_main.html5 template separeted in blocks will bring some advantage to this.

fritzmg · 2017-12-08T13:21:46Z

It seems the orange favicon has been re-added in Contao 4.5-beta3 (Managed Edition). Was this done deliberately?

Aybee · 2017-12-09T15:12:51Z

Why not simply add a favicon.ico to the root? There has to be no code in the HEAD.

A year ago I created a pull request to https://github.com/Ma3xl3/Contao-EasyFavicon. When this will get merged everyone who uses EasyFavicon can easily add the chosen favicon for FE also to the BE by activating a checkbox.

leofeyer · 2017-12-09T16:15:35Z

It seems the favicon has been re-added Contao 4.5-beta3 (Managed Edition).

@fritzmg What exactly do you mean?

fritzmg · 2017-12-09T19:34:51Z

@fritzmg What exactly do you mean?

Execute

composer create-project contao/managed-edition … 4.5-beta3

There will be a web/favicon.ico (the orange Contao logo), which is then automatically visible in the front and back end.

It has been added here: contao/manager-bundle@aa4e4e4

leofeyer · 2017-12-09T20:12:02Z

That's fine. The issue in this ticket was a different one.

fritzmg · 2017-12-09T20:24:50Z

Yeah I realize that now. But still, do we want to have this? Now I have to delete it with every new Contao installation. It's only a minor nuissance, but still.

fritzmg · 2017-12-10T10:06:04Z

Deleting the web/favicon.ico doesn't work, it's added with every composer operation.

> Contao\ManagerBundle\Composer\ScriptHandler::initializeApplication

 Added/updated the web/app.php file.
 Added/updated the web/app_dev.php file.
 Added/updated the web/favicon.ico file.

Instead, one has to replace it with another favicon.ico.

dmolineus · 2017-12-10T20:13:46Z

If I understand the code right after a first short look, the favicon is only added of none exists. Same for the .htaccess file. So you're forced now to add a custom one of you don't want to see the Contao icon.

That's fine with me

fritzmg · 2017-12-10T20:32:40Z

If I understand the code right after a first short look, the favicon is only added of none exists. Same for the .htaccess file. So you're forced now to add a custom one of you don't want to see the Contao icon.

Yes, that's why I wrote

Instead, one has to replace it with another favicon.ico.

However, that's still a little annoying. Implementing the favicon isn't usually the first thing that happens during the development of a website - and if you don't do that, then you got the original problem of this ticket.

So if there's got to be a default favicon.ico, can it at least be the grey one from #963 so that we can distinguish between developing Contao sites and contao.org at a glance again?

Description ----------- | Q | A | -----------------| --- | Fixed issues | Fixes #958 | Docs PR or issue | -  Commits ------- 6b398b20 Set "information_schema_stats_expiry=0" in MySQL 8

leofeyer added the bug label Jul 12, 2017

leofeyer added this to the 4.4.2 milestone Jul 12, 2017

leofeyer self-assigned this Jul 13, 2017

leofeyer added a commit that referenced this issue Jul 13, 2017

Remove the back end favicon again (see #958).

ad7b624

leofeyer closed this as completed Jul 13, 2017

agoat mentioned this issue Jul 14, 2017

[RFC] (Re)add a grey favicon for the backend #963

Closed

agoat pushed a commit to agoat/contao-core-bundle that referenced this issue Aug 1, 2017

Remove the back end favicon again (see contao#958).

3abc0bc

Aybee mentioned this issue Dec 9, 2017

Add an option to add a simple favicon.ico to the root of the Contao installation Ma3xl3/Contao-EasyFavicon#5

Open

leofeyer modified the milestones: 4.4.2, 4.4 May 14, 2019

fritzmg mentioned this issue Jun 3, 2020

Add a default Contao backend favicon to prevent log spamming contao/contao#1785

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Favicon in backend causes usability glitches #958

Favicon in backend causes usability glitches #958

kikmedia commented Jul 12, 2017

fritzmg commented Jul 12, 2017

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 •

edited

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 •

edited

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 •

edited

leofeyer commented Jul 13, 2017

agoat commented Jul 13, 2017

kikmedia commented Jul 14, 2017

agoat commented Jul 16, 2017

fritzmg commented Dec 8, 2017 •

edited

Aybee commented Dec 9, 2017

leofeyer commented Dec 9, 2017 •

edited

fritzmg commented Dec 9, 2017 •

edited

leofeyer commented Dec 9, 2017

fritzmg commented Dec 9, 2017

fritzmg commented Dec 10, 2017 •

edited

dmolineus commented Dec 10, 2017 •

edited

fritzmg commented Dec 10, 2017

Favicon in backend causes usability glitches #958

Favicon in backend causes usability glitches #958

Comments

kikmedia commented Jul 12, 2017

fritzmg commented Jul 12, 2017

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 • edited

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 • edited

agoat commented Jul 13, 2017

fritzmg commented Jul 13, 2017 • edited

leofeyer commented Jul 13, 2017

agoat commented Jul 13, 2017

kikmedia commented Jul 14, 2017

agoat commented Jul 16, 2017

fritzmg commented Dec 8, 2017 • edited

Aybee commented Dec 9, 2017

leofeyer commented Dec 9, 2017 • edited

fritzmg commented Dec 9, 2017 • edited

leofeyer commented Dec 9, 2017

fritzmg commented Dec 9, 2017

fritzmg commented Dec 10, 2017 • edited

dmolineus commented Dec 10, 2017 • edited

fritzmg commented Dec 10, 2017

fritzmg commented Jul 13, 2017 •

edited

fritzmg commented Jul 13, 2017 •

edited

fritzmg commented Jul 13, 2017 •

edited

fritzmg commented Dec 8, 2017 •

edited

leofeyer commented Dec 9, 2017 •

edited

fritzmg commented Dec 9, 2017 •

edited

fritzmg commented Dec 10, 2017 •

edited

dmolineus commented Dec 10, 2017 •

edited