Originally posted by northernladuk
View Post
I'm surprised the vBulletin developers never caught it though. The problem is that when threads or posts are moved, it tries to invalidate its internal cache for everything beneath the relevant things; but that includes the subforums themselves. So if, for example, you try to move a thread from Technical to General, it tries to build an array containing an ID for every single post in both of those subforums (and anything beneath) and, unsurprisingly given there are several million of them, the process exhausts its available memory and crashes.
At this point things have been moved, so that's not a huge issue; the mods get an error message, which isn't perfect, but may be bearable. But the problem is that the necessary changes to fix up the URLs haven't happened yet.
I've finally established a point in the internal APIs where I can safely override the default behaviour so it'll run successfully to completion, at which point it's safe for my extension code to fix the URLs. So it shouldn't be long before the mods can resume casting the unwary out of the safe havens of the professional forums into the pit of General
Come clean, admin forced you into releasing before it was ready. Wink twice if you're being made to work on it against your will? 
Leave a comment: