Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Moving threads isn't working. We are missing a wealth of mirth and merryment in General because of it. We need it now!
That's been a really tricky one to work out a way around, but it's almost there now
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
That's been a really tricky one to work out a way around, but it's almost there now
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
I have absolutely no idea what that means but it looks good. You da man.
And the caching of the threads so the latest thread shows when viewing the forum home page?
'CUK forum personality of 2011 - Winner - Yes really!!!!
Comment