[Deprecated] DMZ 1.5.3 (DataMapper OverZealous Edition)

[eluser]mcnux[/eluser]

@mcnux
If the result of the save returns FALSE, this means one of two things:

1) The validation failed. This should always show an error unless you are using custom validation code.

2) The saving of a related object failed. There are a few common reasons for this:
• First, the related object being saved is not saved.
• Second, the object itself isn’t saved (but this shouldn’t ever happen).
• Third, the most often case, your relationship properties are not correctly configured. Please see the FAQs

To help alleviate this in the future, I’m adding code to DMZ 1.4 that will create error messages when a related save fails. For now, please carefully check your relationship configuration, and make sure that you do not have any typos on either side of the relationship.

Sorry I probably wasn't very clear in my previous post. The validation of the related object (client - there was only one) failed when saving the relationship on the user ($userTwo->save($userOne->client->get()->all)). I couldn't see the error message on $userTwo - I think you got this bit as you mentioned DMZ 1.4 fix.

The actual error was issued because my validation rule requires that a client has a related user. I don't understand why this rule failed, my relationship configuration must be ok as I can relate a bunch of clients who aren't currently assigned to another user to $userTwo, it only fails when they are already assigned to another user. The save works fine when I remove the user validation rule from the client model.

I am happy to avoid adding validation to relationships to get around this but thought you may want to have a look into it.

Many thanks for your help. Great job.