atdblog

Thanks for the heads-up on 6G. I didn’t realize that existed. The 2014 Micro Blacklist is two years newer than the 6G Beta, which is odd. I’ll have to go through the comments after that post – I see on the first page that some had issues with the code. However, I wasn’t aware that the blank user agent block was an issue so I updated my htaccess and my post and text file.

Thanks!

See https://www.allthingsdemocrat.com/htaccess-security-and-the-largest-block-bots-list-on-the-web/ ??

I confirmed it, w3tc is not writing the browser caching rules to my htaccess in the root or the htaccess in the cache/page_enhanced directory. However, the rules are correct when displayed in the Install tab so I just pasted the rules into my htaccess and now all is correct. Raised my GTMetrix YSlow score from 82 to 92 and added 10 points overall to Pingdom now that it specifies a cache validator.

My htaccess files have 644 permissions. Is that correct?

Update: I saw that the w3tc Rewrite Rules I expected was listed in the Install tab so I pasted that into my htaccess file and uploaded it. But shouldn’t that have written to the file on its own? I even tried removing everything from the file, uploading it, and saving a randomn change in W3TC but it only save the page caching code (yes, browser caching was selected). Anyway, it seems to be working now.

See if my settings help you – see https://www.allthingsdemocrat.com/w3-total-cache-cookieless-subdomain-godaddy-shared-hosting/. Skip down to “Installing and Configuring W3-Total-Cache”. Tip: You can use the print button to delete everything else and just print those instructions. Also, many recommend not using Database Caching with shared/web hosting.

Update: Godaddy’s tech support refused to help, blamed it on WordPress “using more memory than is allowed” (yeah, I’ve had this WP blog since 2006 and now its suddenly a problem?). I saw in another post that GD tech support whitelisted her IP and it resolved the issue. I told them that but they refused to consider it. So after 8 years I fired Godaddy and moved my site to Siteground. It tests better than Godaddy and I haven’t seen this issue since.

This explains a lot! Have been defending Godaddy for years but it looks like their security software is now way too conservative for WordPress blogs https://www.wpsitecare.com/performance-of-7-top-wordpress-hosting-companies-compared/

Actually, I had several deprecated functions in my non-WP dynamic pages that I don’t have time to rework so I guess I won’t be able to use Quick Cache. Any reason why you rewrote it to require 5.3? It worked great before (was just nervous about no support at the time).

I disabled all plugins and my blog was speedy again and after activating one at a time it appeared w3 total cache was the problem. But then I reactivated it and it was still speedy. A few hours later and its a dog again. ugh!

this title was supposed to be “Comments link NOT on first page of home page”. and it still happens frequently.

I deactivated the plugin, reactivated and got the update available message. Did the auto update and this time it worked.

Now it redirects from the home page to the single post and then closes properly from the single page. Did it do that redirect from the homepage before?

zignjny’s correct. I like having it on the homepage but this is a good, temporary solution.

See this page. Win7 PC, same behavior in latest versions of IE, Firefox, Chrome and Opera. Not trying to print, just closing the Print Friendly window and stuck in infinite loop.

But when opening Print Friendly though the “Share Buttons by AddToAny” plugin, it opens a new window and then displays Print Friendly, then I can close PrintFriendly (without printing) and it returns to the site page in the new window. Was the new window supposed to close?

Here’s something interesting – when I use the Print Friendly button via the “Share Buttons by AddToAny” plugin, Print Friendly does not have the same issue.

I prefer the visibility of your plugin’s button, so I’ll watch for the fix.