Allow ezuser datatype fromString to be used for updates

[peterkeung]

When creating a user, it's important to make sure there isn't an existing user with the same username or e-mail address (when RequireUniqueEmail is enforced). However, when updating a user, this limitation should be lifted if the match is on the user that you're trying to update.

[andrerom]

This probably fixes this one doesn't it?
http://share.ez.no/forums/developer/problems-with-attributes-of-the-user-datatype-in-ezcontentfunctions

That is if you actually use updateAndPublishObject for this.

[peterkeung]

That is the thread that reminded me to submit this pull request, actually.

[andrerom]

Thanks, merged :)

[nfrp]

Thanks Peter & Andre !

[skrosoft]

It seems there is a problem with the serialized draft present in the data_text attribute. Data are saved when calling the fromString function but is written back to the previous value when attribute->store() is called.

I solved this like that:

$user->setAttribute('email', $email); // change the email in the ezuser table
$user->store();

$contentObject = $user->contentObject();
$dataMap = $contentObject->dataMap();
$userDataMap = $dataMap['user'];
$userDataMap->setAttribute('data_text', ''); // empty the serialized data
$userDataMap->store(); // auto generation of new serialized data using the previously saved ezuser

// increment the version control
$result = eZContentFunctions::updateAndPublishObject( $contentObject, array('attributes' => array('user' => "$login|$email")) );