phbernard

Hi,

No problem! WordPress can be quite messy sometimes, it’s hard to figure out this kind of issue.

Best Regards,
Philippe

Hi,

Your favicon looks great! The favicon checker gives a full-green status.

Even Google shows your favicon, whereas it can sometimes takes so long to have your favicon crawled…

What is your issue exactly? Where is your favicon absent?

Hi,

RealFaviconGenerator plugin has nothing to do with this file. Judging by its name, it seems to be related with Elementor.

Is there something that make you think the plugin might be related with this issue?

Thank you ??

Hi,

Sorry for the late answer. Yes, the plugin has been tested with WP 6.6, and also 6.7. Do you still face the issue?

Regards,
Philippe

Hey WIlliam,

Thank you for your message!

About the specific icons for iOS and Android: yep, other people has asked for it too. It should be back in a few days or weeks.

About the Site icon: what you propose definitely makes sense. Added to the roadmap!

Hi,

Yes, the plugin has been tested successfully with PHP 8.2.23.

Cheers,
Philippe

No problem ??

Thank you so much!! This is the very first feedback I got since the release of the new version ??

Hi,

I’m sorry for the inconvenience. RealFavicon has undergone a huge update yesterday and I’m afraid you have been caught in the middle of the process.

Could you give it another try? This time, when switching from your WordPress site to RealFaviconGenerator (where you can customize your icon), you should notice that the design of RealFaviconGenerator has changed compared to yesterday. If not, this is probably because of a DNS caching issue (ie. your browser is still pointing to the old version of the web site), and you should wait for a few additional hours.

Please let me know if it now works!

Hello Kai,

I don’t have news from you. Maybe you’ve found the solution? I mark the issue as resolved. Please reopen it if you feel you need additional assistance.

Best Regards,
Philippe

Great! Thank you for letting me know.

Best Regards,
Philippe

Hi,

Unfortunately, this is not possible. Adding crossorigin="use-credentials" has serious security implications, as the browser may now send authentication data to another web site. I’m not in favor of an option either (like “Enable crossorigin="use-credentials"“), because it is quite hard to understand and users could enable it without understanding the implications.

May I ask you how you end up with this error? In your example, the web manifest is in the root of your site, but there is no issue in this situation, correct? Is your manifest hosted on another domain? If so, is there a reason why its access is restricted?

Hello Kai,

I’m sorry for the inconvenience. Although this is an issue that ought to be fixed, it’s quite harmless: your visitors won’t even notice it.

This kind of error is not supposed to happen. As soon as the plugin is deactivated, all additional markups generated by the plugin as disabled, too. So your browser is not supposed to know anything about a file called manifest.json. This might be a caching issue: the plugin is disabled, but when you visit your site, you still get the previous version of the page, still referencing a file that’s not here anymore.

When I visit https://www.kai-abresch.de/, I don’t get this error. Maybe you changed something in the meantime, or, in case of caching, the issue solved itself?

What is the behavior on your side?

Best Regards,
Philippe

Hi,

I’m sorry for the inconvenience.

I have never been reported this kind of issue, so I’m not sure how to investigate it.

Did you deactivate the plugin? If so, did it solve the issue?

Regards,
Philippe