-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Favicon is considered orphaned media #30281
Labels
Comments
cadusilva
added
bug
Something isn't working
status/to triage
This issue needs to be triaged
labels
May 13, 2024
ClearlyClaire
added
status/identified
This bug has been identified
and removed
status/to triage
This issue needs to be triaged
labels
May 15, 2024
ClearlyClaire
added a commit
that referenced
this issue
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce the problem
tootctl media remove-orphans
.png
is now gone, but.ico
remains....
Expected behaviour
Favicon not to be considered orphaned media
Actual behaviour
Favicon is considered orphaned media and deleted
Detailed description
After #30040, admins can now upload favicons to their instances. But the
tootctl media remove-orphans
command considers them as orphaned media, so the.png
files are deleted. The.ico
version is preserved, but the favicon used by browsers is the.png
one, so they fail to show a favicon at all. Akkoma instances also fails to present the favicon.Mastodon instance
bolha.one
Mastodon version
v4.3.0-alpha.3-1959365
Technical details
If this is happening on your own Mastodon server, please fill out those:
3.3.1 (2024-04-23 revision c56cd86388)
v20.13.0
The text was updated successfully, but these errors were encountered: