brohism

I found this script: https://livebookmark.net/journal/2008/05/21/memcachephp-stats-like-apcphp/

Does $key stay constant for a given site once W3TC is installed? In other words, can I hard-code it into my Nginx site config once I find its value?

Any tips here? Where can I find the memcached key?

The plugin still does not appear to be reading the Reply-To header. I have the value of Reply-To set to headers in the options. I’m using Contact Form 7, and I’ve set Reply-To in the additional headers field of my form, but no Reply-To address comes through on the sent message.

It may help if those experiencing the issue can post details about their server environment. What web server and version are you using (Apache, NginX, etc.). What version of PHP? Perhaps also include your rewrite rules.

I’ve been getting this error too. Barry’s solution fixed it for me. Would be nice to see this corrected in the next release.

It would be nice to have an option for the plugin to rewrite all uploads, or just ones added since the plugin’s activation. I’ve gone back and uploaded all my wp-content/uploads files to S3 exactly as they are on my web server, so allowing this plugin to rewrite those as well would be very helpful.

This problem just started for me today when I updated to the new version of W3TC. I removed Lazy Load files from CDN, but it didn’t make a difference.

If implemented so that every liveblog tweet that’s sent links back to either the liveblog parent post, or the individual liveblog update, it should still generate sufficient traffic.

Don,

I turned off SSL on my site a few months back but I’ve enabled it again and re-discovered this issue. I recall you mentioned having a test version (I currently have 4.2.3 installed) that would fix the issue. Any word on this?

@balwinder Singh,

I don’t see the location ‘sitemap-tax-post_tag.xml’ listed in ‘sitemap.xml’ which leads me to believe XML Sitemaps isn’t configured to enable this feed. I’d recommend checking your plugin settings to ensure that tag feeds are enabled. Every single one of the feeds listed in ‘sitemap.xml’ that I tried worked properly.

@balwinder Singh,

It appears to be working fine. I’m getting no error when loading your sitemap.

I found a fix for those still having this issue. Nginx needs to be told to pass requests for sitemap.xml to WordPress for handling, rather than try to serve a static file. Here’s what I added inside the Nginx server config:

location ~* ^(/sitemap).*(\.xml)$ {
  rewrite ^ /index.php;
}

It’s working perfectly for me now.

Perhaps users could have the option of setting the size of the watermark for each different type of image size available in WordPress?

Version 2.0.3 appears to have fixed the issue, and all is working properly. Thanks!