-
Notifications
You must be signed in to change notification settings - Fork 210
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
Cannot see font-awesome icons under login #690
Comments
I believe this should fix it. 75c2fef |
hmm, since it's a small bug, could you maybe submit a quick PR just for that part? @kaustubh-nair. Then we can confirm its fixing it. |
@sashadev-sky I think it should be fixed now, since a671852 got merged. Can you check again and confirm? |
Yes its fixed! But I still see were pulling 2 different font-awesome packages into /public/lib that are version 4.2.0 and also pulling in another one via cdn that is version 5.8.2. I am going to open a PR to try getting it down to 1? Or is there a reason for this? @kaustubh-nair One of the packages might go away after I link mapknitter to the latest LDI release where I removed font-awesome as a dependency |
Hey @sashadev-sky I've tried looking into the cause of this.. I think this is happening because |
@kaustubh-nair also in the process of removing font-awesome dependency in favor of svg sprites so we can use any icons we'd like in LDI! @jywarren |
@kaustubh-nair font awesome has been removed from ldi! Is this issue fixed btw? |
We're using a new signup popup now right? I think @divyabaid16 implemented it? |
@kaustubh-nair yes closing this its stale and resolved! |
in the PR #633 a new
<link>
tag was added toapplication.html.erb
for font-awesome:mapknitter/app/views/layouts/application.html.erb
Line 15 in 5f25aa6
This makes it so that the icons no longer show up for this particular set of icons:
Removing this line brings the icons back
@stefannibrasil does this cause the same problem for you locally? Also was this meant for a font-awesome upgrade? I think we should update this dependency across the whole repo if were upgrading, and then link to the relative path in the href. Right now we are pulling 2 versions
The text was updated successfully, but these errors were encountered: