sadhaka

Thanks for that info but it was my mistaken configuration. I’d set it to not allow tweeting of old posts but I’d forgotten that whilst trying to tweet an old post! Duh!

Does anyone know anything about this – is it most likely a misreporting fault with “yslow” or is this a known W3TC issue?

I find you can also exclude further pages of the category by (e.g.):
category/books/page/2

WordPress stores the title tag and the alt tag, and the caption is proprietary, being <p class="wp-caption-text">

@kelek – Your suggestion works! To hide a widget from my category “books” I type in the “or target by URL” box:

category/books

… without leading or trailing slashes – and the widget in question now does not show in that category!

I thought I’d tried every combination, but obviously I missed that one. Thanks!

No, I haven’t found a solution as yet with my WP 3.4.2 installation. I’ve tried every way of entering the path, but nothing works. It’s a pity because if it wasn’t for this bug it would be an extremely useful plugin.

If the “target by URL” ever did work, then you would have thought that the code could be brought up to date.

I missed the configurable options, but the plugin does not rebuild the sitemap when a new post is published. Also, it includes images which are not in the current published post, but which are part of older revisions and so on.

Also needs something like:

$string = utf8_encode($string);
$string = htmlspecialchars($string);

Brilliant. Thanks.

So sorry – I’ve posted this in the wrong place !! Apologies! This comment was meant for a different plugin!

I should have mentioned that I’m not using a CDN. Any reason why YSLOW gives me this message? I’ve enabled “Set expires header” for all options.

Hmm, OK. I am using W3TC and CloudFlare … but the CloudFlare kb states, “Should I still install the CloudFlare WordPress plugin? — We still recommend installing the CloudFlare WordPress Plugin.”

Thanks for that info.

Some options were in fact enabled by default, such as Page Cache and Browser cache.

However, this is the (slightly redacted) output of the compatibility check – what options can I expect to enable with this environment? –

Server Modules & Resources:

Plugin Version: 0.9.2.4
PHP Version: 5.2.17 (PHP5 required for Minify, Rackspace CloudFiles, Microsoft Azure support)
Web Server: Apache
FTP functions: Installed (required for Self-hosted (FTP) CDN support)
Multibyte String support: Installed (required for Rackspace Cloud Files support)
cURL extension: Installed (required for Amazon S3, Amazon CloudFront, Rackspace CloudFiles support)
zlib extension: Installed (required for compression support)
Opcode cache: Not installed
Memcache extension: Not installed
HTML Tidy extension: Not installed (required for HTML Tidy minifier suppport)
Mime type detection: Installed (Fileinfo) (required for CDN support)
Hash function: Installed (hash) (required for NetDNA purge support)
Safe mode: Off
Open basedir: Off
zlib output compression: Off
set_time_limit: Available
mod_deflate: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_env: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_expires: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_headers: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_mime: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_rewrite: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
mod_setenvif: Not detected (required for Page Cache (enhanced mode) and Browser Cache)
WordPress Resources

/path/mysite.com/.htaccess: OK
/path/mysite.com/wordpress/wp-content: OK
/path/mysite.com/wordpress/wp-content/uploads/2012/09: OK
Fancy permalinks: /%postname%/
WP_CACHE define: Defined (true)
URL rewrite: Enabled
Network mode: No

@damoncloudflare – You wrote, “If you’re making changes to the static content we cache, then you would want to go to Development Mode first.”

.. so presumably this includes modifying existing blog posts (images etc) but not simply making new blog posts?

Well if anyone would like to know I found a solution here