actually I'm not as sure now. I know it recalculates the last poster info, but it might not recalculate the topic starter info.

from what i've tested, we still have a wee bit of work to do. and we need to do it in two places, since inline moderation has it's own body of code.

meh, still calls rebuild_topic_data, so we'd probably either modify that function or give it a helper function.

Merge for me works like expected. 2 topics get merged together. Appending topic A to B would be a different function.

i'm ok with that. makes a lot of sense to use one routine or routine + helper for both.

what i really would want at some point is to join the bodies themselves as much as can be. prime example is PMing a user on topic move/merge. right now one body does it, but the other doesn't and if we keep adding ancilliary stuff to them, it would be wise to get as much in common as possible to begin with.

I still maintain that "merge to" implies some kind of parent and child relationship.

In other words, I would expect merge topic A to topic B to yield a different result to merging topic B to topic A. The main difference being that the topic being merged "to" is the parent.

But from what you're saying, you expect the result to be the same.

My only issue is that the parent, or very first post, of the topic you're merging "to" isn't upheld if one of the merged posts happens to be newer.

Just a note ive noticed a bug within a hidden forum set up
ive posted it here. Click Me