Plugin "Entity: set field value" not working if using token for new field value

Will have a look at this.

The underlying problem here is, that a nested update of the same entity is happening, since the model reacts upon the "Update content entity" event. I was wondering why the infinite recursion detection was not kicking in here, and it turns out that the entity system relies on values of the original object. On a nested update, the values of the attached original object can be out of date. For this case, I've added a refresh of the original object in the update action (see MR296).

To prevent the infinite recursion, you could work this a token that is being exposed as context. I've added this to your example model (see uploaded file attachment).

I think it makes sense to also add this to the generic save action. Will have a look.

OMG, I completely missed the recursion myself. So glad you caught this, and the resolution looks perfect.

Merged into 1.2.x and back ported to 1.1.x - thanks @mxh for your help on this.

You're welcome, glad I could help.

This needs a backport to 1.0.x as well.

Good point, done that.

Automatically closed - issue fixed for 2 weeks with no activity.