Posted by vvrabie on March 31, 2008 at 4:29am
| Project: | Apply for role |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
one more issue for you, Soren.
if the user was deleted, it's impossible to delete its role applications.
Comments
#1
Vitalie,
Thank you!
#2
I don't have much time now. This should take care of the problem in the future. It doesn't deal with the orphans, now. If you have access to your database, you can delete them by hand. I'll try to get around to an orphan function later this week.
Thanks, again!
#3
Fixed in 5 and 6 -dev. But I'm leaving this as active as a reminder to myself until there's also a fix for orphaned applications.
#4
this should do the trick for D6. you might want to bump the update number down to 5000 something so you can also commit it to the D5 branch and avoid having it run multiple times... thought it wouldn't really matter.
#5
#6
Automatically closed -- issue fixed for 2 weeks with no activity.
#7
Since I haven't thought of anything better and it was a waste not to use this in the first place...applying to the next release.
#8
This was fixed in 6 in commit #108507 and in 5 in commit #108516. The issue is that there isn't currently a way to identify and delete orphaned applications. As the bug has been fixed, I'm changing this to a task. We shouldn't ever run into this problem again, but a) we should have a test for it and b) we should check for orphaned applications and delete them.