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
There's currently no visibility to deletion activity outside of the DB. #1167
Comments
Hi @ezzra, If they still don't show for you please confirm the exact steps you're performing and I'll try to re-produce. |
oops yes did not check this well enough, its actually in the DB tables but still does not show up in the web frontend. I guess that is because of the missing |
Ok I looked it up, it's because of the permissions, obviously the query can't check if a missing object has the necessary permissions, so this will not return the activities of deleted objects:
I'm afraid to fix that, one would have to change the delete process from real cascade deleting to updating the page with a "deleted=true" column. |
Yeah, This is kind of by design. At some point it'd be nice to have a admin-area activity log 'Audit' view where they can see all activities otherwise they'd need to resort to the DB for now. Otherwise we'd be looking to implement #1017 functionality to get to soft-deletes to keep related data, But you'd still have the same issues on permanent delete. |
ah ok good to see that there already is an issue for that, I just wanted to propose that :)
yes true, but this might also be intended when using a permanent delete and there could be a warning/information about that. There could also be implemented a possibility to just remove the content but to keep the metadata. But I guess #1017 is the first and important step |
As of v0.30, There will be an audit log interface included where delete events will be made visible without needing to access the database: Therefore this specific request should be covered. |
If a page is deleted, no entry is added to the activity table but I think its also very much worth to mention this.
The text was updated successfully, but these errors were encountered: