W3 Total Cache breaks fonts and Charset

I Have been having problems and my fonts appear to be broken also.There was just an update of the plugin today, so hopefully that will make a difference. Were you using Google font?

Hello,

The W3 Total Cache is writing the rules in .htaccess just fine. There might be a chance that your .htaccess got corrupted somehow.
Try to back up the current .htaccess and see if WP and W3 Total Cache will write the rules in the new .htaccess

You mean, I should backup the current htaccess and then delete the htaccess completly? Do I have to create a new “empty” one or will WP and W3 Total Cache create a new one automatically? I added some lines to the htaccess which were necessary (security, rewrites etc.), but not in the last months or so.

PS: I deleted the htaccess file, deactivated W3 Total Cache and activated it again: No htaccess was created. Then I created a new htaccess file with nothing in it, deactivated and activated W3 Total Cache. No change. I just get the message “The required directives for fancy permalinks could not be detected, please confirm they are available” above the WP admin area.

Usually W3 Total Cache should write some lines into the htaccess, right? Now the htaccess is empty, permissions are (as usual) set to 640 (I also tried 644, but it did not change anything).

I added the following lines to the htaccess, but it did not help (but the message above disappeared):

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

———-
UPDATE:
I followed some steps to test if WP is able to create or write into the htaccess and it was successful. I deleted the htacess, saved (without changes) the permalinks settings of WP and the new htaccess was created. I then uploaded my saved htaccess and changed the code of the # BEGIN WordPress section (changed index.php to example.php), then saved the permalinks settings again and this wrong “example.php” was correctly changed to index.php again.

But whenever I deactivate or activate W3 Total Cache or save the settings etc., not any lines of code get save into the htaccess by W3 Total Cache – regardless if I am using my old htaccess file or the new one which gets created if I delete the htaccess file, save permalinks settings, so that WP created a new htaccess. W3 Total Cache never updates the htaccess in any way.

What to do?

• This reply was modified 6 years, 1 month ago by dajanas.
• This reply was modified 6 years, 1 month ago by dajanas.
• This reply was modified 6 years, 1 month ago by dajanas.

Unfortunately, I still haven’t found a solution. W3 Total Cache does not update the Htaccess file at all (as described in detail above).

There must be a solution?

Nothing?

Wow.

Hello @dajanas,
Sorry for the delay, we can not do 24/7. We are looking into this. Trying to replicate the issue, but we are unable so far. Can you please check what is your file permission for .htaccess?
This is a very strange issue. W3 Total cache should not have any problems writing the rules in .htaccess. Try to disable any other plugin as there might be some conflict. Maybe for some odd reason, something is preventing W3 Total Cache to write the rules that are related to any other plugin you have installed or your server configuration.

Hello,

thank you very much for your answer. I set the permissions with 644, but I also tried 640 and tested on 777 (just to see if it works then). I’ve disabled and tested several plugins, but W3 Total Cache still doesn’t write to htaccess. After your message I suspected that maybe Yoast SEO could cause problems, but even after deactivating this plugin W3 Total Cache still couldn’t write to htaccess.

Is it possible to insert a kind of “test button” into W3 Total Cache, with which it is clearly recognizable whether htaccess can be written? So not only a check of the rights, but a real test where the htaccess is written to?

…

… hello again?

Hello,
Unfortunately, we could not reproduce your issue. No matter what we do We Total Cache always writes the rules to .htaccess.
The only thing that I can advise is to try to restart apache server or I can offer you our professional support to investigate compatibility issue.

What’s the matter with you guys? Why was this thread marked as “solved”? The problem was not solved in any way! The problem still exists, there was no help, W3 Total Cache still doesn’t write to .htaccess. It is incredible and cheeky that this post was simply marked as “solved”!!!

PS: Maybe it helps to REALLY solve this problem. My htaccess shows for example this line in terms of W3 Total Cache:

Header set X-Powered-By "W3 Total Cache/0.9.2.11"

So obviously 0.9.2.11 was the last working version in terms of htaccess. Maybe that helps as a hint?

• This reply was modified 6 years ago by dajanas.

Hello @dajanas,
The post was mar as resolved due to the inactivity please check our “Read before posting” sticky post.
I advised you to try to restart the apache server and offered you our Professional support to investigate compatibility issue.

Restart did not help at all and I am not able to pay professional support unfortunately. I now deactivated W3 Total Cache AND deinstalled it. What is strange: The website is still “cached” and tries to load the minified files from W3 Total Cache. Which makes no sense, all of that should disappear after deactivation and deinstallation of W3 Total Cache. And still all old entries in the htaccess are still there. There must be a reason for all that.

I have finally found a solution and it also confirms that it is 100% a problem of W3 Total Cache.:

W3TC does NOT automatically delete the “wp-content/cache” and “wp-content/w3tc-config” folders when it is uninstalled – but it should! Uninstalling means uninstalling, everything from the plugin should be removed completely!

The following steps solved my problem – unfortunately the support of W3 Total Cache in this forum couldn’t help me, so I had to try it out myself.

1) DO NOT use the export options of your W3TC settings. This function does not work reliably. Instead take screenshots of every single settings page, note down all settings, possibly copy entries into text files – in short: Save everything MANUALLY.

2) Purge all caches.

3) Disable all W3TC cache options (in the “General Settings”, so disable Page Cache, Minify, Databace Cache, Object Cache, etc.)!

4) Deactivate and delete the W3 Total Cache plugin.

5) Delete the “wp-content/cache” and “wp-content/w3tc-config” folders that still exist (but should not) despite uninstalling.

6) Check your .htaccess file and make a backup copy of it. If there are still W3TC entries (like in my case), remove them completely.

7) Install the current version of W3 Total Cache, activate it and reset all the settings you have saved in the form of screenshots or notes. This way you have restored all settings and you should also see that your .htaccess file has been updated (easy to recognize by the changed file size – when you open the file you will also see the added lines from W3 Total Cache).

Sometime in the past there must have been some problem with a version change, so that the saved settings of W3 Total Cache didn’t work properly with the newer versions of the plugin anymore and also the update of the .htaccess wasn’t possible anymore. Only the clean and complete removal of the plugin and the manual recovery of all settings solved the problem – normally when removing a plugin the plugin should remove all settings, files and folders associated with the plugin. This is the meaning of “Remove”.

Through the above mentioned steps it now works for me again.

• This reply was modified 6 years ago by dajanas.