-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
'Fatal error' when processing favicon #19
Comments
I should add, I'm using |
Hi, thank you for reporting and sorry for the late answer. Apparently this is because your Note that |
Well I don't want to add a special case for empty file name. After all, this is not the only illegal file name. In the next version of the plugin, you will get additional information by adding |
Done in v0.1.4 |
Hi Philippe, Thanks for your help - I feel like an idiot - I completely missed the empty filename array I've just re-run it and it has now injected the favicon markup into the page. One question though (and I might be missing something else here) - what determines the position on the page where the favicon markup gets injected? Thanks again, Chris |
No prolem, I didn't spot it either, and I had to debug to find out! The injection is done with the |
OK cool, thanks very much :) Chris |
You're welcome! Philippe |
I'm having trouble getting the Grunt task to work.
Gruntfile.js task:
It's basically what's given in the readme, just with a couple of updated paths. I wanted to see what the standard code output before making too many changes.
Console output:
Do you have any idea what the issue might be?
Thanks very much.
Chris
The text was updated successfully, but these errors were encountered: