you can edit the field value with simple code in skeleton plugin:

$data['field1']=$data['field2'];

is similar to the reset of the fields that you use.

Also you can do some operation or counter.

example for counter:

$data['field']=$data['field']+1;

When user update their profile, Easy Profile launch the trigger for each changed field.

If there are some field changed at the end launch triggerProfileUpdate.

When one triggerFieldxxxxxxUpdate is triggered always is trigger also triggerProfileUpdate

I will explain with an example:

triggerProfileUpdate($user,$data,$changed,$isNew){

    if(in_array('accessrequest',$changed))

    {

        //CODE

    }

}

is the same as

triggerFieldAccessrequestUpdate($user,$data,$changed,$isNew){

        //CODE

}

Thank you, this clarified enough for me to implement and test, and all looks good. One additional question, and again should be easy. Is it possible, and if so, how is it possible to change a field to read only from within the skeleton plugin trigger routines I have written? Being able to do this would be very helpful.

Ken

The same way to edit other field, add $data['alias_of_readoly_field']='value';

Perfect, thank you. Your product is so very good and capable, and the support is second to none! Honestly, great job.

Ken

is this changing the field or changing its property to "readonly"?

this row only assign a value to a field (whether that is readonly or not).

What i think will work is to have an additional action to apply on a condition parameter

Yes, we plan in future to implement in condition possibility to change readonly and required status

What I want to achieve is this

the easiest way is this: you must create a field(integer,text or what do you prefer) to check if privileges are assigned or not, set this field in skeleton plugin to 1; set condition for this field to hide access request field if equal to 1; set this field hidden on profile,edit and registration page.

also, if you want to see access request on profile you can create 3 HTML delimiter field:
title,description,Access Level (dropdown field in edit field page on the right)
Access Request,Buyer,Buyer Access Level
Access Request,Seller, Seller Access Level
Access Request,Subscriber, Subscriber Access Level

first you must create Access Level for Buyer, Seller and Subscriber groups from Administration->User->Access Level

But thank you, once again. In the future, I look forward to this being managed by parameter conditions that also manage READONLY and REQUIRED properties, but for now I think your thoughts combined with mine have set me on the correct path to implement. Thanks very much.

Ken

Easy Profile Support wrote:
Yes, we plan in future to implement in condition possibility to change readonly and required status

Hi, another vote for this feature. Would love to see some hidden fields be not required that switch to required when they become visible due to condition.

Hi,
You can already do this.
If a required field is hidden by a condition become not required. When return visible become required

Easy Profile Support wrote:

Hi,
You can already do this.
If a required field is hidden by a condition become not required. When return visible become required

You're right. It seems I was mistaken. This component is great, thanks for the good work.