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

Resource Tree problems with template icons #29

Closed
wuuti opened this issue Jul 29, 2015 · 2 comments
Closed

Resource Tree problems with template icons #29

wuuti opened this issue Jul 29, 2015 · 2 comments

Comments

@wuuti
Copy link

wuuti commented Jul 29, 2015

We use template icons a lot in our installations. All of them (v2.3.5) show problems at the dashboard displaying the resource tree: some of the icons there are not shown, instead cryptics signs (unicode char?) show up. The problem definitely occurs in FF (chrome works). Icons of the resource tree are shown correctly on any other page - but not on the dashboard if QuickStartButtons widget is there.
Here is a screenshot of the RT in Firefox showing the problem:

qs_buttons_error1

And this is how it is expected to look like:

screenshot from 2015-07-29 17 26 08

The icons not working here are -building and -newspaper-o - both of them not available at QuickstartButtons. So I assume the cause is the old Fontawesome version of QB, which seems to overwrite the dashboards css somehow causing the resource tree icons having the "wrong" font.

If this cannot be fixed in general, it might be the best to remove the FA as supposed in #26 to prevent any such errors now and in the future (hard to keep the core and QB versions of Font-Awesome in sync, and quite useless to deliver redundancy).

@wuuti
Copy link
Author

wuuti commented Jul 29, 2015

Just realized I already opened an issue for that some weeks ago (#25) :-(. I should read my own comments...
Anyway, closed that one in favour of this which provides a bit more information.

@Mark-H
Copy link
Member

Mark-H commented Mar 7, 2016

This appears fixed when using 1.3. Likely related to #35 one way or another? Please reopen if you can still replicate the issue with 1.3.

Be sure to specify the icon as icon-building, and not just building, though I guess that's just a typo in your issue.

@Mark-H Mark-H closed this as completed Mar 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants