Very Exciting News: Forum Upgrade Next Week

[Stomme poes]

Freak outs are good. Devs sometimes need some whippin. >:)

[xhtmlcoder]

Certainly, I hope you gave them a good thrashing Sarah and not let they stray from our reasonable and sensible requests. Since we are the people of the community whom will be using the system and interacting with it the most when it goes live.

[hairybob]

It's not too late to go for IPB or Xenforo....

[siteguru]

It's not too late to go for IPB or Xenforo....

Would these easily import a VB3 forum database?

[PhoenixDown]

Yes both IPB and Xenforo will easily import from vb3.

[PhoenixDown]

Don't forget - the original core group aren't there anymore - it's a whole other group that somehow wedged the original team of owners out. The original have started a new company (can't think of what it's called at the moment...)

Two of the lead developers started up Xenforo. I am about to migrate one of my forums over this week. I would've switched already but I've been super busy at the day job.

[TheRaptor]

Has the transfer started? I'm getting "502 Bad Gateway" errors when I try to access certain threads. I've reloaded the page and still the same.

[ScallioXTX]

You've very lucky you haven't encountered the 502 before today; they've been pestering the forums for a while now. And I don't think the upgrade has started just yet

[Mittineague]

The 502's are because of the current server problems, the reason for the upgrade. TBH I'm surprised you haven't gotten them before.

EDIT:
slowhand gets beat again!

[TheRaptor]

Well, I have noticed these issues before, just not like this. There are several threads that I can't view because of this. It only usually took a minute or two before they'd go away and everything would be fine. They seem to be sticking though this time thus the assumption something was happening.

[TheRaptor]

It's getting worse too... now one out of every three threads has this problem. Are the servers dying or something?

[HAWK]

Are the servers dying or something?

The former.

[Stormrider]

Freak outs are good. Devs sometimes need some whippin. >

Don't tell my boss this!

[deathshadow60]

Uhm... "502 - Bad Gateway" should have exactly two things to do with what forum software you are running... and to be frank Jack left town, took his **** with him.

Unless part of the upgrade process is changing what server its hosted on or switching out major hardware and software... What forum software version? If that's what's being pointed at as the cause somebody isn't qualified to be handling your hosting!

[deathshadow60]

Addendum -- when you said that vBull 4 was going to be LESS resource intensive -- especially with all the background ajax bull that effectively doubles the query counts (just to top off the massive increase in bandwidth use) I started to question the competence of your back-end folks. THANK YOU for confirming said suspicion with the explanation of the 502 error.

[Lemon Juice]

I think the devs are putting off the upgrade because they fear the whipping they'll get from the community once the new forum is launched. The criticism of the new sitepoint forum version has started now even before anybody has seen it - imagine what will happen when it's actually here!

[Stormrider]

I've seen it, and I like it!

[ScallioXTX]

I just browsed our new VB4 forum and compared downloads with the current VB3

Page                     VB3             VB4            Difference
------------------------------------------------------------------
Forum index         217.2 KB        123.6 KB      93.6 KB (43.1 %)
 - Cacheable        177.7 KB        105.2 KB      72.5 KB (61.6 %)
 - Download          39.5 KB         18.4 KB      21.2 KB (53.7 %)

My SitePoint        164.2 KB         79.5 KB      84.7 KB (51.6 %)
 - Cacheable        127.9 KB         65.3 KB      62.6 KB (49.0 %)
 - Download          36.3 KB         14.2 KB      22.1 KB (60.9 %)

View forum          229.0 KB        141.2 KB      87.8 KB (38.3 %)
 - Cacheable        173.6 KB        109.0 KB      64.6 KB (37.2 %)
 - Download          55.4 KB         32.2 KB      23.2 KB (41.9 %)

View long thread    433.7 KB        348.8 KB      84.9 KB (19.6 %)
 - Cacheable        368.9 KB        325.9 KB      61.0 KB (16.5 %)
 - Download          64.8 KB         22.9 KB      41.9 KB (64.7 %)
------------------------------------------------------------------
                   1044.1 KB        693.1 KB     351.0 KB (33.6 %)

And there no AJAX calls whatsoever during normal operation (only the quick reply, but VB3 does that as well).

So, I'm really wondering how all you guys came to the conclusion that VB4 uses a load of ajax and has a massive increase in bandwith use ... As you can see above, just browsing around VB4 has a bandwith decrease of about 1/3rd.

Disclaimer: I do not work for SitePoint, and am not involved in/do not have anything to benefit from/etc this upgrade in any way.

[HAWK]

I think the devs are putting off the upgrade because they fear the whipping they'll get from the community once the new forum is launched.

Nope. Frankly, I'm a bit sick of all the negativity! I'm really excited about the launch and am working really hard to do it as quickly as we can - but as with any update this huge, we have to be completely ready.

Addendum -- when you said that vBull 4 was going to be LESS resource intensive -- especially with all the background ajax bull that effectively doubles the query counts (just to top off the massive increase in bandwidth use) I started to question the competence of your back-end folks.

And there no AJAX calls whatsoever during normal operation (only the quick reply, but VB3 does that as well).

So, I'm really wondering how all you guys came to the conclusion that VB4 uses a load of ajax and has a massive increase in bandwith use ... As you can see above, just browsing around VB4 has a bandwith decrease of about 1/3rd.

Thanks Remon. I hope that puts an end to all the rubbish that's being spouted here. I didn't start this thread so that people could sling mud. I'm going to close it now because I think you've made our point.