Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
$407 per month—let's make that $500!Learn more
MODX is written in PHP, and as such, it relies on the underlying PHP date functions, e.g. strftime. The discussion here can get quite tricky because the strftime and strtotime functions deploy similar arguments, but they are not identical.
The discussion here relates primarily to the following content fields:
createdon- creation date;
deletedon- date of deletion;
editedon- the date of the last edit;
publishedon- the date when the resource was published;
pub_date- the date when the resource should appear in the publication;
unpub_date- date of removal from the publication.
Unix timestamps and formatted dates¶
Depending on the source and method of retrieving a value, you may either receive a UNIX timestamp or a formatted date. A unix timestamp is recognised as a large integer number (representing the number of seconds sinds January 1st 1970).
In MODX, the
date output modifier, which is used to format dates using PHP's
strftime() function, expects a unix timestamp. In order to turn a formatted date into a unix timestamp, you will use the
strtotime output modifier.
So if a value, say
[[*createdon]], returns a formatted date, you need to first transform it to a unix timestamp with
[[*createdon:strtotime]] before you can format it with
date. But, if a value immediately returns a unix timestamp, you can skip that.
It's not possible to give every possible example, but here are some common ways of formatting dates using the MODX output filters.
|Example Output||The Filter Parameters|
|Thu Apr 14, 2011||
|18 April 2011||
|Monday, April 18, 2011||
|Depends on configuration||
The date output modifier internally runs the PHP strftime function, so all documentation about strftime applies to the date output modifier as well.
To change the language used by the
date output modifier (e.g. for the name of days and months), configure the
locale system setting in MODX appropriately.
|%a||Short weekday name||Sun|
|%A||Full weekday name||Sunday|
|%b||Short month name||Jan|
|%B||Full month name||January|
|%c||Local date and time||Wed Jan 7 00:22:10 2010|
|%C||Century (the year divided by 100, range 00 to 99)||20|
|%d||Day of the month (01 to 31)||03|
|%D||Same as %m/%d/%y||04/29/10|
|%e||Day of the month (1 to 31)||3|
|%H||Hour (24-hour clock)||00-23|
|%I||Hour (12-hour clock)||01-12|
|%l (lower-case L)||Hour in 12-hour format, with a space preceding single digits||1-12|
|%j||Day of the year||001 to 366|
|%m||Month||01 to 12|
|%M||Minute||00 to 59|
|%P||am or pm||am|
|%p||AM or PM||AM|
|%r||Same as %I:%M:%S %p||08:23:11 PM|
|%R||Same as %H:%M||23:11|
|%S||Second||00 to 59|
|%T||Same as %H:%M:%S||26:12:27|
|%u||Weekday (Monday=1)||01 to 07|
|%w||Weekday (Sunday=0)||00 to 06|
|%Z or %z||Time zone offset or name||-005 or EST|
|%%||A literal % character||%|
Server compatibility note¶
Not all servers support all the formatting parameters, in particular on Windows
%e is not supported and
%Z return the timezone name instead of the offset. On Mac,
%P is not supported.