Required Field Add-on Idea
Development and Programming
Related, but separate (and maybe a cool addon or field type idea). Is there a field, something in the ‘comments’ variety. imagine an entry where there’s an empty field, that HAS to be filled out with each save. as in: “always required”
versioning + a forced, written comment log would be the ticket @andrewgunstone
Ahh like a commit message, that’s a good idea!
In the past I’ve set up a general ‘required’ textarea field … but I’ve then had to create an add-on that uses the entry saving hook to take the content of the field, adds it to a db table (with the member id, entry id, datetime, etc), and then wipes the content from the field (so it’s empty for next time, thus ‘required’ again).
Then I created a custom fieldtype that just displayed the results from the db table for that entry.
But this is sort of like Git comments … “I did some stuff” isn’t very helpful.
@mithra62 highlander might.. accidentally fit this need, too 😃
Add highlander field to a channel. require it. and.. the field could be blank, well, there can be only one, innit?
so it (ironically?) forces a unique comment
would require uniqueness across all entries, but I like where you’re headed 🤔
all entires in a channel, or all entires, period?
in a channel OR all :slightlysmilingface: is flexible
@Bryan err… the use case from my client call, is more nuanced
every save of the entry would require a comment. so it’s like.. a Highlander field that ‘empties’ every time an entry edit occurs
… though would be overwritten upon subsequent changes 🤔 would lose the history
one sec; it may work with Grid