How to use it
- In any field that takes dynamic data, write a tag.
- Type a colon and one of the filter names after the tag, inside the braces.
The filters:
:kiln_numberformats a number with your site's separators and no decimals.{acf_price:kiln_number}turns 1234 into 1,234 on an English-language site.:kiln_number2does the same with two decimals.{acf_price:kiln_number2}turns 1234 into 1,234.00. Put the number of decimals right after the name:kiln_number3gives three. A single digit from 0 to 9 works.:kiln_moneyformats a price.{acf_price:kiln_money}turns 25 into $25.00 on a store set to US dollars.:kiln_agoturns a date into relative time.{post_date:kiln_ago}gives "3 days ago". A date in the future gives "in 3 days".
How it works with Bricks' own filters
Bricks reads each part after a colon itself and turns a number into a word count. Kiln therefore carries the
decimals inside the filter name, as in kiln_number2, instead of in a second colon part.
For :kiln_ago, {post_date} and {post_modified} use the post's own timestamp, so the result does not depend
on how Bricks formatted the date. Any other tag can give a Unix timestamp or a date text that Kiln can read. It
reads that text in your site's timezone.
Limits
- The filters change text output only. They do nothing in link or image fields.
:kiln_numberand:kiln_moneyleave the value untouched when it is not a number.:kiln_agodoes the same when it cannot read a date.:kiln_agoreads post dates, Unix timestamps and dates such as2026-10-13. Bricks formats date fields from ACF or Meta Box date pickers before Kiln sees them, so for those use Bricks' own:human_time_diff.:kiln_moneyuses WooCommerce's price format, including the currency symbol, when WooCommerce is active. Without WooCommerce it prints the number with two decimals and no currency symbol.
Settings
None. Turn the module on in Bricks > Kiln (it is on by default).
Requirements
Bricks 2.4 or newer. :kiln_money uses WooCommerce's formatting when WooCommerce is active.