Permissions on Install

Running an install on a server with a host I've never used before and got a nice surprise.  When I run http://yoursite.com/install/index.php it comes up and says all files are writable except the ffmpeg.exe as being unexcutable.  I was suddenly thinking, since when did Boonex start setting files that need no chmod to them on install.  Wow, what a great trick that would be. 

Unfortunately it's not true, the script is reading the 755 & 644 permissions as writable even though they are not.  Ok, they're writable by the owner, but not the endusers.  LOL...

Not sure if this is a bug with 6.1.6 or if it's a host isolated issue.  In Boonex's defense, I have installed 2 copies of 6.1.6 on another hosts server and it has gone exactly as I'm used to, including the chmod part.  Just curious and wondering who else has seen this among those experienced with Dolphin.  This might explain why so many newbiew are having problems with fresh installs thinking they are set when they're not.

In addition, at the end of the install, when it says to chmod back the files, it wants them to go to RRR only with NO Write or execute.  I think that's a 444 code.  Obviously, I'm not setting them they're, just where we're supposed to at 755 & 644.  I am seeing this as an issue though.

And FYI:   I've used the same zip file of Dolphin 6.1.6 on all 4 installs.  I just keep unzipping and uploading it, not going back after new package every time. 

A lot of hosts are using suphp.exe for additional security. This means that you do not have to chmod the files.... At least that is what my host tells me!

true when i installed d7 i only needed to chmod ffmpege.exe

 Which sounds good in the interest of security and the number of people who do not know how to chmod a file.  We were all one of them at one time or another, however, when it's ordering files to be chmod'd back to 444 and made completely unwritable when we know that is not the goal, then that is where issues begin to arise.  Perhaps Boonex wants to patch the script to recognize wht php is being used and write it so the installs still arive at the same result. 

I've noticed a large number of newbies lately complaining of cron job e-mails coming like crazy and so on.  Perhaps this has some effect on it.  I have personally seen a site that dumped over 600 cron job e-mails in one day saying files like periodic/notifies.php don't exist and gone into the server to see them sitting right where they're supposed to be.

I had the same problem with D7. My original host actually told me that they wouldnt allow perm changes to make ffmpeg.exe executable. Dont know if you're having the same problem, but I had to get a second host because of it.