wp-super-cache security issue (wp-content writable?)

fkranjce
(@fkranjce)

16 years, 9 months ago

Hi,

After many problems with CPU load of my server i’ve instaled wp-cache and it works great. CPU load is down and site works extra fast.

I have jsut two questions.

I’ve look cached html files and i see adsense script is intact so i guess it shoudl work fine and google wont have any problesm with cache.

Second is about security. Wp-cache require 777 permision on content folder and i am jsut wondering if it is possible to change that and keep wp-cache working. I dont feel safe with 777 permision on that folder.

Thank you for any help.

Viewing 10 replies - 1 through 10 (of 10 total)

dj-primat
(@dj-primat)

16 years, 6 months ago

+1

huckmag
(@huckmag)

16 years, 3 months ago

bump for this. I just got spam files added to my wp-content folder and I’m pretty sure it’s because of chmodding it to 777 for wp super cache.

Any help on this?

Moderator Samuel Wood (Otto)
(@otto42)

WordPress.org Admin

16 years, 3 months ago

The content folder does not need to be 777. The cache folder does.

huckmag
(@huckmag)

16 years, 3 months ago

If I set the wp-content folder to 755 then in the wordpress admin section the page for wp Super cache displays:

Error: wp-content directory (/hsphere/local/home/huckftp/huckmagazine.com/wordpress/wp-content) is not writable by the Web server.
Check its permissions.
Cannot continue… fix previous problems and retry.

Moderator Samuel Wood (Otto)
(@otto42)

WordPress.org Admin

16 years, 3 months ago

Well, that really sucks. Seems like an error in WP-Super-cache to me. It should not require that wp-content be writable, it should only require that the config file be writable (since that’s all it’s writing to).

huckmag
(@huckmag)

16 years, 3 months ago

I *think* it’s still caching OK but the admin is not available.
Mark
(@mindstar)

16 years, 3 months ago
Once you have WP_Super_Cache installed and operational, you can CHMOD wp-content back to 755 (to protect your plugins folder).

You will need to modify the wp-super-cache/wp-cache.php file to remove the check to see if wp-content is writable.

Comment out lines 723-726
```
if ( !is_writable($dir)) {
	echo "<b>Error:</b> wp-content directory (<b>$dir</b>) is not writable by the Web server.Check its permissions.";
			return false;
	}
```
huckmag
(@huckmag)

16 years, 3 months ago

The new version of Super Cache now displays the admin page even if you have wp-content at 755 but it is read only.

I now change it to 777 when I need to clear the cache or make changes in admin and change it back.

The new version is 0.5.4 and can be downloaded from
http://ocaoimh.ie/wp-super-cache/

Jer Clarke
(@jeremyclarke)

15 years, 11 months ago

I have to say: Still, WTF? The only file that needs to be edited to change the settings is wp-cache-config.php, so why should people change the permissions on both that AND wp-content when they want to change settings, rather than just wp-cache-config?

If Donncha is around, I’m interested to hear the reasoning, is there something we’re missing? I guess we should just learn to edit the wp-cache-config.php file manually?

myhelipad
(@myhelipad)

15 years, 9 months ago

I just install WP Super Cache 0.6.5 and running smooth but having warning when i check back on WP Super Cache Manager

Cache contents

Warning: Invalid argument supplied for foreach() in /home/xxxxxxx/public_html/wp-content/plugins/wp-super-cache/wp-cache.php on line 942

pls advice.

Regards