phbernard

Thank you!

Damn! I need more reviews like yours! 🙂

oo
   oo     OOOOOOOO:       OOOOOOOO!
      oOOOO!!!!;;;;O    OO.......:;!O
     'OOO!!!;;;;;;;;O  O.......:   ;!O
     OOO!!!!;;::::::.OO........:    ;!O
     OO!!!!;;:::::..............:   ;!O
     OOO!!!;::::::..............:   ;!O
      OO!!;;::::::.............:   ;!O
       OO!;;::::::......oo.....::::!O
         O!!;::::::........oo..:::O
           !!!;:::::..........ooO
              !!;:::::.......O   oo
                ;;::::.....O        oo  ,o
                   :::..O              ooo
                     ::.              oooo
                      :

Alright… it should be better that way 🙂

Thank you Rachel!

Thank you Chris!

Unfortunately the plugin offers no workaround for this at the moment. If the validation error is a blocking issue for you, then you shouldn’t use the plugin.

As an aside: is this issue critical for you? I mean:

• All pages, including famous ones (Google’s homepage, Amazon’s homepage…) have validation errors at some point.
• Although this attribute is not W3C compliant, it is introduced by Apple so this is the kind of proprietary feature which is supposed to spread across the web, whatever it is correct or not.

So from my point of view, this is the kind of error that can be safely ignored. But if that’s not the case for everyone, I would like to know the context (eg. “hard corporate policy”, “customer doesn’t want any error”, etc.).

Actually the presence of paths such as /wp-content/uploads/fbrfg/favicon.ico in your code is normal, it’s always that way. Because I forgot to mention a point: when the rewriting (ie. ‘/favicon.ico) fails, it often fails silently, without the plugin being notified about this. So it always chooses the safe way (ie./wp-content/uploads/fbrfg/favicon.ico`).

What you can do to test your site is to fire http://www.yoursite.com/favicon.ico with your browser.

The first versions of the plugin were more reckless, trying to take advantage of the rewrite API as much as possible. But many people reported issues, mostly because of security plugins and hosting providers. So I changed my approach.

No the plugin doesn’t override the Site icon yet. I didn’t know WP was also using this icon that way… I definitely need to hurry! Thanks for reporting!