X Xon Well-known member Aug 27, 2015 #1 XenForo_Model_Post::_moveOrCopyPosts calls rebuildDiscussion() on all source threads, regardless of if it is a move or copy operation. This causes copying posts from a massively long thread to take an unexpectedly long time.
XenForo_Model_Post::_moveOrCopyPosts calls rebuildDiscussion() on all source threads, regardless of if it is a move or copy operation. This causes copying posts from a massively long thread to take an unexpectedly long time.
m1ne Well-known member Aug 27, 2015 #2 Define massively long, I have a thread with 3500 replies and would like to test that.
X Xon Well-known member Aug 27, 2015 #3 Solidus said: Define massively long, I have a thread with 3500 replies and would like to test that. Click to expand... It was a thread with ~58000 replies. I'm aware that is longer than most normal threads!
Solidus said: Define massively long, I have a thread with 3500 replies and would like to test that. Click to expand... It was a thread with ~58000 replies. I'm aware that is longer than most normal threads!
R rdn Well-known member Aug 27, 2015 #4 My top replied thread is only: 14, 355 10, 619 7, 796 So I will try this one too.
R rdn Well-known member Aug 27, 2015 #5 RoldanLT said: 14, 355 Click to expand... Tried, and it was quick for me.
Daniel Hood Well-known member Aug 27, 2015 #6 Regardless of speed, it's still an unnecessary task. There's no need to rebuild thread data for threads that weren't modified (moving makes sense, copying does not).
Regardless of speed, it's still an unnecessary task. There's no need to rebuild thread data for threads that weren't modified (moving makes sense, copying does not).