So ... it looks like it is sending down a whole pile of HTML that does contain the page, but then does something that convinces the browser to display a blank page instead. I had other things on the cards for today.
The HTML being sent looks broken (chunks missing) for some reason not clear at present.
So, it looks like vBulletin (or perhaps the content in one of the posts) is trying to interface with a Facebook API which is failing. Cause of the failure would seem to be some version incompatibility according to the error message I can see when quizzing the browser about what's going on. There is also some problem with accessing some "skim link" service, though this is only flagged as a warning, so I wouldn't have expected this to kill off the whole page.
Can this be fixed? Probably not in the immediate future. This feels like it is quite deep into the mechanics of vBulletin and certainly outside my direct experience.
My best guess is that Facebook have changed their API, which is reasonable for them to do. It looks like their current API version is 3.2, and our version of vBulletin is calling them using v2.2. Facebook maintain a range of previous API releases they continue to support, but eventually they will drop the oldest. It's possible that this has just happened to v2.2.
There was another possible explanation for this "white screen" from vB' but in light of the error messages seen I am not placing this at the top of the probable causes list.
Last words for the time being: If you go to page two of the thread, then select "Thread Tools -> Show printable version" and then go backwards to page 1, you can see the content (albeit in printable form). hmm.
Maybe it's fixed. I can see that section of the thread now. The cause? Probably some errant HTML code that Alan accidentally slipped into his post when editing it. Not Alans fault, vBulletin should automatically strip it out, but didn't. A bug at the end of the day.
Could somebody confirm it's OK now. Ta.
Reply With Quote
Bookmarks