phbernard

Wow, I’m glad you figured this out! 🙂

Thanks Galina 🙂

Thank you for your feedback!

Hi,

Thank you for your message!

Yes, query strings are optional. You have some because you have probably checked the “Version” feature while generating your icons.

If you are updating the favicon of an existing site and want your returning visitors to see the new favicon and not the old one, then I suggest you to keep the query strings as they are. They force the browsers to reload the icons (browsers tend to cache the favicons, which is annoying when you undergo a huge re-design but your visitors still see your old icon).

If query strings are just too annoying, they I suggest you to generate your icons again. This time, make sure to not check anything in the “Version” tab of the options.

Best Regards,
Philippe

Thank you for your review!

Hi,

Thanks for the review!

😉

Hi,

Your icons work. It’s the favicon checker’s fault. You can safely forget about this issue.

Explanations: you apparently used the “versioning” feature of RealFaviconGenerator, probably because you are updating an existing site. When using this feature, RFG generates link suffixes such as v=Kmnm3OrjEy. This auto-generated suffix is just fine but if you want you can change it, which you apparently did. The problem is that you entered http://synchronet.co/favicon.ico as the value. Because this is a URL, the favicon checker is somehow misled when it tries to process a path such as /wp-content/uploads/fbrfg/favicon.ico?v=http://synchronet.co/favicon.ico (“what’s this http:// in the middle of the path?”) and fails. But the links themselves are correct and both Chrome and Firefox display your favicon.

If you really want to get the “full green” report when checking your favicon: please generate your favicon again, and this time leave the versioning values as they are (eg. v=Kmnm3OrjEy). Run the favicon checker again, it should pass.

If you only wanted to have your favicon up and ready: Do nothing. It works as it is, really.