最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

security - File permissions for wp-minify plugin

matteradmin6PV0评论

I am worried on installing Wp-Minify plugin. But it needs 777 permission for the cache directory located inside wp-uploads directory. Isn't it a security issue?

I am worried on installing Wp-Minify plugin. But it needs 777 permission for the cache directory located inside wp-uploads directory. Isn't it a security issue?

Share Improve this question edited Dec 29, 2012 at 10:45 fuxia 107k39 gold badges255 silver badges459 bronze badges asked Dec 29, 2012 at 9:57 jamesjames 1
Add a comment  | 

2 Answers 2

Reset to default 0

toscho is right. So you could probably give a try to another plugin. The Better Wordpress Minify.

This one also uses a folder inside the plugin's folder, BUT. You can change the folder and place it elsewhere. Please have a look at Advanced Customization. screenshot http://s.wordpress/extend/plugins/bwp-minify/screenshot-1.gif

We have been using it without a problem.

It doesn’t need 777. The author recommends it, but you don’t have to follow that. The usual file permissions should be good.

The real problem: the plugin wants to write into its own plugin directory.

var $cache_location = 'wp-content/plugins/wp-minify/cache/';

This is bad. After each update, the whole cache will be gone, and if you don’t allow write access to the plugin directory by default, the plugin will just not work.

And a hard codet wp-content directory is a rather bold assumption. It should use the constant WP_CONTENT_DIR, because the real name and path of that directory is configurable.

Articles related to this article

Post a comment

comment list (0)

  1. No comments so far