Recently I have been having the following error on my PHP code every time I call the PHP function date();  Mostly when running it on my local test server.

Warning: date(): It is not safe to rely on the system’s timezone settings

Cause: Since PHP5.1.0 the E_RESTRICT setting causes PHP to report error for every call
to a date/time function, if no default time is set.

Fix: There are 2 approaches to  resolving this.

1. Set time setting to your PHP script with the function date_default_timezone_set();  with the intended time zone/location eg: for GMT one can use date_default_timezone_set(‘Europe/London’);
2. Set time setting to your php.ini file by editing the line ;date.timezone = to date.timezone = “Europe/London” or you required location. This is good for setting a server wide time setting.

Technorati Tags: DATE, error, PHP, php.ini, PHP5, time setting

Related Posts

• October 7, 2011 -- Spotify crashes in Linux under Wine
• August 10, 2011 -- Cardsave error “transaction date/time expired”
• August 26, 2009 -- Wordpress Media upload HTTP Error
• May 13, 2009 -- Automatically display form data with PHP
• April 14, 2009 -- PDF to Email with registration

WordPress and WordPress-MU have given me the HTTP error in the various installations I have performed and each time there’s a different cause. This post is nothing more than a personal notation for future reference but I hope it’s helpful to someone.

Error: when trying to upload media using the WordPress Flash uploader it get the message HTTP Error

Disclaimer: before messing with your .htaccess file, make sure you have a backup copy of it in case it causes a 500 Server configuration error. If this happens just replace the .htaccess file with the back up version. Check your code for any mistakes and try again.

Possible causes:

• mod_security – basically all Apache servers will have it turned on, so you may need to turn it off for the async-upload.php file using .htaccess. The newer versions of WP have added this code already, but in case you mess up your htaccess file, here it is.  Just add the following lines to the bottom of your .htaccess file in the root folder of your WP or WP-MU installation. 

• Access Denied Error 403/ Permission issue – another typical problem. Make sure that the upload folder is writeable by the server, you can set the permission to 754 and it should work fine. In WordPress the upload folder sits under /wp-content/  in WP-MU it sits under /blogs.dir/”blog number”/files  (default site blog number is 1 and the other blogs are numbered in ascending order of creation)

• PHP Upload limit – check you PHP.ini settings for the settings upload_max_filesize and post_max_size. You can change these directly in your PHP.ini if you have access to it or you can change it by adding a php.ini file to you root directory with the following code. The default is normally 2M but you can change it to anything at your own risk, you should not need more then 8M.)

• Authentication Failed Error 401- I checked my server log and noticed that WordPress was trying to access the 401.shtml error template every time I got the HTTP error during a media upload attempt. This normally occours if you are using password protection for the WordPress root folder or the folder where your uploads should reside. You should disable the password protection on the folder i norder for the uploader to work.

Hope it helps. Please leave your contributions and bug reports so others can benefit from it.

Technorati Tags: .htaccess, Apache mod_security, HTTP Error, php.ini, swfupload, WordPress, WordPress-MU

Related Posts

• January 31, 2011 -- It is not safe to rely on the system’s timezone settings
• August 12, 2010 -- LinuxCon 2010 Just for Fun Poll Results explained
• June 5, 2009 -- Keyword search and website ranking tools
• May 12, 2009 -- Offline Blogging Tools
• March 27, 2009 -- .htaccess 301 Redirect