Dolphin permissions check...

In Tools -> Admin Tools there is a Javascript button for checking if all file permissions are set correctly, however, it does nothing so I assume for some reason there is a Javascript conflict on that page. I really need to assess the permissions of our site - is there a file/direct link you can suggest to test them?

Is this a fresh install?

Also can you SSH into your server?

If so use the install instructions to run the chmod for the files listed.

Install Script - Step 1 - Permissions

http://www.boonex.com/trac/dolphin/wiki/DetailedInstall

This is a fresh install... but the folder location was moved and I'm concerned that some permissions were not correctly carried over.

I'll run the commands in SSH. The caches are cleared, all manually. Odd!

Just realised I'm able to access the Permissions section by click on 'Permissions' at the top rather than the link within the Admin Tools text. However, all are now set correctly, so that job is complete.

The issue I'm having is adding photos (for example) to the EVOwall... and a standard member not being able to delete their own post... only admin can do so. Membership Levels have all been checked and activated for both standard and admin. Really weird! That's why I thought it might've been a permissions issue conflicting with EVOwall/Boonex Spy. 

Oh, good you figured that out.

I don't have the EVO module.

http://www.boonex.com/trac/dolphin/ticket/2878

 My link works Host Tools - Permissions, does yours?

It would be a God-send if there were an additional button for all the core modules of Boonex (photos, sounds, files, forums, etc... ) which read "permissions". This would be a HUGE help to those who transfer their sites or change hosts. That way it stops the dreaded "my files will not upload" questions.

How difficult would that be to add into each of the core modules in a quick update since so many other modules rely on them to function properly, but no tools exist to check these modules?

 True and I agree; users should see these too as most new users go right to install and never read the actual install directions.

The install directions tell you to do those permissions; for the modules to work right as your last step.

And for those that move sites, file ownership should also be checked. But ownership vs permissions will confuse the hell out of newbs.

But that check will determine if uploaded avatars/photos which should be owned by the apache webserver(except when running suphp) are owned by the user account which will prevent files from being removed when members delete avatars/photos.

 Agree! lol

Ah, but we all don't run Apache .  In my case the website is owned by a user, not by the webserver; however, it is important to make sure that PHP is running as the owner of the website; otherwise, PHP isn't allowed access to the files.

I did mention one condition on which php runs as the owner. Thats with suphp. Other wise apache runs it. I can't think of all possible conditions. There is always of course(cough) windows servers.

Not to mention that I had crontab running as the wrong owner; that was staring me in the face and yet I missed it entirely until I happened to notice the message in the backend.  Once I fixed the owner problem videos and sounds processed faster than you could blink an eye; well, at least fast enough that I am pleased.

http://www.boonex.com/trac/dolphin/ticket/3019

 Excellent!! 

Excellent! The folders for /data and additional subfolders would be checked and permission warnings set since most 3rd party programs drop the files into these spots and then support is sooo much easier.

You guys rock!

 This should have been done years ago! This is going to help many new users.

How do I update lang-en.php or database to add the 2 new lines required by ticket 3019 Host tools - permissions: show modules permissions

'_adm_admtools_modules_dirs' => 'Modules Directories',
'_adm_admtools_modules_files' => 'Modules Files',

 I just manually added like any new language key, then recompiled.

If you SVN update, you will have a new "install" folder, breaking the site. [edit] just rename the folder or remove..

I just did a diff on the two files and found the changes and added.