davidlyness

Hey, great idea! The plugin’s home page already has a couple of examples, but I’ll add some more which include special characters.

As for your specific example – although the double-quotes character itself shouldn’t interfere with pattern matching (it’s not a special character in regex world), it’s likely that some other character in your pattern is. Are you able to share the full line you’re trying to remove?

OK, so it looks like WP Super Cache wasn’t the only cause of this problem. If you can provide the following information we can try to work out what else may be causing you to experience this issue.

1. Do you have any other plugins that affect the content of pages served to users? If you’re not sure, feel free to list the other plugins you’re using.
2. Can you give some detail on 1) the strings you wish to filter out of your HTML, and 2) the regular expression(s) you’ve defined that should remove them?

Thanks!

David

Thanks for the bug report! This behaviour looks like it was caused by a recent change in WP Super Cache’s functionality that caused it to cache the unmodified version of the page, rather than the modified version.

I’ve just pushed a new version of HTML Cleanup (v1.2.4) which should fix the issue – I checked with WP Super Cache’s default settings on a test website and it worked for me. (It may take a few minutes for the updated version to appear in your plugin list. Alternatively, you can uninstall / reinstall HTML Cleanup to get the latest version immediately.)

Please let me know if this fixes your problem!

David

Hey Angristan,

It’s David, the plugin author here. Hundreds of people use this plugin without issue, so hopefully we can get it working for you! Can you describe what you’re trying to do, the issue you’re facing, and how you’ve configured the HTML Cleanup plugin?

Hey Shane,

The HTML Cleanup plugin removes / modifies HTML across the entire page, not just within user-generated posts. It also works at the level of lines of HTML, rather than working on strings (like HTML tags) within lines of HTML which is what you’re looking for.

From a quick search of the Plugins directory, the Post Content Cleaner plugin may do what you need.

Thanks for the bug report! I’ve pushed v1.2.3 to the plugin repository that should fix this issue – feel free to reopen this thread if you’re still having this problem with the new version.

I fixed the problem by changing the contents of the .htaccess file to the following:

Options -Indexes

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/(tech)/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /tech/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /tech/index.php [L]
</IfModule>

# END WordPress

The permissions on the file are 644, group and owner both myuserid.

I tried the steps you suggested, but the same problem keeps happening. It’s not always the same file in that ‘fails’ the upgrade – for example, just now I got “Could not copy file: /public_html/wordpress/wp-content/upgrade/wordpress-2.8.5/wordpress/wp-admin/includes/taxonomy.php”.

Hi,

I tried what tomazl suggested – I backed up my original installation, and then copied all the files to my local machine, and then back to the web server. This changed the group to my user ID. I attempted to perform the upgrade, but I ran into the same error.

I then tried changing every file in the directory to have permissions 777, but the upgrade failed again, with the same error.

As an extra note, a plugin upgrade is failing too – Google Reader Shared is attempting to upgrade to v4.0.1, but I’m fairly sure it’s not a problem with this particular plugin, as the built-in WordPress upgrade feature doesn’t seem to be working either.

The file is there in the upgrade folder.

The WordPress files are owned by my user ID, but they’re in the ‘nobody’ group (apart form the upgrade folder, which is both owned by me and in the group ‘myuserid’). As far as I can tell from the URL you provided, my permissions are correct – I could not find the cgi-bin folder on my server though, I suspect the hosting provider keeps those files somewhere else.

Bump.

I tried the steps you suggested, but the problem still seems to persist.