Scenario: Content profile node-type has new required fields added after many users have already filled out their profile info. (this scenario can work for any node-type). They go back to update their profile, and don't see the need to fill in the required fields, submit the forms, miss seeing the error message, and walk away, thinking that their updates have been submitted successfully.
I've had various versions of this same scenario play out across different websites and situations. And have tried out various home-made solutions where I have data collected at the validation stage in a nodeapi hook implementation. But those solutions are painful and flawed.
Anyone know of a simple solution to this pervasive problem?