Since you uploaded this package I have made really good use of it! It has made a lot of things easy for me!
I have found one thing that is an issue though; Mandatory values.
On a few Document Types I have mandatory values that users have to enter a specific value into. I don't want any default value in that field because that would let them forget to enter a correct value. One example is a date. I want this date to be entered for an event. But if I want other values to be defaulted then I run into a problem with your package.
It tells me that I have to enter a value in all fields that are mandatory, thus defeating the purpose of making them mandatory. They will always pass a mandatory test when saving a content node.
Is there some way you could skip that test for your Standard Values form?
Yes, this is a very good point. I didn't actually give to much consideration to Mandatory fields, when I first made it. But I clearly should have, as this is a very valid point.
I'm testing the package during the weekend for some updates that I have added. I will see how I can fix the issue with mandatory fields, so it'll be fixed in the next version.
@rasb: A quick update - I turned off page validation, so you can save your standard values even though you have some mandatory fields, which are empty. An error message will appear, but the content will be saved. A bit misleading maybe, but so far its the best I can do.
I will do some further testing and hope to update the project page with a new package soon. I wanted to update the package this past weekend, but got stuck in some xslt testing.
I finally got around to updating the Standard Values package, so you should now be able to save even though a mandatory field is empty. You will still get a warning, but the content WILL be saved.
Mandatory fields
Since you uploaded this package I have made really good use of it! It has made a lot of things easy for me!
I have found one thing that is an issue though; Mandatory values.
On a few Document Types I have mandatory values that users have to enter a specific value into. I don't want any default value in that field because that would let them forget to enter a correct value. One example is a date. I want this date to be entered for an event. But if I want other values to be defaulted then I run into a problem with your package.
It tells me that I have to enter a value in all fields that are mandatory, thus defeating the purpose of making them mandatory. They will always pass a mandatory test when saving a content node.
Is there some way you could skip that test for your Standard Values form?
Thanks,
RasB
Yes, this is a very good point. I didn't actually give to much consideration to Mandatory fields, when I first made it. But I clearly should have, as this is a very valid point.
I'm testing the package during the weekend for some updates that I have added. I will see how I can fix the issue with mandatory fields, so it'll be fixed in the next version.
I will keep you posted.
Thanks for the bug report.
- Morten
@rasb: A quick update - I turned off page validation, so you can save your standard values even though you have some mandatory fields, which are empty. An error message will appear, but the content will be saved. A bit misleading maybe, but so far its the best I can do.
I will do some further testing and hope to update the project page with a new package soon. I wanted to update the package this past weekend, but got stuck in some xslt testing.
- Morten
Hi RasB,
I finally got around to updating the Standard Values package, so you should now be able to save even though a mandatory field is empty. You will still get a warning, but the content WILL be saved.
Go check it out ;)
- Morten
is working on a reply...