Home Forums Weaver Xtreme Theme Favicons, Site Icons and Weaver 5

Topic Resolution: Resolved
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #70354


    First, I have updated to WP5.9 a few hours ago and all worked perfectly. No issues at all!

    Second, thank you so much for answering my request and incorporating custom URLs for Favicons etc. into the Customizer. This is greatly appreciated, as I can now serve them from my Cloudinary plugin, rather than WP. Thanks!

    However, there is a minor issue with the Favicons, which is possible a legacy issue, and it results in us serving Favicons from both Cloudinary and WP.

    In previous version of Weaver and Xtreme, it was possible to serve separate images for the Favicon and the Apple-Touch-Icon withing the settings. I installed these assets in the site root directory, as well as an upload directory, and they are still there now.

    After your latest Xtreme update, I added a link in the customizer at the appropriate place under “Site Icon”, the URL being https://res.cloudinary.com/hkp/images/f_auto,q_auto/v1617849029/favicon/favicon-png?_i=AA

    (I used 16×16 rather than the recommended 512×512 size, as that used massively more broadband, for no obvious benefit. Our Favicon has always been 16×16 and our apple-touch-icon 50×50)

    On checking our site, https://www.hiskingdomprophecy.com/ with GTmetrix, I found that under their Waterfall Tab, the last item is favicon.ico and it is supplied from https://www.hiskingdomprophecy.com/wp-content/uploads/2019/12/favicon.ico

    When checking with Cloudinary, I find that they are also providing the favicon.ico from the above URL.

    Ergo, Favicon.ico is now being delivered from two sources.

    Then searching the source code, on line 11, I found under <!-- Weaver Xtreme Standard Google Fonts for page-type: pwp --> the line: href="/wp-content/uploads/2019/12/favicon.ico" />

    And then I also found on lines 120-123:

    <link rel="icon" href="https://res.cloudinary.com/hkp/images/w_16,h_16,c_fill/f_auto,q_auto/v1617849029/favicon/favicon-png?_i=AA" sizes="32x32" />
    <link rel="icon" href="https://res.cloudinary.com/hkp/images/w_16,h_16,c_fill/f_auto,q_auto/v1617849029/favicon/favicon-png?_i=AA" sizes="192x192" />
    <link rel="apple-touch-icon" href="https://res.cloudinary.com/hkp/images/w_16,h_16,c_fill/f_auto,q_auto/v1617849029/favicon/favicon-png?_i=AA" />
    <meta name="msapplication-TileImage" content="https://res.cloudinary.com/hkp/images/w_16,h_16,c_fill/f_auto,q_auto/v1617849029/favicon/favicon-png?_i=AA" />

    Everything is working, but it seems that there is a bit of duplication at work here.

    I shall leave it with you and let you advise. If you have any questions,
    please do ask.

    Finally, is there any way I can provide different images for the Favicon and the Apple-Touch-Icon as previously? Just curious, for at the moment, it looks not possible. In not, no matter.

    Regards and thanks,


    That was a bit difficult to follow.

    It has been a very long time since I’ve heard much mention of Apple-touch-icons associated with core WP. Because Weaver  Xtreme still generates .ios classes, that could be used, but from my perspective, Apple Touch Icons are fairly irrelevant now, and have been for quite a while.

    Once a feature becomes core WP, like the fav icon, it really means that is a bit off topic for themes.

    I know Apple Touch Icons had some sort of meaning at one point, but I really don’t remember their exact purpose any more, and they probably aren’t worth much effort on you part, either.



    Thank you. I shall simplify 🙂

    To cut to the chase: Our Favicon Icons are loaded twice.

    First on line 11 and again on lines 120-123 of the home page source code.

    Each is loaded from a different source. Line 11 from WP server and Lines 120-123 from Cloudinary plugin server.


    Don’t know how the plugin server works, but I think if you don’t specify a favicon to WP, no code gets generated.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.