ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

entry_date format in Safecracker doesnt work

March 07, 2011 8:48am

Subscribe [3]
  • #1 / Mar 07, 2011 8:48am

    hi everyone!

    when i want to display entry date in Safecracker this tag doesn’t seem to work at all:

    {entry_date format="%d.%m.%y"}

    can anyone confirm the same thing? is it a bug?

    it only works without formatting like {entry_date}

    regards,
    dmitry

  • #2 / Mar 07, 2011 10:22am

    Sue Crocker

    26054 posts

    Hi, dmitry.

    We’ll need more information, please.

    Can you tell us which version/build of EE2.x you’re using? See EEWiki:// HowTo Determine My EE Version

    Which version of SafeCracker are you using? 1.03 or 2.0?

  • #3 / Mar 07, 2011 2:29pm

    i run EE 2.1.3 Build: 20101220 and Safecracker 2.0

  • #4 / Mar 07, 2011 5:33pm

    Ingmar

    29245 posts

    Can you show us a little more of your code? I am talking about the relevant parts of your form.

  • #5 / Apr 05, 2011 3:40pm

    Noah Kuhn

    60 posts

    Doesn’t work for me either

    EE 2.1.3
    SC 2.0.0

    {exp:safecracker channel="the_channel" url_title="{segment_2}" return="/{segment_1}/{segment_2}/" limit="1" show_future_entries="yes"}
    {entry_date format="%F %Y"}
    {/exp:safecracker}

    Have tried everything, taking out the show_future_entries, hard coding the url_title etc.

  • #6 / Apr 05, 2011 3:41pm

    Noah Kuhn

    60 posts

    Actually,

    Just specifying: {entry_date} works. But once you add the format code, it stops parsing it.

  • #7 / Apr 05, 2011 4:07pm

    Sue Crocker

    26054 posts

    Hi, Noah and Dmitry.

    EE takes a date field and saves it out to the database, so specifying different date formats aren’t going to work. Mostly because what if you only specified the year? What would EE use for the other parts of the date field?

    So I’d say this is by design, and not a bug per se. Does that make sense?

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases