Title: Possible Bug: Missing Cache Validator for Fonts
Last modified: November 24, 2019
---
# Possible Bug: Missing Cache Validator for Fonts
* Resolved [dK](https://wordpress.org/support/users/dkristanda/)
* (@dkristanda)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/)
* Hi W3TC team,
Just found a possible bug.
* GT Metrix complain about missing cache validator on fonts file.
* It seems **Version 0.11.0** create a conflicting entry in .httaccess:
* snippet: “Group 1”:
* ```
FileETag MTime Size
Header set Pragma "public"
Header append Cache-Control "public"
Header unset Set-Cookie
Header set X-Powered-By "W3 Total Cache/0.11.0"
```
* and immediately followed by “Group 2”
* ```
FileETag None
Header unset ETag
Header unset Last-Modified
```
* “Group 1” is using “FileETag MTime Size” while “Group 2” is using “FileETag None”.
And it seems “Group 2” is a subset of “Group 1”. (Those group of code are the
last 2 FilesMatch block before mod_header)
* If I remember correctly, the previous version did have a similar second group
but only to remove the Last-Modified header (without “FileETag None” and “Header
unset ETag”)
* So, I remove those 2 commands (the one removing the Etag at 2nd group and all
good)
* Hopefully, it is just simple bug otherwise I am the one that might have some
conflicting setting 🙂
* If I did not change any setting W3TC will not recreate my .htaccess, right? please?
LOL….
* Awesome plugin. Internet will never be the same without W3TC!! Literally…
Thanks.
Cheers, Denis
Viewing 9 replies - 1 through 9 (of 9 total)
* Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* (@vmarko)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12171872)
* Hello [@dkristanda](https://wordpress.org/support/users/dkristanda/)
* Thank you for bringing this to our attention and I am happy to assist you with
this.
We’ve checked this and it appears that when compatibility mode is enabled
this may happen. Go to Performance>Page cache>Advanced and untick the compatibility
mode and see if the issue persists. Usually, the compatibility mode is not required
in modern hosting accounts. I’ve also created a ticket on your behalf in our
[Github](https://github.com/W3EDGE/w3-total-cache/issues/84) public repository
so you may check the progress there regularly.
* Thread Starter [dK](https://wordpress.org/support/users/dkristanda/)
* (@dkristanda)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12178972)
* Thanks for your reply and the github link
* I think what happen here is that the developer has removed the compatibility
mode but havent fully strip the code.
* The only checkbox in Page Cache Advance is “late initialization” and “late caching”
* Also the exact coding is repeated at the Browser Cache plugin. Might be useful
info for the developer if they want to strip it clean.
* Thanks again!
* Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* (@vmarko)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12181232)
* Hello [@dkristanda](https://wordpress.org/support/users/dkristanda/)
* Just to confirm, In Performance>Page Cache>Advanced section you are not seeing“
Compatibility mode”?
Can you please check this [image](https://i.ibb.co/KbdQLHL/Annotation-2019-11-27-145702.png)
and confirm that?
* Thread Starter [dK](https://wordpress.org/support/users/dkristanda/)
* (@dkristanda)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12185150)
* Yes, confirmed.. no pg cache compatibility.
* here is my screen capture
* > [View post on imgur.com](https://imgur.com/fK31h8C)
* weird?
* thanks!
Denis
* ps. I hv submit another bug I found – quite big one/obvious.. but on hold by
moderator due to lots of ‘dummy’ link as illustration. hope can be released soon..
if ever…
* Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* (@vmarko)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12185468)
* Hello [@dkristanda](https://wordpress.org/support/users/dkristanda/)
* Thanks for the information.
This is very strange. “Maximum lifetime of cache
objects:” should be located in Performance>Database cache. Here is the [screenshot](https://i.imgur.com/O8089fZ.png)
of the advanced sub-box of Performance>Page Cache (how it’s supposed to be).
Can you please share a similar screenshot?
* Thread Starter [dK](https://wordpress.org/support/users/dkristanda/)
* (@dkristanda)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12188982)
* Hmm…so I was denied 2 options… lol
* Here it is… [PageCache Advance box](https://i.imgur.com/qeK1WL7.jpg)
* Is it interference from another plugin?
The only thing that I installed related
to W3TC is the helper plugin to help me do the manual mode “W3TC Minify Helper
Version 1.0.0.1 By Magenta Cuda” which did help me get better js deferral. But
have tried to disable this plugin, no effect to the missing options.
* Thanks
Regards, Denis
* Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* (@vmarko)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12196572)
* Hello [@dkristanda](https://wordpress.org/support/users/dkristanda/)
* W3 Total Cache generates those rules only in compatibility mode.
The compatibility
mode option is shown only when disk-enhanced is used. What caching method are
you using? Maybe Memcached or Redis? If you have had Disk: Enhanced enabled and
then switched to something else there is a possibility that the Compatibility
mode was selected and now affects browser cache rules historically. Two things
that you can do potentially. You can switch back to Disk: Enhanced save all settings
and then disable compatibility mode, save all settings and purge caches. The
other thing that you can do is to manually remove W3TC rules from .htaccess and
leave the .htaccess only with WP default rules. This will allow W3 Total Cache
to write new set of rules to your .htaccess file. I hope this helps!
* Thread Starter [dK](https://wordpress.org/support/users/dkristanda/)
* (@dkristanda)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12200214)
* OK. That explained it.
Thanks heaps!
* Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* (@vmarko)
* [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12200589)
* Hello [@dkristanda](https://wordpress.org/support/users/dkristanda/)
You are
most welcome! We would really appreciate it if you could take a minute and post
a review [here](https://wordpress.org/support/plugin/w3-total-cache/reviews/).
This will help us to continue offering a top-notch product to users. Thank you
for your help!
Viewing 9 replies - 1 through 9 (of 9 total)
The topic ‘Possible Bug: Missing Cache Validator for Fonts’ is closed to new replies.
* 
* [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
* [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
* [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
* [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)
## Tags
* [cache-validator](https://wordpress.org/support/topic-tag/cache-validator/)
* 9 replies
* 2 participants
* Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
* Last activity: [6 years, 6 months ago](https://wordpress.org/support/topic/possible-bug-missing-cache-validator-for-fonts/#post-12200589)
* Status: resolved