AutoActions - Profile update - change value of submitted field

Hi,

I'm trying to MD5 encode the value of a field when the user updates his profile. I thought it would be as simple as using a PHP(eval) action like this:

but I guess I was wrong.
Trigger: onAfterUserUpdate (is that correct?)
No conditions yet (although once this works I'll add one making sure the value has actually changed as I don't want to encode it over and over again).

I'm sure my mistake will be obvious to you...

Thanks.

Seb.

The after update trigger is fired after the profile has been completely saved. You'll need to use the before update trigger with your same code, which may work.

This is strange...
I changed the trigger to OnBeforeUserUpdate, and enabled debug & maximum error reporting.
I did see in the debug info that the POST variable had been changed to an MD5 hash. So my PHP code was executed.
But then when I go check out my profile... It's the normal text that appears, not the hash, which would mean the hash wasn't saved in the database... Weird.

The field value was processed before your change to post. So your change to post didn't do anything in regards to storing. I suppose you can use prepareFieldDataSave, but it fires for every field being saved so be careful with its usage.

I guess I could limit its usage using a condition...
Can I set the condition to be true only if the submitted value is different from the already stored value? In which case the auto action wouldn't be triggered if the user doesn't change that password... It would be [cb_myfield] different from [var1_cb_myfield] is that correct?

Or maybe I could change directly the value that's being stored? I.e. instead of changing the POST value... I just let the system store the password in clear... Then encode it immediately. It might be better. I guess I would use directly [cb_myfield] to affect the stored one, right?

Can I set the condition to be true only if the submitted value is different from the already stored value? In which case the auto action wouldn't be triggered if the user doesn't change that password... It would be [cb_myfield] different from [var1_cb_myfield] is that correct?

Yes, you can try limiting it only if it was changed using something like the below.

[var1_cb_myfield] Not Equal To [post_cb_myfield]

Or maybe I could change directly the value that's being stored? I.e. instead of changing the POST value... I just let the system store the password in clear... Then encode it immediately. It might be better. I guess I would use directly [cb_myfield] to affect the stored one, right?

You can try using CB Query Field to display the field by querying for it directly in database then use SQL functions to alter it. I just don't quite understand why you want to encode it then display the encoded version of the field as that basically completely defeats the purpose of encoding it.