Grow your CSS skills. Land your dream job.

Last updated on:

Change Date from dd/mm/yyyy to yyyy-dd-mm


$date_array = explode("/",$date); // split the array
$var_day = $date_array[0]; //day seqment
$var_month = $date_array[1]; //month segment
$var_year = $date_array[2]; //year segment
$new_date_format = "$var_year-$var_day-$var_month"; // join them together

Possibly a more MySQL friendly format in some circumstances.

Change period-separated to slash-separated or vice versa (and reverse order)

Convert date from YYYY/MM/DD to DD.MM.YYYY (and from DD.MM.YYYY to YYYY/MM/DD)

 * @param string $date (d.m.y, y-m-d, y/m/d)
 * @return string|bol

function convertDate($date) {
       // EN-Date to GE-Date
       if (strstr($date, "-") || strstr($date, "/"))   {
               $date = preg_split("/[\/]|[-]+/", $date);
               $date = $date[2].".".$date[1].".".$date[0];
               return $date;
       // GE-Date to EN-Date
       else if (strstr($date, ".")) {
               $date = preg_split("[.]", $date);
               $date = $date[2]."-".$date[1]."-".$date[0];
               return $date;
       return false;


  1. kukat
    Permalink to comment#

    date(‘Y-m-d’, strtotime(’23/10/2009′));

  2. Fabricio Anzorena
    Permalink to comment#

    implode(‘-‘, array_reverse(explode(‘/’,$date)));

    Won’t have the 1970 limit problem of the timestamp.

  3. Emma Davis
    Permalink to comment#

    Your last line of code in preparing the date for databse is incorrect as it puts the day before the month:

    $new_date_format = “$var_year-$var_day-$var_month”;

    Should be:

    $new_date_format = “$var_year-$var_month-$var_day”;

  4. Prashant Palikhe
    Permalink to comment#

    Fabricio’s answer is much more elegant and works just fine:)

  5. nile
    Permalink to comment#

    kukat’s is the best though.

  6. Kira
    Permalink to comment#

    Thank you. Simply effective :)

  7. Jitendra Joshi
    Permalink to comment#

    DateTime::createFromFormat(‘d/m/Y’, “21/1/2013″)->format(“Y-m-d”)

Leave a Comment

Posting Code

Markdown is supported in the comment area, so you can write inline code in backticks like `this` or multiline blocks of code in in triple backtick fences like ```this```. You don't need to escape code in backticks, Markdown does that for you.

Sadly, it's kind of broken. WordPress only accepts a subset of HTML in comments, which makes sense, because certainly some HTML can't be allowed, like <script> tags. But this stripping happens before the comment is processed by Markdown (via Jetpack). It seems to me that would be reversed, because after Markdown processes code in backticks, it's escaped, thus safe. If you think you can fix this issue, get in touch!

If you need to make sure the code (typically HTML) you post absolutely posts correctly, escape it and put it within <pre><code> tags.

Current ye@r *

*May or may not contain any actual "CSS" or "Tricks".