[fixed] Copy Thread Moves Wrong Copy!

[DVD Plaza]

The point of copying a thread is you make a duplicate of it - the original remains unchanged. vBulletin, however, moves the ORIGINAL THREAD into the specified new location and the COPY is the one left where the original was.

In theory this seems like no big deal, they're both identical right? No - all e-mail notifications, moderator alerts, and manual links (on your site, on other sites, in e-mails, etc) will be pointing at the original thread, and that original thread has now suddenly moved.

In our situation, since we make copies of threads before making changes to them (just in case), we make a copy of threads into a private forum - due to vBulletin's quirk this means the ORIGINAL thread is relocated into an area members cannot access, and the COPY is the one that is left behind in its place. Thus all links to that thread now fail.

My point - when making a copy of a thread a NEW COPY should be made (which is what happens) however THAT NEW COPY is the one that needs moving, not the original.

Thanks :)

[Steve Machol]

Confirmed on my unhacked 2.2.8 forum. Moving to Bugs to get feedback from a Developer.

[Scott MacVicar]

fixed for 2.2.9

[DVD Plaza]

Cheers guys - that was quick :)

[eva2000]

vB's always been that way for me .... didn't think much of it.. guess the fix is nice :)

[Erwin]

Yeah, I've lived with this idiosyncratic thing for many versions of vB. :) Good to know it's been "fixed".

[Fusion]

Originally posted by eva2000
vB's always been that way for me .... didn't think much of it.. guess the fix is nice :) Heh, careful, or the fix will confuse you. Bet you'll revert back first chance you get. :D

[aidler]

I assume 2.2.9 will be made public in the next couple of days as the fix to the bug isn't posted here with reference to the 2.2.9 update. :confused:

[Paul]

I think it would be pretty safe to expect 2.2.9 to be released in the near future. Perhaps in the interim the developers would be willing to post the details of the fix here.

[DWZ]

Originally posted by LoveShack
I think it would be pretty safe to expect 2.2.9 to be released in the near future. Perhaps in the interim the developers would be willing to post the details of the fix here. Yeah, I was guessing that too.

Although, it's not running here yet.

[TheEDIGuy]

I reported this one several weeks ago, and I'm glad it's fixed. I assume that this also fixes the "sticky" problem as well? Before = if a thread was stickied, and you copied it, the "original" thread got a new threadid number and was unstuck, and the "new" thread got the old threadid number and was sticky.