Does anyone know if Elgg core trac ticket #607 and the related fix is covering the issue of orphaned files? i.e. you delete a user, but their files are left behind and visible in the "All sites files" view. These files are not attributed to any user. If you click on the file, a blank page is displayed.
I also can't tell where this fix is being applied - so is this part of Elgg 1.7?
Thanks.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- DhrupDeScoop@Dhrup2000
DhrupDeScoop - 0 likes
- Brett@brett.profitt
Brett - 0 likes
- Kevin Jardine@kevin
Kevin Jardine - 0 likes
- Kevin Jardine@kevin
Kevin Jardine - 0 likes
You must log in to post replies.http://community.elgg.org/mod/groups/topicposts.php?topic=390431&group_guid=52477
If you look at the very last comment on the ticket you'll see when the fix was committed--changeset 3700, which was about 3 months ago so it will be in 1.7.
This fix doesn't affect the database, but deleting a user should remove all entities owned or contained by that user.
James' report implies that orphan file references *are* left behind in the database (and not just on the file system).
As this should be impossible even under Elgg 1.6.1, it would useful to get some understanding of how this could be happening.
James, what version of Elgg are you running?
I think that if an admin deactivates the file plugin, deletes a user with files, and then reactivates the file plugin, you might see the behaviour James describes.