Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue @Gedmo\Blameable(on="update") set NULL value #371

Open
ArturTovmasyan opened this issue Jun 21, 2018 · 3 comments
Open

Issue @Gedmo\Blameable(on="update") set NULL value #371

ArturTovmasyan opened this issue Jun 21, 2018 · 3 comments

Comments

@ArturTovmasyan
Copy link

ArturTovmasyan commented Jun 21, 2018

When i run my symfony2 command, and in command i change DB data, after flush update field is NULL, but create field is ok, why? But not CLI process, all is ok!

@dracken
Copy link

dracken commented May 8, 2019

We're having the same behavior, using YAML. We're also using timestampable, which is working on both create and update. Being that this is nearly a year old, @stof, has any maintainer reviewed this issue?

createdBy: gedmo: blameable: on: create works
updatedBy: gedmo: blameable: on: update fails with a null value

Another issue is also open, looks like a duplicate.
#387

@ArturTovmasyan
Copy link
Author

Thanks for answer.

@janklan
Copy link

janklan commented Jul 6, 2021

Not sure how relevant it is, but I had a similar issue - I did not work out the exact cause, but while searching for it, I found that I was configuring the Blameable behaviour directly in my service definition. At first I was using Gedmo directly, then I switched to Stof's bundle. I removed the service definitions and my issue went away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants