Andrew Biss

Works OK in version _1.13.1_beta from github.

Works OK in version _1.13.1_beta from github.

Added as a reply by mistake. Sorry!

I can also confirm that version 2.2.2 fixes the problem with the “Empty Spam” or “Empty Trash” buttons I noticed with 2.2.1.

I noticed the same error message appears when I moderate comments and use the “Empty Spam” or “Empty Trash” buttons.

Regenerate Thumbnails version 2.2.0 was working OK with WordPress 3.3 but is broken by the update to version 2.2.1.

Thanks for the solution Adam.

I use the WPSEO title() and metadesc() methods in some validation code I added to my theme. Instansiating the WPSEO_Frontend class as you suggested fixed the problem.

Latest version works OK when WordPress is installed in a sub-directory. Thanks for quick fix.

Fixed OK in version 0.2.3

i’ll try to comment out the code that builds the Column in the Posts/Pages cause it breaks my screen with long titles…but i think that an option to activate or disable the WP SEO columns is needed.

To hide the “WP SEO Title” and “Robots Meta” column in the Manage Pages and Manage Posts lists just click on “Screen Options” in the top right corner of the page and deselect these columns. You don’t need to make any code changes in the plugin.

To get back the original WordPress format just click on the “Screen Options” link at the top right of the “Posts” page and disable the checkbox against “WP SEO Title” and “Robots Meta”.

I see from the HTML your minified CSS is in /wp-content/w3tc/min/thesis_17/thesis_17/default.include.4223048014.css whereas mine is in /wordpress/wp-content/w3tc/min/thesis_17/thesis_17/default.include.0.css.

The first difference is that you have WordPress installed in the root directory and I have WordPress in a sub-directory, but that looks OK.

The more interesting difference is you have 4223048014 in the CSS file name, whereas I have 0 in my CSS file name (and that file is not being generated).

I have double checked permissions of my CSS files and all permissions and ownerships look good.

Next step is to have a look at the W3TC code to see what this number represents (a timestamp?) and whether that gives any insight into where the problem is.

The W3TC development version as at 23rd June.

I installed the W3TC development build before updating to WordPress 3.0.

@gregrickaby,

Thanks for your comments about CSS and Thesis.

My understanding of how Thesis works with the CSS files is a little different, so I had a quick look at the theme source to see what it is really doing.

When you change the design options using the Admin panels then Thesis saves this information into the database and writes the layout.css file to disk using function thesis_generate_css(). This disk file is only updated when you make changes via the Admin panels (which seems reasonable).

It should be possible to minify and combine the generated Thesis CSS files along with a local custom.css override file using W3TC. I was combining and minifying my CSS without any problems using W3TC, WordPress 2.9.2 and Thesis 1.7.

Where the confusion might arise is that Thesis dynamically rebuilds the CSS objects in memory for each page as it needs to calculate some information such as line heights or maximum image widths. Rather then reading and parsing this information from the on-disk CSS files, Thesis just rebuilds the in-memory objects from the database values.

Looking at the code, however, it does not seem that Thesis rebuilds the CSS files on disk for each page load. Again this seems reasonable and is also consistent with the use of cachebuster timestamps on the CSS files.

So I am not really any clearer on the source of my problem with W3TC and WordPress 3.0. At the moment it seems to me to be an issue with the change to W3TC for multi-suite support in WordPress 3.0, and not being due to the Thesis theme.

I will continue to investigate and see if I can see what is going on and why the combined CSS file default.include.0.css is not being created by W3TC.

Yes, I have the WordPress 3.0 installation in https://mydomain.com/wordpress/ and just the index.php file in the root directory.

This was the setup when I was using WordPress 2.9.2 and earlier versions and these worked OK with W3TC.

I download the latest W3TC development version yesterday to see if that resolved the problem, but no luck. The minified CSS file was still not being generated correctly.