<p>What about using a table field with a column for HH/MM/SS, with each one restricted to numbers?</p>

<p><a href="https://i.sstatic.net/KL2az.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KL2az.png" alt=""></a></p>

<p>Alternatively you could use <a href="https://github.com/fruitstudios/craft-validateit" rel="nofollow noreferrer">https://github.com/fruitstudios/craft-validateit</a> with a custom regex rule, but I've no idea what that would need to be.</p>

CC BY-SA 4.0
2018-11-19T17:09:24.383Z
Thanks man. Regex looks like a great option. This field already exists so would mean retrofitting a bunch of stuff.
Steven Grant
CC BY-SA 4.0
2018-11-19T17:11:56.543Z
https://stackoverflow.com/questions/8318236/regex-pattern-for-hhmmss-time-string 
Steven Grant
CC BY-SA 4.0
2018-11-18T14:18:15.740Z
2018-11-18T14:18:15.740Z
James Greig
<p>I'm looking for a way to restrict how a field gets formatted.</p>

<p>I have a channel for a podcast that should always be in the format of hh:mm:ss - despite the instructions making this clear, editors tend to ignore and invariably we end up with 45.</p>

<p>Is there a way I can take that input and format appropriately or even alert on the frontend that what they've given doesn't validate?</p>

<validation><format>
Field formatting
# Field formatting

(Asked by: username_0 on 2018-11-18)

I'm looking for a way to restrict how a field gets formatted.

I have a channel for a podcast that should always be in the format of hh:mm:ss - despite the instructions making this clear, editors tend to ignore and invariably we end up with 45.

Is there a way I can take that input and format appropriately or even alert on the frontend that what they've given doesn't validate?

**Tags:** validation, format


---

## 1 answers

### Answer by username_1 on 2018-11-18. Score: 2 | Accepted answer

What about using a table field with a column for HH/MM/SS, with each one restricted to numbers?

[![](https://i.sstatic.net/KL2az.png)](https://i.sstatic.net/KL2az.png)

Alternatively you could use <https://github.com/fruitstudios/craft-validateit> with a custom regex rule, but I've no idea what that would need to be.

> **Comments:**
> **username_0**: Thanks man. Regex looks like a great option. This field already exists so would mean retrofitting a bunch of stuff.  
> **username_0**: https://stackoverflow.com/questions/8318236/regex-pattern-for-hhmmss-time-string   

---

