Limiting Avatar size

[balisto]

OK. First step of your instructions accomplished successfully Avatar image uploads are now limited to 100KB - that's fair enough and works great! Thanks again. I didn't get how to do the redirect in case an avatar was bigger than 100KB...

The saving process in user.php is:

Code: [Select]

if ($access->canViewProfOwn) {
if ($mosConfig_sef != 2) {
$query = "SELECT id FROM #__menu WHERE link='index.php?option=com_user&task=list'"
."\n AND published='1' AND ((language IS NULL) OR (language LIKE '%$lang%'))";
$database->setQuery($query, '#__', 1, 0);
$_Itemid = intval($database->loadResult());
if (!$_Itemid) { $_Itemid = $Itemid; }
$redLink = 'index.php?option=com_user&task=profile&uid='.$uid.'&Itemid='.$_Itemid;
} else {
$redLink = 'members/'.$row->username.'.html';
}
mosRedirect ($redLink, _E_USRDET_SAVED);
} else {
mosRedirect ('index.php', _E_USRDET_SAVED);
}

So I don't see a possibility to ask again for the file size (after it was already rejected) to redirect to another message!?! Or should I use another IF? You see I'm not a programmer, so obviously I lack some logic 

[datahell]

From the language files:
define('_E_USRDET_SAVED','Your settings have been saved.');
Now, we want to modify the above message when the avatar upload fails.

Find (line 650 or near): $file = $_FILES['upavatar'];
Add bellow:
$avatar_ok = 0;
Find (line 665 or near): $newavatar = 1;
And next to it or bellow it: $avatar_ok= 1;

Now make lines 682 to 696 (or near) like this:

   if ($access->canViewProfOwn) {
      if ($mosConfig_sef != 2) {
         $query = "SELECT id FROM #__menu WHERE link='index.php?option=com_user&task=list'"
         ."\n AND published='1' AND ((language IS NULL) OR (language LIKE '%$lang%'))";
         $database->setQuery($query, '#__', 1, 0);
         $_Itemid = intval($database->loadResult());
         if (!$_Itemid) { $_Itemid = $Itemid; }
         $redLink = 'index.php?option=com_user&task=profile&uid='.$uid.'&Itemid='.$_Itemid;
      } else {
         $redLink = 'members/'.$row->username.'.html';
      }
                $txt = (isset($avatar_ok) && !$avatar_ok) ? ' Your avatar could not be uploaded. Try with a smaller image.' : '';
      mosRedirect ($redLink, _E_USRDET_SAVED.$txt);
   } else {
                $txt = (isset($avatar_ok) && !$avatar_ok) ? ' Your avatar could not be uploaded. Try with a smaller image.' : '';
      mosRedirect ('index.php', _E_USRDET_SAVED.$txt);
   }

[balisto]

Whow. Works great! Thank you. Just to be sure that I don't mess everything up: As I have a multilingual website I created a new language definition

Code: [Select]

define('_E_AVATAR_TOO_LARGE','Your image was too large. Please try again with a smaller image.');
Could I change your given code this way:

if ($access->canViewProfOwn) {
      if ($mosConfig_sef != 2) {
         $query = "SELECT id FROM #__menu WHERE link='index.php?option=com_user&task=list'"
         ."\n AND published='1' AND ((language IS NULL) OR (language LIKE '%$lang%'))";
         $database->setQuery($query, '#__', 1, 0);
         $_Itemid = intval($database->loadResult());
         if (!$_Itemid) { $_Itemid = $Itemid; }
         $redLink = 'index.php?option=com_user&task=profile&uid='.$uid.'&Itemid='.$_Itemid;
      } else {
         $redLink = 'members/'.$row->username.'.html';
      }
                $txt = (isset($avatar_ok) && !$avatar_ok) ? ' _E_AVATAR_TOO_LARGE' : '';
      mosRedirect ($redLink, _E_USRDET_SAVED.$txt);
   } else {
                $txt = (isset($avatar_ok) && !$avatar_ok) ? '_E_AVATAR_TOO_LARGE' : '';
      mosRedirect ('index.php', _E_USRDET_SAVED.$txt);
   }

Or is this wrong syntax? Can I use HTML at this place to have the error message in red? For example:

$txt = (isset($avatar_ok) && !$avatar_ok) ? '<font color="red"> _E_AVATAR_TOO_LARGE</font>' : '';

Or would this be wrong? Alternatively I could use the red message-box instead of the blue one, but don't know how to manage that.

BTW: just in case, anybody else is experiencing the same problem with 1&1 (or any other) hosting, it seems that this is a known issue with gd resizing cause they usually have low memory limit for their shared hosting (some say it's only 20MB, phpinfo says it's 40 - the truth is probably somewhere in the middle). This is just one thread out of 1000s on the net: http://www.phpalbum.net/node/1197