-
Notifications
You must be signed in to change notification settings - Fork 380
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
Loggable with softdeleteable and uploadable #256
Comments
Hi, For Uploadable:
And for Loggable:
After seeing this, I was surprised why Loggable have a higher priority than Uploadable (5 >> -5). So I was forced to switch priorities. I'm not sure about choosing the right priorities but I think that It's prefereable for me to keep priorities under the default (default=0) because most listeners have a default priorities even the kernel.controller event-dispatcher. Just keep a look at this command to understand:
So I just set the Uploadable priority to -5 and the Loggable priority to -7 (it's a choice). And after uploading a file, I found the file info in the "ext_log_entries" table. To do set these priorities, I overrited the listeners in the config/services.yaml (for Symfony 4).
I hope this can help anyone that found this problem like me. And please if I said wrong concepts or any thing that should be corrected, don't hesitate to keep me informed. Best regards |
Hi,
I'm trying to use this three extensions together, but i have some issues.
First of all, i tried updating report entity which params: path and size are versioned, but no changes are logged.
After creating new entity, there is create action logged, but path and size params are logged as nulls.
I tried messing around with listener priorities.
I changed uploadable priority which fixed the update action versioning, but screwed up soft delete logging (remove).
Tried to change softdeleteable priority, but it doesn't change anything apart from totally screwing up softdelete (the file is being deleted)
Just can't get these three to work with each other
The text was updated successfully, but these errors were encountered: