The recommended setup is:
1. your user account should own the code directory with permissions of 755 for directories and 644 for files.
2. the apache account can own the data directory with permissions of 755 or you can own the data directory with permissions of 777. Apache should create directories in the data directory that it owns and that you won't be able to read with a normal user account (new users are placed in the 2010 directory for example - at least for this year).
In Ubuntu, owner must be 'www-data'
Have you worked through all the troubleshooting guidance such as checking allow override and have you checked that mod rewrite is working as is documented in the trouble shooting guide?
ok I have it now. thanks fot all!
first thing to have in mind, maybe in wiki doc:
enable .htaccess : some server hosting can put it off now by default like mine :-(
then also found that PHP Safe Mode and Safe Mode GDI have been disable, but
I'm not sure, and I want to ask: Is Safe Mode compatible with elgg 1.7.2 now???
because I can run my site also with it on. but in generally do you advice it? my server hosting says: YES!!!! don't put it off!!!
best regards
PHP Safe Mode has been deprecated for PHP 5.3. I wouldn't put much faith in a hosting provider that still insists that it is used. If I remember correctly, the possible conflict between safe mode and Elgg was writing and reading from the data directory. It is possible there could be other issues and safe mode is not supported.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.