Joe,
Maybe I suggested the wrong validation...
The point is that when presenting the data, it will be looked at as an edit, but your create validation ensured that all fields were filled as required.
For that reason, you should be able to set your update validation to not require any of those fields. The other option is to fill those values in the form so that they are presented along with the Id. You could put them in hidden fields...
Either way it has to pass validation before the join data will be present after patching the entity.
-- Maybe I suggested the wrong validation...
The point is that when presenting the data, it will be looked at as an edit, but your create validation ensured that all fields were filled as required.
For that reason, you should be able to set your update validation to not require any of those fields. The other option is to fill those values in the form so that they are presented along with the Id. You could put them in hidden fields...
Either way it has to pass validation before the join data will be present after patching the entity.
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment