phbernard
Forum Replies Created
-
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] Chrome Console error after deactivationHello 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,
PhilippeForum: Plugins
In reply to: [Favicon by RealFaviconGenerator] Fixing 401 Error for site.webmanifest FileGreat! Thank you for letting me know.
Best Regards,
PhilippeForum: Plugins
In reply to: [Favicon by RealFaviconGenerator] Fixing 401 Error for site.webmanifest FileHi,
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 “Enablecrossorigin="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?
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] Chrome Console error after deactivationHello 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,
PhilippeForum: Reviews
In reply to: [Favicon by RealFaviconGenerator] Site won’t load after RealFavconGeneratorHi,
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,
PhilippeOkay I understand. Don’t hesitate to post again on this thread when the site goes live.
Hi,
The RealFaviconGenerator plugin leaves no trace of any favicon when it is deactivated. So if you still got a 404 while the plugin was off, this is probably because there was a favicon provided from another component. Most likely: from the theme you’re using.
I cannot see any favicon at https://www.milesadcox.com/. GTMetrix does report any 404 and I cannot spot any 404 error with Chrome. I suppose you deactivate the RealFaviconGenerator plugin and fixed your issue, whatever it was?
The problem now is that you don’t have any favicon. My advice is to activate the RealFaviconGenerator plugin again and run GTMetrix again.
Please let me know if I can help.
Regards,
PhilippeForum: Plugins
In reply to: [Favicon by RealFaviconGenerator] error 60: SSL certificate problem:Hey @hamiltonjunio
The plugin doesn’t call curl directly. Instead it calls
wp_remote_get, which in turns call curl… or anything your WP instance supports. Because of this,--insecureis not an option here.Well, the change I could perform on my server would be to change the certificate provider. In other words, drop Let’s encrypt for something else… and non-free, since, to my knowledge, Let’s encrypt is the only free solution around. I’m very reluctant to do such a move, and not only for the cost of a certificate. Let’s encrypt is a good solution, with certificate renewal, etc.
I know this is just a minor issue: you just have troubles with your favicon and there are plenty of other ways to get the job done. However, it might reveal a more troubling situation. Reading https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/, we can see the root cause of the issue: an outdated system. For example, your WordPress instance might run on a system with an outdated version of OpenSSL. This is why I’m asking for hosting providers and offers: this issue should be thoroughly investigated and the providers might have to be informed.
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] error 60: SSL certificate problem:Hi,
Despite of the message, the certificate did not expire. You can visit https://realfavicongenerator.net/ and check for yourself.
This is a client issue and the likely culprit is your hosting provider.
What you can do:
- Contact your hosting provider with a link to this issue and to https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
- Tell me the hosting provider you use and the offer you subscribed to. I will try to reach them personally.
FYI the issue was also reported here: https://github.com/RealFaviconGenerator/realfavicongenerator/issues/470
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] ALERT BLOGVAULT !!!!Back from vacation 🙂
The issue has been fixed in version 1.3.22.
The issue has been fixed in version 1.3.22.
Thank you all for your reports and patience!
The issue has been fixed in version 1.3.22.
Thank you all for your reports and patience!
Hi,
Thank you for reporting this security breach.
I’m currently on vacation and will investigate it in a week.
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] WordPress update not compile to your pluginYou’re welcome!
Forum: Plugins
In reply to: [Favicon by RealFaviconGenerator] WordPress update not compile to your pluginHi,
I’m sorry if my answer was not clear. Let me rephrase.
The lines added by the plugin in
.htaccessare completely optional, really. Even without then, your visitors will still see your favicon, which is exactly what you expect from this plugin.If you add the lines manually:
- You get (almost) no benefits, see my previous answer. Your favicon already works without those lines.
- You put your site at risk, since
.htaccessis tricky and can easily disrupts your site if anything goes wrong.
You usually shouldn’t edit your
.htaccessfile manually, unless you have a good reason to do so. This is not the case here.Again, the best thing to do here is to ignore this issue. You favicon works just as well.
Regards,
Philippe