Is it possible to force some sort of naming convention when saving a node of a certain type, in this instance a "year", so ideally id like the client to use sensible names like, 2018, 2019 etc. But, they could in all fairness type and save "fluffy pink rabbit" which could cause problems throughout.
I guess you could tie into the event handler for the save event and then 'logic'?
Just wondering how others tackle this surely common problem, is it just a case of client education or do you jump through some development hoops to make the system as fool-proof as you can?
Forcing a node naming convention
Hey all.
Is it possible to force some sort of naming convention when saving a node of a certain type, in this instance a "year", so ideally id like the client to use sensible names like, 2018, 2019 etc. But, they could in all fairness type and save "fluffy pink rabbit" which could cause problems throughout.
I guess you could tie into the event handler for the save event and then 'logic'?
Just wondering how others tackle this surely common problem, is it just a case of client education or do you jump through some development hoops to make the system as fool-proof as you can?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.