good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Nodes that got reaped before they had any replies used to just completely disappear without a trace. A few rather serious bugs were found with that so the behavior was changed as a temporary solution. I'd like to have that behavior restored (with the bug fixed) when vroom or a duely appointed helper gets the time. I'd also like the reaping of a node that has replies that have all been reaped to rereap the whole subtree of replies from the bottom up so the nodes are "just gone" and then move up to the parent node and rereap it if it was previously reaped but was hanging around because of this reply. Perhaps the easiest solution for all of this is just a cron job that looks for recently (but not too recently) reaped nodes and purges any subtrees of nodes that contain only reaped nodes. "not too recently" means don't purge a reaped node if it is currently the last node of the site as that is what triggers the nasty bugs. - tye (but my friends call me "Tye")In reply to (tye)Re: Hiding Reaped Nodes
by tye
|
|