WordPress update not compile to your plugin

?????????????????????
please?
is kind of emergency.
I need to know if is possible to put your code outside the WordPress index.php…
is a problem when WordPress does an update.

please hurry is an emergency, the site gets 404 now.

Please I believe to a lot of people have the same issue,
is lead to 404 especially now when WordPress do a lot of changes and update his core.
any time WordPress do a core update.
he rewrites his core code inside the htacsses…

Your code lost in the shadows… you needed to think about that is irresponsible,
you couse to a lot of people 404 errors.

please answer if I can put your code outside the WordPress core code inside the htaccsess.
please is an emergency.

???????? plugin abonded?

@phbernard ????????????????????????????????????????????????????????????????????

I understand your plugin is abounded?

Hello,

The plugin is still supported! I’ve just made sure it works well with the latest WordPress release (5.7.1).

Unfortunately, I cannot reproduce your issue.

The changes in the .htaccess file is done through WordPress itself, so if is suppose to be correct. What is the URL which causes a 404 error? What makes you think Favicon by RealFaviconGenerator is involved? Did you try to disable the plugin?

Regards,
Philippe

come on bro.
Your code sit exactly inside AND split the WordPress core code:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteRule ^android-chrome-192x192\.png /wp-content/uploads/fbrfg/android-chrome-192x192.png [QSA,L]
RewriteRule ^android-chrome-512x512\.png /wp-content/uploads/fbrfg/android-chrome-512x512.png [QSA,L]
RewriteRule ^apple-touch-icon\.png /wp-content/uploads/fbrfg/apple-touch-icon.png [QSA,L]
RewriteRule ^browserconfig\.xml /wp-content/uploads/fbrfg/browserconfig.xml [QSA,L]
RewriteRule ^favicon-16x16\.png /wp-content/uploads/fbrfg/favicon-16x16.png [QSA,L]
RewriteRule ^favicon-32x32\.png /wp-content/uploads/fbrfg/favicon-32x32.png [QSA,L]
RewriteRule ^favicon\.ico /wp-content/uploads/fbrfg/favicon.ico [QSA,L]
RewriteRule ^mstile-150x150\.png /wp-content/uploads/fbrfg/mstile-150x150.png [QSA,L]
RewriteRule ^safari-pinned-tab\.svg /wp-content/uploads/fbrfg/safari-pinned-tab.svg [QSA,L]
RewriteRule ^site\.webmanifest /wp-content/uploads/fbrfg/site.webmanifest [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

as you see, all the [QSA,L] ending.

is from your plugin…
now, when have an updated core, let’s say WordPress 5.5 to WordPress 5.6

your code is gone, now you get it?
now is the FAVICON get 404 because your code is gone:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

the only solution for that is to put your code, [QSA,L].

Outside the WordPress core code.
as i said in my first message.

I hope is helpful to understand the issue.

the only thing i need to know is if i can to put your code separately.
above the WordPress core code, is should look like this:

# your code favicon
RewriteRule ^android-chrome-192x192\.png /wp-content/uploads/fbrfg/android-chrome-192x192.png [QSA,L]
RewriteRule ^android-chrome-512x512\.png /wp-content/uploads/fbrfg/android-chrome-512x512.png [QSA,L]
RewriteRule ^apple-touch-icon\.png /wp-content/uploads/fbrfg/apple-touch-icon.png [QSA,L]
RewriteRule ^browserconfig\.xml /wp-content/uploads/fbrfg/browserconfig.xml [QSA,L]
RewriteRule ^favicon-16x16\.png /wp-content/uploads/fbrfg/favicon-16x16.png [QSA,L]
RewriteRule ^favicon-32x32\.png /wp-content/uploads/fbrfg/favicon-32x32.png [QSA,L]
RewriteRule ^favicon\.ico /wp-content/uploads/fbrfg/favicon.ico [QSA,L]
RewriteRule ^mstile-150x150\.png /wp-content/uploads/fbrfg/mstile-150x150.png [QSA,L]
RewriteRule ^safari-pinned-tab\.svg /wp-content/uploads/fbrfg/safari-pinned-tab.svg [QSA,L]
RewriteRule ^site\.webmanifest /wp-content/uploads/fbrfg/site.webmanifest [QSA,L]

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

tell me if is ok please.

Hi,

Oh, ok. I didn’t realize the redirections were gone in your initial copy of htaccess.

TL; DR

There is nothing wrong here. You can safely ignore this issue. DON’T edit the htaccess file, this is error prone.

In details

The plugin adds redirections to htaccess in order to satisfy two conventions:

• /favicon.ico

This is what most browsers look for when no favicon is declared in the HTML.

• /apple-touch-icon.png

(and friends) iOS Safari is looking for this when none is declared.

However, the plugin makes sure your icons are declared in your site pages. Therefore, these conventions are enforced only to make your favicon bulletproof, and also to save you from annoying (and harmless) 404 errors in your logs. But they still work: your visitors will see your favicon, whatever the browser or device. You might imagine some super-remote scenario, such as a visitor using an old version of Internet Explorer, stuff like this… Even in that case, the favicon should still work.

Plus, some settings prevent htaccess from being updated. It depends of the hosting provider, etc. So the plugin is designed to handle this scenario gracefully. What you get here is not considered as an error by the plugin, only a fallback which occurs very often.

Why this fails after a WP update is a mystery, but this issue is definitely too minor to be seriously investigated.

I hope this clears your doubts.

Regards,
Philippe

I didn’t get you, bro…

in simple language, past the code, I need to copy, I didn’t get your explanation.
and I need the exact code.

btw,
if someone has this inside his htacsses, so the same client must fix it manually!
is not minor bro, is big.
any WordPress update your code is gone.
is not minor, it can be a big problem.

please if you can correct your code here and past me what I actually need to do
as you see in my examples on this topic.

Sorry, bro, I didn’t get you with this
explanation and this be must adjustment

please past here me what I need to do.
and I will copy that to my htacsses
(please put the exact code outside the WordPress core code).

Thanks ??

Hi,

I’m sorry if my answer was not clear. Let me rephrase.

The lines added by the plugin in .htaccess are 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 .htaccess is tricky and can easily disrupts your site if anything goes wrong.

You usually shouldn’t edit your .htaccess file 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

perfect ?? thanks ??

You’re welcome!