Best approach if I want to make some fields required?

[martinluff]

I'd be interested in the approach you suggest in PW if I want to make some fields in a template required so a page can't be created if they're empty?

[Adam Kiss]

I think it's for client – again, either just tell them or page::save() beforeHook, that will check for existence of some fields and if left blank, will halt save() routine and return to edit page with the top message set [that should be possible]. However, I don't think there is inline validation [i.e. erroneous fields red or something]

[ryan]

This is the same situation as my last post. This was taken out last minute. Though I believe the implementation for this actually still is in place (just disabled). There are a few reasons for this. Changing a pages template to one that had required fields that didn't exist in the previous template resulted in lots of ugly error messages. Easy enough to fix, but I figured this was non-crucial and something I could get back to later. The other part was that I hadn't yet implemented the required option for some of the more complex fieldtypes, and wanted to put more time into it. Lastly, required fields drive me nuts (I have a strange workflow). But I recognize the need and you can count on this one coming back.

[martinluff]

@adamkiss - yes makes sense. I can also just add a little JS to alert users or do validation if leaving a field empty is likely to cause issues...

@ryan, likewise, makes a lot of sense. Looking forward to seeing how the system blossoms as you decide how to implement (or for that matter leave out) features from PW1...