New Forum Bug Reports

[SueEllen]

Some thread links return a 404. Like SueEllens link about SYL's libel case today.


https://forums.contractoruk.com/gene...his-libel-case

Yep no-one moved the thread.

Interestingly if mentioning him is banned how comes you can see the link if you hover over my thread title?

[vetran]

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?

I fell asleep half way through as NLyUK will tell you is common!

But I for one trust Nick!

[vetran]

Some thread links return a 404. Like SueEllens link about SYL's libel case today.


https://forums.contractoruk.com/gene...his-libel-case

[northernladuk]

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?

[NickFitz]

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

[northernladuk]

Moving threads isn't working. We are missing a wealth of mirth and merryment in General because of it. We need it now!

[d000hg]

I'm working on it…

For a loooong time 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?

[NickFitz]

So it's been a few months, do we conclude CUK forum is like Windows and we just need to wait for the next major version?

I'm working on it…

[d000hg]

So it's been a few months, do we conclude CUK forum is like Windows and we just need to wait for the next major version?

[NickFitz]

Somethings not quite right...

Admin was having problems setting up the notice - the save button didn't seem to be working, but behind the scenes, it was