Open system/application/config/mime.php file and add RAR definition

‘rar’ => ‘application/rar’

(Note: I use Firefox 4, that config may not work on other browser because other browser may define MIME for rar fire differently.

I increase the “file_uploads” to 150MB. When I try upload 18MB file use my application it’s just show me a blank page without any error, then I look error log file and found something

POST Content-Length of 18248964 bytes exceeds the limit of 8388608 bytes in Unknown on line 0

I found that I also need increase the ‘post_max_size’ to 150MB on php.ini. Yup my application work fine now, glad to see this

reference : http://codeigniter.com/forums/viewthread/127502/

1. Login To your Yahoo small business, http://smallbusiness.yahoo.com/
2. Click “Access Your Account” on top bar, then “small business”
3. Click “Web Hosting Controll Panel”
4. Click “Create & Update” tab
5. Click “Other Site Building Tools”
6. Click “PHP/Perl Mail”
7. On right side, you must set email sender to use on “From” field, for example I use webmaster
8. Click “Save Default” to set it

Now at CodeIgniter controller we must use email address that have been already set on ‘from’ field, for example I have already set “webmaster@mydomain.com” so here the code example:

## send email to some one
$this->load->library('email');
$config['protocol']     = 'sendmail';
$config['mailpath']     = '/usr/sbin/sendmail -t';
$config['wordwrap']     = TRUE;
$config['useragent']    = 'CI Mailer';
$config['mailtype']     = 'text';
$config['newline']      = "\r\n";

## email contact
$this->email->initialize($config);
$this->email->from('webmaster@mydomain.com');
$this->email->to('recipient@domain.com');
$this->email->subject('Web Visitor");
$message  = "Test Email";

$this->email->message($message);
$this->email->send();
#echo $this->email->print_debugger();

In part used session function (I use the library session Codeigniter) , randomly displays a HTTP 406 error.

When searching on google, I know that the problem is probably caused by the Apache  mod_security. I tried de-active mod_security function using  . htaccess files but it causes HTTP error 500.

When a page that uses session displays a HTTP 406 error, It can be fixed by delete computer cookies, but sometimes  it comes back HTTP error 406 at random.

Another problem, the session produced by the library Codeigniter likely trigger mod_security apache and the mod_security considers it as a threat so mod_security block access from my  IP (I have many times to reset my modem to get a new IP)

My solution :  I change my session from the Codeigniter library  into Native PHP session. The solution worked perfectly, I don’t have anymore HTTP error 406 and blocked by mod_security.

After googling , I found information that say there a problem with server clock, since I got server access ( thanks to someone that allow me in ) I adjust server clock same as my computer clock. Surprise  ….. I test from IE everything work fine just like there nothing happen.

Then I run a little test, my session expire setting is 7200 (2 hour), I change my computer clock 1 hour faster, I test the administrator panel again and everything work fine.

Then I adjust my computer clock 3 hour faster (more that session expire setting) then my administrator panel fail to work again …. just wondering how could be like this

For now I move my application to native PHP Session …. lot work to do

$patt = '/^(0?[1-9]|[12][0-9]|3[01])[\/](0?[1-9]|1[0-2])[\/](19|20)\d{2}$/';

After sure the date input is valid according our rule, we must also validate the input date according the calendar, for example, if the user input 31/2/2009 it will be valid in that regular expression check, but of course there no February 31 :p

$inputdate = explode("/",$_POST['inputdate']);
if ( ! checkdate($inputdate[1],$inputdate[0],$inputdate[2]) )
{
 echo 'Invalid Date';
}

So here my complete example code snippet :

## date input pattern validation
$patt = '/^(0?[1-9]|[12][0-9]|3[01])[\/](0?[1-9]|1[0-2])[\/](19|20)\d{2}$/';
if (! preg_match($patt,$_POST['inputdate']))
{
echo 'Invalid Date Format, mm/dd/yy';
die();
}
else
{
echo 'A Valid Date Format';
}

## calendar validation
$inputdate = explode("/",$_POST['inputdate']);
if ( ! checkdate($inputdate[1],$inputdate[0],$inputdate[2]) )
{
echo 'Invalid Date according Calendar';
die();
}
else
{
echo 'A Valid Date according Calendar';
}

In code igniter, when you use “Language Class” you will create a “Language file” in your language directory application path. The important part is, when you make the “language file” make sure you use right decode method. By default many text editor use ANSI decoding for file format. It must be change to UTF-8 to make sure when you use your language file, it will display right character.

For example, I use Notepad++ editor, I can change the file format into UTF-8 from Toolbar choose “Format” -> “Convert to UTF-8 without BOM”.

Code Example :

$lang['messege_fail_head'] = “Désolé, il ya une erreur”;

With out correct file encoding, when you “echo $this->lang->line(‘messege_fail_head’)”

It will display :

D?sol?, il ya une erreur

With correct file encoding (UTF-8)

Désolé, il ya une erreur

The CI Upload class use their own ‘mime’ data to determinate the file mime type, I think why they use own mime rather than using mime function on PHP or Apache is to avoid dependency. Some server may not include mime extension in their setting so it will be problem if we can not use mime function to determinate the file mime.

The CI mime file located in system/application/config/mimes.php , when we do upload some file using upload class, the file that uploaded will generate the information about the file like file name, file type, size and temporary file name. This information generated by the browser. Here some information example of an ‘exe’ file uploaded using Internet Explorer browser.

Array
(
[userfile] => Array
(
[name] => putty.exe
[type] => application/x-msdownload
[tmp_name] => d:/wamp/tmp\phpCF.tmp
[error] => 0
[size] => 454656
)

)

The Uploading class use ‘type’ information as mime types. That information will compared with data from system/application/config/mimes.php to determinate if the file allowed to upload. If the data from ‘type’ included on mimes.php data it mark as ‘allowed file’. From mimes.php, an ”exe” file mime type is :

‘exe’ => ‘application/octet-stream’,

And from ‘type’ information the ‘exe’ file mime type is :

application/x-msdownload

Now we can see the problem here, the file information is generated by the browser and the browser may generate different kind of file type, Here the example for an “exe” file :

Internet Explorer : application/octet-stream (we have no problem if we use IE for upload)
Firefox : application/x-msdos-program (we got problem here)
Safari : application/x-msdownload (we also got problem here)
Opera : application/x-msdownload (we also got problem here)

So, we must check the allowed file type and the mime type in mimes.php in common browser : Safari, IE , Firefox and Opera is quite enough. For debugging, put this code on line 195 of Uploading Class, you will got information about file you been uploaded like in above example.

echo ‘

';
print_r($_FILES[$field]['type']);
echo '

‘;
die();
?>