Solution for Stop Replacing My Favicon

[Koos O]

This issue has been going on for years. Examples are:
viewtopic.php?t=937844
viewtopic.php?t=965010
https://github.com/joomla/joomla-cms/issues/17629

The Joomla community refuses to do the simplest thing. Just leave out the Joomla favicons in an update.
Then the old favicons will remain active during an update, regardless of whether they are Joomla favicons or your own or company favicons.

The reasons for this refusal are of course obvious.

A dirty solution was always to copy your template and give it your own name and activate it. The big disadvantage of this is that updates in the template will pass you by.

That can have serious consequences. Not a nice solution.

But luckily now there is a simple solution : Child templates.
It works simply.

Go to systems in the backend, your template and press the child templates button. Go to that child template with filezilla, see a folder there: /domains/yoursite/public_html/media/templates/site/cassiopeia_child/images

place your own favicon in this folder. Done.

Now go in the backend to systems, templatestyles. Open menus and activate all menus in one click.

That's it.
Success.

[ceford]

You do not need a child template! You need to put your own favicons in the right place:

For the Cassiopeia template, Joomla will look for the favicons in the following locations:

media/templates/site/cassiopeia/images - they are not there so Joomla will look in the next location.
media/system/images - they are there so Joomla will use them from there.

https://jdocmanual.org/jdocmanual?artic ... s/favicons

[Koos O]

Unfortunately, then Joomla 5.2.1 comes in

That update places Joomla favicons in media/templates/site/cassiopeia/images
But they are made harmless by the child template

The update also places/overwrites favicons in media/system/images
And that's where it goes wrong :-(
The child template has no influence on that folder (yet?).

Ceford's response is incorrect. He does not solve the update problem with his comment.

The problem is now quickly solved. Just delete those media/systems/images favicons, but this should also be possible without human intervention.

I'll keep looking. Suggestions welcome

[Koos O]

Final solution :-)

I made a mistake by only placing the favicon.ico in the images folder of the child template.

By also placing my own variant favicon as joomla-favicon.svg and the joomla-favicon-pinned.svg in the child it seems that the issue is definitely solved.

[ceford]

Unfortunately, then Joomla 5.2.1 comes in

That update places Joomla favicons in media/templates/site/cassiopeia/images
But they are made harmless by the child template

The update also places/overwrites favicons in media/system/images
And that's where it goes wrong :-(
The child template has no influence on that folder (yet?).

Ceford's response is incorrect. He does not solve the update problem with his comment.

The problem is now quickly solved. Just delete those media/systems/images favicons, but this should also be possible without human intervention.

I'll keep looking. Suggestions welcome

Look at the dates of the favicon files in media/templates/site/cassiopeia/images and media/system/images

Joomla does not place favicon files in media/templates/site/cassiopeia/images during installation or update. You are having problems because you have put them there.

[Koos O]

Sorry ceford,

Ik did not put them there on installation. On the contrary I had deleted them there.

But the update 5.2.1 putted them right back. As always.

If you don't believe me. Read the Githup I provided the link for above.

Excuse me for my English. It is not my native language.

[Mr. Wimpy]

The github issue you refer to is from 2017.
It discusses favicons in protostar; that's Joomla 3.

In my installations (with updates) I don't see favicons in ~/media/.../cassiopeia/images.

So I don't know where your cassiopeia favicons are coming from. How did you update?


=== OFF TOPIC ===

PS. In the manual that ceford refers to, the "site" folder needs to be added to some paths:
At Online processing: #6
At Deployment
At The Link Block

[ceford]

=== OFF TOPIC ===

PS. In the manual that ceford refers to, the "site" folder needs to be added to some paths:
At Online processing: #6
At Deployment
At The Link Block

Thank you for that. Now fixed (in 8 languages).

[Webdongle]

@Koos O
You are Wrong. I present here the proof. Although I do not I do not expect) you will not accept the truth there will be many reading this thread that need to see the evidence so that they don't get misled by your posts.

In Cassiopeia Joomla looks in media/templates/site/cassiopeia/images first. There are no favicon images in that folder in the installation package.

To see a new image of the same name you need to clear your browser cache. So even if Joomla update did overwrite the favicon then your browser would not show it unless you cleared your browser cache.

https://docs-next.joomla.org/docs/templates/favicons/

For the Cassiopeia template, Joomla will look for the favicons in the following locations:

media/templates/site/cassiopeia/images - they are not there so Joomla will look in the next location.
media/system/images - they are there so Joomla will use them from there.

If you want to use your own favicons rather than Joomla favicons you upload them to the first location: media/templates/site/cassiopeia/images. You can do that using the Templates: Customise form. They will not be affected by any update to the Cassiopeia template.

From a Joomla (test) site that started as J5.1.3 updated to J5.2.0 then to J5.2.0. There are no favicons

folders 01.png