Field datetime

Version: Free.

Why this type

Date and time in one calendar, not two fields. The saved value is an ISO-like string, so you can sort it. That avoids the mismatches you get from separate date and time fields.

When to use

• Promo start with exact hour
• Scheduled news publish
• Countdown or timer on a landing

Tips

Day-only needs date. Format for display in the chunk or a snippet.

Similar types

• date when time is irrelevant
• time when date lives elsewhere

Schema

{
  "name": "starts_at",
  "type": "datetime",
  "label": "Date and time",
  "tab": "Content",
  "width": 100,
  "active": true
}

Value

datetime-local string.

Section data

Key starts_at in the section data (datetime-local string):

{
  "starts_at": "2026-08-24T14:30"
}

Chunk example

modx

<time datetime="[[+starts_at]]">[[+starts_at]]</time>

fenom

<time datetime="{$starts_at|escape}">{$starts_at|escape}</time>

Common properties

For fields with name that are stored in the section data:

Key	Type	Role	CMP
tab	string	Group subtitle in the inspector	yes
width	25–100	Field width as % of the row (flex)	yes
description	string	Hint under the label	yes
default	any	Initial value for a new section	yes
active	bool	false hides the field in the inspector	yes
required	bool	Required on publish (draft still saves)	yes

See fields overview.

See also

• Field types reference
• Fields overview