crashnet

It seems the plugin itself excludes the /wp-content/cache/* files.

Bump.

I don’t know how to do that, but

– make sure to serve the main URL from HTTP so you don’t get mixed content warnings OR

– you could just get free SSL certs from LetsEncrypt for your CDN names and be done with it.

• This reply was modified 7 years, 11 months ago by crashnet.
• This reply was modified 7 years, 11 months ago by crashnet.
• This reply was modified 7 years, 11 months ago by crashnet.

Thanks nigro.

I don’t think the wildcard will work when setup that way. I tried something similar for blacklisting /wp-admin/ and ended up having to use

/home/*/public_html/wp-admin/*

also, are you sure the cache files are supposed to be blacklisted? there isn’t one single mention of this on google:

https://www.google.com/search?q=opcode+blacklist+"%2Fwp-content%2Fcache%2F"

(couldn’t get this link to work)

• This reply was modified 7 years, 11 months ago by crashnet.
• This reply was modified 7 years, 11 months ago by crashnet.
• This reply was modified 7 years, 11 months ago by crashnet.
• This reply was modified 7 years, 11 months ago by crashnet.

I’m also looking to add custom fields to SendPress. I’d purchase a pro version if I could do this right now.

Thanks

This question has a bounty of 50 points on SE https://wordpress.stackexchange.com/questions/135525/

Thanks Dion.

I want to get pt_BR with pt_BR in the admin!

Done.

Richard, I have protection against fake bots: the first time an IP shows up identifying itself as a bot, my system checks, via reverse DNS, if that IP is legitimate for the UA it claims. So we can rule that out, in my case.

I think there’s a typo in your reply, as it seems to contradict itself: “but not from MSNbot or Google” followed by “the problem is on Bingbot’s and MSNbot”.

Either way, for the last 7 days, I had 149 hits to ‘?share=*’ from Bingbot and 49 from MSNbot.

There were no hits from Google.

Hope this helps. I am happy to give you access to the logs.

Richard, below are my logs showing the ?share=* links being followed by MSNbot.

Nov 08 05:29:03 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:00 +0000] "GET /blog/slide/slide-3/?share=google-plus-1 HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:14 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:11 +0000] "GET /blog/slide/slide-3/?share=twitter HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:24 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:15 +0000] "GET /blog/slide/slide-3/?share=email HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:24 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:19 +0000] "GET /blog/slide/slide-3/?share=facebook HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:34 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:22 +0000] "GET /blog/slide/slide-two/ HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:34 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:26 +0000] "GET /blog/slide/slide-two/?share=email HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:34 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:29 +0000] "GET /blog/slide/slide-two/?share=google-plus-1 HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:44 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:34 +0000] "GET /blog/slide/slide-two/?share=twitter HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:44 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:37 +0000] "GET /blog/slide/slide-two/?share=facebook HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:44 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:41 +0000] "GET /blog/slide/slide-one/ HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:54 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:44 +0000] "GET /blog/slide/slide-one/?share=email HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:54 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:47 +0000] "GET /blog/slide/slide-one/?share=google-plus-1 HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:29:54 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:50 +0000] "GET /blog/slide/slide-one/?share=twitter HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"
Nov 08 05:30:04 MYHOST www-access-mydomain.com: msnbot-65-55-213-70.search.msn.com - - [08/Nov/2013:05:29:53 +0000] "GET /blog/slide/slide-one/?share=facebook HTTP/1.1" 404 3973 "-" "msnbot/2.0b (+https://search.msn.com/msnbot.htm)"

I disabled Minify months ago because the problem would not get fixed, version after version of W3TC. About month ago, I re-enabled it and the problem persisted.

So i disabled minify, but now I am getting the “error occurred while creating the minify cache” emails, with **MINIFY DISABLED**, even after emptying the page cache.

There are so many threads on this topic around the web that it becomes hard to find help for your version/situation

So how do I make these errors go away? I don’t even care if I use minify at this point – I will leave it disabled.

WP 3.7.1
W3TC 0.9.3

hehehe sorry! just trying to help… imagined you would be too swamped to post back here.

Will be fixed in the next version. See issue at github.

It doesn’t affect the performance of the plugin. The function is only called when you update plugins/themes/core and it checks whether you updated the current theme and if so, re-checks whether the theme has a <meta description> tag. Nothing major. (via jnfnl)

Will be fixed in the next version. See issue at github.

It doesn’t affect the performance of the plugin. The function is only called when you update plugins/themes/core and it checks whether you updated the current theme and if so, re-checks whether the theme has a <meta description> tag. Nothing major. (via jnfnl)