Skip to content
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

[BUG] Icons, getting it wrong #1288

Closed
5 tasks done
Nivin37 opened this issue Aug 17, 2023 · 6 comments
Closed
5 tasks done

[BUG] Icons, getting it wrong #1288

Nivin37 opened this issue Aug 17, 2023 · 6 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working 🕸️ Inactive

Comments

@Nivin37
Copy link

Nivin37 commented Aug 17, 2023

Environment

Self-Hosted (Docker)

System

CASA OS V0.4.4.1

Version

2.2.1

Describe the problem

When I add an icon name and I get it wrong, after saving the Item you get to see the broken icon symbol.

However when I then go back to fix the broken icon, I can never fix it.
I have tried to incert the correct name, remove all reference and save, use another correct icon name, all fail.
The only way I have found to fix this issue is to remove the item and start again.

My current build is on CASA OS, however I did have the same issue with a previous build I did on a Debian VM.

Additional info

No response

Please tick the boxes

@Nivin37 Nivin37 added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Aug 17, 2023
@liss-bot
Copy link
Collaborator

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

@TKinslayer
Copy link

I do have the same problem, actually.
I would also add the fact that plenty of icons (even when I seem to get them right on the first) do not « work » - I get a broken icon. No icons from font awesome works, actually. I can make some icons work from SimpleIcon or others.

I can’t say the problems don’t come from me, though… (I mean… I’m very new to Dashy and I may do something wrong). But that bug sure looks like what I’m experiencing.

On a side note, great, great, great app !

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Aug 19, 2023
@PooreOne
Copy link

PooreOne commented Oct 1, 2023

I also experience this. I've seen the icon work, then break, and I could then never get an icon to show again using local or hosted icons like dashboard-icons. Switching to favicon I saw the exact behavior again where notifiarr icon worked, then broke and never came back.

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Oct 2, 2023
@liss-bot
Copy link
Collaborator

This issue has gone 3 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

@liss-bot liss-bot added the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Dec 31, 2023
@github-project-automation github-project-automation bot moved this to Todo in Dashy V3 Dec 31, 2023
@liss-bot
Copy link
Collaborator

liss-bot commented Jan 6, 2024

This issue was automatically closed because it has been stalled for over 1 year with no activity.

@liss-bot liss-bot closed this as completed Jan 6, 2024
@github-project-automation github-project-automation bot moved this from Awaiting Triage to Done in Dashy V3 Jan 6, 2024
@liss-bot liss-bot removed the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Jan 6, 2024
@Taverius
Copy link

This is absolutely still a thing that happens, and the solution is to recreate the docker image.

Looks like you're caching the remote icons locally, and so long as you're switching between valid icons it works. If you put in something which yields no icon, like a fontawesome you don't have access to, and swap back, that also works.

But if you ever end up with the broken icon icon, that never gets cleared from the cache.

What's the location in question so I can clear it, either by mounting it with a bind and wiping when needed, or with a quick rm inside the docker?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working 🕸️ Inactive
Projects
Status: Done
Development

No branches or pull requests

6 participants