This happens every time I install a language in 2.0.10. File permissions for forum root directory are changed from 755 to 777, causing internal server error until permissions are manually set back to 755. Don't recall ever seeing this problem in support. Does it only happen to me?
Yes, I've seen that reported around. The installer puts the files to 777 which causes the server (the ones who don't like these permissions) to throw error 500.
Although, looking at the code, it does try 755 first so if it goes to 777 it is strange...
Doesn't it work same way as package manager? Package installs don't cause this problem. Directories are set to 755, so there's no reason to change them, and only the root dir is changed, none of the target theme dirs are affected.
Quote from: Krash on July 16, 2015, 02:46:07 PM
Doesn't it work same way as package manager? Package installs don't cause this problem. Directories are set to 755, so there's no reason to change them, and only the root dir is changed, none of the target theme dirs are affected.
actually we have seen this in the past with the package manager, it was a rare case that was never pinned down... i seem to recall AB had opened a topic in this board about it many years ago. maybe moved to the solved board?
[edit] http://www.simplemachines.org/community/index.php?topic=472532 https://github.com/SimpleMachines/SMF2.1/issues/1276
Yeah it's odd. I'll check the code later, maybe something pops up ;)
@Illori, but I seem to remember a similar issue not long ago: all fine with PackMan, 777 crashes the site with languages. Dunno, I'll search
hmmm.... my server is set to throw a hissy fit on 777 -- but I was able to install Portuguese on my 2.0.10 test installation, successfully, with no error...
seems that it may be server/configuration specific (fun, of course, since that means an intermittent issue)
Quote from: Kindred on July 16, 2015, 03:18:12 PM
seems that it may be server/configuration specific (fun, of course, since that means an intermittent issue)
exactly that is why it has not been fixed over the years since it was first reported [officially].
Maybe get some info on that server configuration while it is doing this to try and narrow down what the root cause is. If its server side its going to be a pain really to find as its so random. While a servers in this state take advantage to investigate.
we really dont know what the config is, most of the time it is on a shared server and only happens with some mods not all.