Thank you =]

I also checked the main logs on the cpanel, and got this info :

 suexec policy violation: see suexec log for more details

[Mon Jun 27 22:23:21 2011] [error] [client 166.248.0.219] Premature end of script headers: 500.php, referer: http://endeavourdigital.net/pg/admin/statistics/ [Mon Jun 27 22:23:33 2011] [error] [client 207.46.204.180] File does not exist: /usr/local/apache/htdocs/robots.txt [Mon Jun 27 22:24:01 2011] [error] [client 85.133.71.104] Invalid method in request \x80y\x01\x03\x01 [Mon Jun 27 22:24:01 2011] [error] [client 85.133.71.104] File does not exist: /usr/local/apache/htdocs/501.shtml [Mon Jun 27 22:24:01 2011] [error] [client 85.133.71.104] Invalid method in request \x16\x03 [Mon Jun 27 22:24:01 2011] [error] [client 85.133.71.104] File does not exist: /usr/local/apache/htdocs/501.shtml [Mon Jun 27 22:24:25 2011] [error] [client 66.249.67.98] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace. [Mon Jun 27 22:24:25 2011] [error] [client 66.249.67.98] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace. [Mon Jun 27 22:24:30 2011] [error] [client 79.141.40.132] Invalid method in request \x80y\x01\x03\x01 [Mon Jun 27 22:24:30 2011] [error] [client 79.141.40.132] File does not exist: /usr/local/apache/htdocs/501.shtml [Mon Jun 27 22:24:31 2011] [error] [client 79.141.40.132] Invalid method in request \x16\x03 [Mon Jun 27 22:24:31 2011] [error] [client 79.141.40.132] File does not exist: /usr/local/apache/htdocs/501.shtml [Mon Jun 27 22:24:45 2011] [error] [client 166.248.0.219] File does not exist: /home2/endeavp5/public_html/xuum, referer: http://endeavourdigital.net/pg/dashboard/ [Mon Jun 27 22:24:45 2011] [error] [client 166.248.0.219] SoftException in Application.cpp:601: Directory "/home2/endeavp5/public_html/mod" is writeable by group, referer: http://endeavourdigital.net/pg/dashboard/ [Mon Jun 27 22:24:45 2011] [error] [client 166.248.0.219] Premature end of script headers: icondirect.php, referer: http://endeavourdigital.net/pg/dashboard/ suexec policy violation: see suexec log for more details [Mon Jun 27 22:24:45 2011] [error] [client 166.248.0.219] Premature end of script headers: 500.php, referer: http://endeavourdigital.net/pg/dashboard/

Did you talk to HM Tech Supp ?
And what did they say about the "755 and 644" perms ?
Those are *still not correct.
Seems that you've made some elementary errors in the setup and H/M Tech Supp should be able to tell you exactly what you've done wrong. That's what they're there for.
The problems are not caused by any aspect of Elgg or PlugIns - simply ->
Server Configs that's all.

^_^; awesome, i knew I wasn't a total fool lol.

Thank you! I'll talk to support and report =]

And here is the awesome result:

oki ;-0 except that the data folder should be 777 at the top.
"batch operation" ?
chmod -R 0644 <elgg-code-dirname>
if you have shell access else do each one manually thru (s)ftp

NO NO NO - the data folder (and files) must be writeable by the webserver which does not necessarily mean chmod it to 777. You certainly do not want all the files in the data dir being world-writeable from a security point of view. ;-)

Marik, sometimes Elgg doesn't work with the 775 permission on some servers. It requires 777. And, the data folder is outside the public directory. So, I don't think it would be that vulnerable of being hacked.

I'm wondering if the permission issue of the data folder really is causing the problem with the missing images. Did you change anything at all in the data folder and its permissions when upgrading from 1.7.9 to 1.7.10? The upgrade process of Elgg wouldn't change anything in the data folder. So it seems more likely to me that the problem is either caused by some corrupted files of Elgg 1.7.10 or by an error in the database that was introduced by the upgrade. Have you restored your database with a backup created while still on Elgg 1.7.9 when you "downgraded" again?

Permissions 777 are normally not necessary for the data folder. If your server is running with suPHP enabled it maybe even stop working because of it as it might be seen as security risk. In this case 755 should work. If your Apache runs with php as a module (DSO) it still can work with 755 if owner and group of the data folder are set to the owner and group of the Apache process, for example nobody or www or wwwrun.

IT was a permission file structure of the site, some of the plugins didnt have correct CHMOD settings, unrelated to the image files but needed to run the site correctly, got the php code from my site, fixed it a little (had some artifacts randomly that broke the code, go figure) and uploaded as a mini php plugin to save others time =]

http://community.elgg.org/pg/plugins/project/746391/developer/Shadowpark/easyperm-script