Odd issue with editing posts

I’ve had no success with working this problem out and it is VERY frustrating. I have tried not using the visual rich text editor but it makes no difference. Edits are not being saved on opening the Write page in Admin. (I can see the previous changes on the preview screen though)

I use Firefox and the plugins include fuzzy recent comments/ posts/ sk2 / contatct form /static front page / smart archives and exec php

I hope this extra info will be useful, since i would really like to resolve the problem

Disable the WordPress cache and give it a try. (See the wp-settings.php file, search for disable and comment it out per the comment in the file). – Trip

The cache is disabled by default isn’t it?

I discovered that I can fix the problem by setting the WP content cache folder to CHMOD 655.

When I do this, posts save OK. I do however get a multitude of error messages from the semiologic plugins when I try to delete a post – although the post does get deleted and the blog seems to be OK.

e.g of error:
Warning: is_file(): Stat failed for /homepages/7/d88945627/htdocs/digitalgeography.co.uk/wp-content/cache/c4ca4238a0b923820dcc509a6f75849b (errno=13 – Permission denied) in /homepages/7/d88945627/htdocs/digitalgeography.co.uk/wp-content/plugins/sem-recent-comments.php on line 136

also:
Warning: Cannot modify header information – headers already sent by (output started at /homepages/7/d88945627/htdocs/digitalgeography.co.uk/wp-content/plugins/sem-recent-comments.php:136) in /homepages/7/d88945627/htdocs/digitalgeography.co.uk/wp-admin/post.php on line 151

Can anyone account for this?

The comments say the cache is disabled by default but that is not the case. They ship it enabled. You can change the settings and return the file permissions and everything should be ok.

You should delete everything in the cache directory after you disable the cache (backup if you are worried but it doesn’t appear to affect anything adversely).

You can tell right away as WP shouldn’t write anything to the directory if the cache is disabled.

I have also found that I can re-enable the cache once the contents have been deleted and things work fine for a while but I can’t see any advantage of using the cache in its current state.

The cache needs to be reworked so that it only caches client side requests. It should not cache admin functions such as editing and categories. – Trip

Thanks Trip.
I appreciate that the wp cache is causing the problem. I tried deleting the contents of the file, but it is still being written to.

Just to be clear, how exactly should I change the following lines so that the cache is disabled?:

// For now, disable persistent caching by default. To enable, comment out
// the following line.
//define(‘DISABLE_CACHE’, true);

wp_cache_init();

You should uncomment the define line.

// For now, disable persistent caching by default. To enable, comment out
// the following line.
define(‘DISABLE_CACHE’, true);

Deleting the contents of the cache will not work unless you actually trun it off. ls -a might show hidden files.

The comment in the wp-settings file is misleading. – trip

It worked – thanks very much!