gwp_date_format

The gwp_date_format Merge Tag Modifier returns a modified date time relative to the date time of a field-value with a date/time string in the desired format.

{Date Field:1:gwp_date_format modify="first day of next month" format="d-m-Y"}

Using with Date Field

Example where field 1 is a Date Field:

{Date Field:1:gwp_date_format modify="first day of next month" format="d-m-Y"}

Using with Text Field

Example where field 2 is a Text Field:

{Text Field:2:gwp_date_format field_format="Y-m-d" field_timezone='UTC' format="d/m/Y\ \a\t\ H:i:s" timezone='Europe/Amsterdam'}

Input format of the field value

• Date field: you do not need field_format. The modifier reads the date format set in the field (mm/dd/yyyy, dd/mm/yyyy, dd-mm-yyyy, dd.mm.yyyy, yyyy/mm/dd, yyyy-mm-dd or yyyy.mm.dd).
• Other fields (Single Line Text, Hidden, and so on): set field_format to the format of the stored value, like Y-m-d H:i:s. Without it, the modifier returns an “unknown date field format” error.
• Unix timestamp: use field_format="U" for a timestamp in seconds since 1 January 1970 UTC.
• Local timestamp: use field_format="U_local" for a timestamp that holds the local (wall clock) time instead of UTC. The number is read as a time in field_timezone.

{Timestamp:5:gwp_date_format field_format="U_local" field_timezone="Europe/Amsterdam" format="d-m-Y H:i"}

Timezones and nested merge tags

field_timezone is the timezone of the stored value and timezone the timezone of the output. Both default to the WordPress timezone setting and accept a timezone name like Europe/Amsterdam or an offset like +0200.

modify, timezone and field_timezone support nested merge tags, so a value can come from another field:

{Date Field:1:gwp_date_format modify="+*|Days:3|* days" timezone="*|Timezone:4|*" format="d-m-Y"}

For more modify examples, see Relative Date Formats in Gravity Forms.

Try it

Since

The gwp_date_format modifier was added in 1.2.

Frequently Asked Questions