Hello,this is Japanese Moderetation team, Yama and Nick(smallworld).
Today we have to announce some important problem about ’rss’ directory which is created by an installer within modxpath/assets/cache.
We tried an installation of modx-0963rc1 and 2 version, and both of them has a problem.
The directory of ’rss’ was owned by user "apache", and anyone who use shared server couldn’t delete this "rss" directory.
Some people couldn’t delete this "rss" directory and had to contact to the support center to delete them.
We found that this directory is generated by a "MagpieRSS" and it don’t concious about the permission of the directory they create.
So we strongly request to fix this problem. The "rss" directly should be reserved and created from initial package, and it should involve an index.html to protect the directory.
We think it needs to modify an installation program. The instalation program should check the directory’s permission.
Meanwhile, may the Japanese moderator have a permission to commit the program code to repositry?
If we could have an account that could commit to repositry, we could fix, modify and commit the program when we find the problems.
Please consider about it.
Anyway,please modify the "rss" directory problem.
Sincerely,
Yama and Nick8smallworld) from Japanese comunity
-
MODX Staff
- 10,725 Posts
You really should never need to manually delete this folder. This would be the same with any files being created in the assets/cache/ directory; all those things can be deleted from the manager. And this also only affects those using shared servers with mod_php (vs. a CGI method), which is becoming increasingly rare in shared server environments.
Hello, Zi and Opengeek. Thank you for your answers.
We think that users who are looking for cms systems (and don’t know about modx’s operation well) wouldn’t notice a usage of modx’s file manager and other tools. Even if modx’s senior users couldn’t delete the rss directory after he uninstalled the modx, if he don’t aware of the method. We think this is not a good feature.
Modx is getting newcomers day by day and many of them are not well-skilled, like web-designers and webmasters, and we wish that modx should be user-friendly and easy-to-use system.
If many newcomers tried to use modx, and if they faced the same phenomenon as we said, they would feel that modx is not user-friendly, and they would never use modx again, and they even would say that "modx was unkind system!" to their neighborhood.
I don’t know about U.S’s hosting environment, but in Japan, over 2/3 hosting users are using shared-server service, so this problem is fatal for Japanese environment. I think there are many other countries like Japan. So we think user-friendly features are very important.
The reason we wrote about commitment right is that if the problem occurred and it seemed to be not important among core members, we would like to handle these problems --- so if you ordered us to use jira, we obey and use jira. But the reason that we propose about these things is that we hope modx should be opened and friendly project to everyone, even if not-skilled newcomers. Please understand about that.
Sincerely,
Yama and Nick(smallworld) from Japan
