Changes on flush not handled by auditor about auditor

[dvdknaap]

@dvdknaap auditor relies on Doctrine changesets to keep track of what was added/updated/deleted/associated/dissociated.

When several onFlush subscribers are registered (which is the case here, there are at least 2 subscribers: auditor's one and yours), if subscribers alter entities and try to persist them but do not explicitly tell Doctrine to update the computed changeset, then changes applied by one subscriber may not/won't be available/visible to other subscribers.

This is discussed in Doctrine documentation

Changing primitive fields or associations requires you to explicitly trigger a re-computation of the changeset of the affected entity. This can be done by calling $unitOfWork->recomputeSingleEntityChangeSet($classMetadata, $entity).

Do you explicitly trigger a re-computation of the changeset in your subscriber?

Hi, thanks for your reply.

I know i'm using unit of works recomputeSingleEntityChangeSet function to tell doctrine there is an change.

I found the issue apparently is unitOfWork is getting new data from the database and triggers postLoad (Events::postLoad) which makes the data readable again because it's an select query so i have to find a way to manual do this so unitOfWork doesn't see a change everytime.

Now it also updating different 'encrypted' entity colomns because it's comparing it with the plain text value that postLoad provided it so this issue it not in your code but in doctrine because of this i shall close this issue

[DamienHarper]

@dvdknaap did you solve your issue on your own?

[dvdknaap]

@DamienHarper
Hadn't test the priority setting yet but it's still not working unfortionatly :(

services.yaml

  App\EventSubscriber\EncryptSubscriber:
    tags:
      - name: 'doctrine.event_subscriber'
        priority: 9999

But in the database it still gives plain text.
{"new":"5yTc8wChiQyTEXi1MtOO5A==","old":"testName"}

"old" should have a base64 string

[DamienHarper]

@dvdknaap auditor relies on Doctrine changesets to keep track of what was added/updated/deleted/associated/dissociated.

When several onFlush subscribers are registered (which is the case here, there are at least 2 subscribers: auditor's one and yours), if subscribers alter entities and try to persist them but do not explicitly tell Doctrine to update the computed changeset, then changes applied by one subscriber may not/won't be available/visible to other subscribers.

This is discussed in Doctrine documentation

Changing primitive fields or associations requires you to explicitly trigger a re-computation of the changeset of the affected entity. This can be done by calling $unitOfWork->recomputeSingleEntityChangeSet($classMetadata, $entity).

Do you explicitly trigger a re-computation of the changeset in your subscriber?