Required Field Add-on Idea
Development and Programming
@mithra62 I don’t think so, I don’t know what the hook situation looks like there but if you’re doing it as an add-on you might rather keep it in a separate table that just associates the message with a specific entry_version id
It could also be an interesting improvement in the core
yeah
@mithra62 and @creativearc ponder movies where this paradigm exists: “you MUST write something each time!!!”
am thinking:
- FT to require message
- Second layer to display history on entry (likely next to field)
- On save, either write to entry revisions (or more likely) a separate table that stores the datadead simple but a legit one Paul
YaZzzz
11 Nov, 2025: Mithra62 is proud to release the Beetlejuice™ fieldtype.
Beetlejuice (1988)
- Scene: The recently deceased are given The Handbook for the Recently Deceased, which they must read and follow.
- Relevance: They can’t proceed in the afterlife or interact properly with the living without understanding and following the book’s instructions.
but maybe {tps_report} is more relevant
ngl, TPS Reports makes me chuckle
it’s relevant to the need
it evokes: Client requires I do this field… whcih nobody will want to do… yet we have to do..
aka… TPS report
Name the field “What is it you’d say you did here?”