"Mandatory" properties not so mandatory after all...
Note, this is problem we found on v4.7.1...
We have found that our users can do the following:
1. Completely ignore a "mandatory" property while editing a node and leave it blank. They click the "save" button anyway, and are told "your data has been saved, but before you can publish this page there are some errors that you need to fix first." (i.e., the mandatory property!)
2. So, what do our users do? They simply right-click on a parent node, and choose "Publish", check a few boxes, et voila! Their bogus node with blank property has been published! And then of course that section of the site crashes. And so then our users are confused and call us. We have to explain that the word "mandatory" actually means "required", and no, they are not supposed to find a way to leave this blank and should really fill in an expected value.
We are currently hacking in some really quick-n-dirty javascript to not let you even save the node if any of the mandatory properties are left blank. I'm not sure if this is a problem in v5 but I hope this is something that can be addressed somehow.... Even if all you have to do is hack in some other just-as-cruddy javascript to prevent such a situation!
"Mandatory" properties not so mandatory after all...
Note, this is problem we found on v4.7.1...
We have found that our users can do the following:
1. Completely ignore a "mandatory" property while editing a node and leave it blank. They click the "save" button anyway, and are told "your data has been saved, but before you can publish this page there are some errors that you need to fix first." (i.e., the mandatory property!)
2. So, what do our users do? They simply right-click on a parent node, and choose "Publish", check a few boxes, et voila! Their bogus node with blank property has been published! And then of course that section of the site crashes. And so then our users are confused and call us. We have to explain that the word "mandatory" actually means "required", and no, they are not supposed to find a way to leave this blank and should really fill in an expected value.
We are currently hacking in some really quick-n-dirty javascript to not let you even save the node if any of the mandatory properties are left blank. I'm not sure if this is a problem in v5 but I hope this is something that can be addressed somehow.... Even if all you have to do is hack in some other just-as-cruddy javascript to prevent such a situation!
Thx!
I've also had this problem. Glad it seems to be solved in v5: http://our.umbraco.org/forum/core/umbraco-5-general-discussion/25082-Alpha-2-Publish-node-and-all-its-subpages. Too bad v5 has a different problem with mandatory fields: http://issues.umbraco.org/issue/U5-60
Jeroen
I've solved this problem by hooking BeforePublish event.
For more information about how to use BeforePublish event, see here: http://our.umbraco.org/wiki/reference/api-cheatsheet/using-applicationbase-to-register-events/event-examples
Place the cs file in App_Code directory.
Huri
is working on a reply...