Understanding and using Comment Mover

What Comment Mover does

The results of using Comment Mover make a lot more sense if you know what the module actually does behind the scenes. In reality, Comment Mover (CM) does not “move” topic posts and comments. It creates new comments (or nodes in the case of conversion/“promotion”) and moves the original data into them, placing redirect links where the data was in the original comments or nodes.

The following principle applies consistently:

Common CM Actions and Results

Action: Prune uncommented topic node, graft onto another topic node
Result: Node content transfers to a new comment, receives next available CID
The new comment takes its place in the destination thread according to its CID and your sort order

Action: Prune commented topic node, graft onto another topic node
Result: Node content transfers to a new comment, receives next available CID
Comments move with it (retain their CIDs) and become its children/replies
The new comment takes its place in the destination thread according to its CID and your sort order
The children comments retain their original CIDs and sort accordingly (by CID in flat display. By parent comment then CID in threaded display)

Action: Prune a childless comment, graft onto a topic node
Result: Comment content transfers to a new comment, receives next available CID
The new comment takes its place in the destination thread according to its CID and your sort order

Action: Prune a childless comment, graft onto another comment (with or without children)
Result: Comment content transfers to a new comment, receives next available CID
The new comment becomes the child of the comment it was grafted to, sorts according to it’s new CID (flat display) or according to parent, then CID (threaded display)

Action: Prune a commented with children, graft to a topic node
Result: Comment content transfers to a new comment, receives next available CID
Child comments move with it (retain their CIDs) and remain its children/replies
The new comment takes its place in the destination thread according to its CID and your sort order
The children comments retain their original CIDs and sort accordingly (by CID in flat display. By parent comment then CID in threaded display)