The way it is implemented is that child's controller created from parent's controller, so when parent post is deleted child post lookup fails. In fact, this affects not only delete, but also reply functionality of the child post.
The obvious fix can be that we remove all the children, when parent is deleted. However I don't sure we want to do that. It kinda makes sense, but maybe not :) We'll need a task to cleanup posts that already have deleted parent. I don't sure we can't detect them, though. The second approach is to move handling of reply, delete, etc to the thread controller and always lookup post by full id and not by path from a parent. I guess it will require changes in quite a few places on the UI and test. What do you think? --- ** [tickets:#1731] Cannot delete a post, after deleting its parent** **Status:** in-progress **Milestone:** unreleased **Labels:** 42cc **Created:** Wed Mar 16, 2011 04:56 PM UTC by Dave Brondsema **Last Updated:** Fri Apr 17, 2015 07:04 PM UTC **Owner:** Igor Bondarenko I was trying to clean up the discussion on https://sourceforge.net/p/allura/wiki/FAQ/ and move it into the page proper. I deleted a parent discussion node, and now I cannot delete the children --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
