New Forum FAQ
How do I report bugs?
You can send me a PM (send it to Max) with a screenshot or explanation, or post in this thread.
Yeah, not sure why those posts got merged into this thread. It's definitely not just a new skin problem.
***
Edit/MH: Corrected my merge error. Moved posts back to this stand-alone thread.
maybe to redirect people to the new forum, which isnt getting as much love/attention because its quite terrible
the new skin has many problems
the old skin only has one, but for the last 24h its been working fine for me
Lol I only just started lurking in 2p2 again a few months ago on my burner account (after deserting for years). Didn’t even know this happened until just now - I clicked on a thread that forced me into some weird interface (didn’t learn until later it was the new “twoplustwo.com”😉. Why it auto-forced me there, I have no idea- I was logged onto the old interface the whole time up to that point- all I did was click on a perfectly normal thread. Anyways, I DMed someone while on the new interface. Logged off for a bit, logged back on (through the original forumserver interface), and the DM does NOT show up in my sent messages. I went back to that thread, and it did NOT force me to the new interface (bug?). I got so confused that I thought maybe I just never sent the DM.
That’s when I dug a little more, learned about this whole new thing, tried logging onto the new 2p2, and saw the DM there.
Tl;dr- if you send a DM in one and not the other, it won’t show in both?? What if the person I sent it to doesn’t use the new 2p2??
Unrelated. One thing I’ve noticed in the past couple years of spontaneous on and off lurking- I also occasionally get the 504 Gateway Timeout message. But if I go and log in through an incognito window at that same time, I have no login issues. No idea why but the workaround has worked for me for a while now.
There are multiple studies that suggest reading is most comfortable when lines are limited to a certain number of characters. I think it's 55 to 70 characters for books, and it might be a little bigger for online content. On the old forum software, you can read lines of about 280 characters. I get the appeal—you don't have to scroll as much, and everything looks compact. But
Is there a way to see, that a thread will take you to the new forum before clicking it? Or even better, can I make so that I never see threads made in the new forum? I really really hate it, and never want to use it no matter what.
Is there a way to see, that a thread will take you to the new forum before clicking it?
There used to be, but it got removed for whatever reason. When it was around I would actively avoid clicking on threads marked as the new forum but now sometimes get tricked into visiting there.
There's been a big trend of this over the last 10 years. The large popular forums that are still around trying to move off vbulletin onto their own platforms. They always seem to face huge backlash in doing so as users love vbulletin. No idea why the owners are united in moving to their own platforms but I presume its a cost/control thing such is the way of the world - and its completely understandable.
I've always tried the "new" forums but its never the same and just not as good. It's not a resistance to change either. Vbulletin has been honed over many many years and is always superior for the experienced user to what comes instead. If/Whenever the old forum is switched off here it will be sad times and a major rip, I won't be sticking around.
If you're going to have a link that says "Read X on the new forum" the link should at least go to the correct part of the new forum. It gives the new software bad look when you just get this confusing mishmash of random posts when you click that banner.
I have no interest in using the new forum setup, as it seems like more trouble and I think everything was nearly perfect as is.
Usually everything is working for me as normal, but occasionally I click on a thread (in the old forum setup), and it takes me to the posts in the new forum setup.
Every- time I try to go to that thread again, the same thing happens.
Even worse, I can't reply to anything in that thread, as it tells me that I need to log in first. I am already logged in as I always have been, and I have no idea how to log in on the new forum. I would prefer not to even have to know how to do that though, I really just want to know why this is happening sometimes and if it can be fixed. Thanks!
I have no interest in using the new forum setup, as it seems like more trouble and I think everything was nearly perfect as is.Usually everything is working for me as normal, but occasionally I click on a thread (in the old forum setup), and it takes me to the posts in the new forum setup.Every- time I try to go to that thread again, the same thing happens.Even worse, I can't r
This will let you read such a thread in the old forum:
I have this problem, too. Until it's fixed, the simple workaround I have used so far is to click on the OP's username, then click on the relevant post [or thread] by that user - which opens the thread in the old forum format.
You can then also post in the thread using the old forum method.
It works but it is a quite annoying workaround.
Will it be possible in the future to have an option to see anything in the "old style"?
Even worse, I can't reply to anything in that thread, as it tells me that I need to log in first. I am already logged in as I always have been, and I have no idea how to log in on the new forum. I would prefer not to even have to know how to do that though, I really just want to know why this is happening sometimes and if it can be fixed. Thanks!
Yeah I have seen that too. Not interested in logging in to the new forum. The only way I can read the forums is on my phone on tapatalk which sometimes is very clunky to see as it is often freezes when you want to scroll up or down a thread (although seems to be better recently). Although still annoying that I have to as 75% of my 2+2 time is now non-phone.
The same username and password you use to log in to the VBulletin forum can be used to log in to the new forum
What part of "not interested" don't you understand?
It's pretty clear that this changeover is unwanted and unnecessary. Why can't website administrators ever get "if it ain't broke, don't fix it"?
New forum replying to a post opens a reply window that doesn't let me see or refer to the OP. Is the expectation that I memorize the OP before composing replies? I see a "quote" button at the bottom of replies already made but I don't see how to quote an OP in a reply (no button).
Old forum OP had a quote button and, if desired, I can draft a response in Quick Reply window while scrolling up to refer to OP.
Old Forum > New Forum
Workaround: Have a **** while you wait?
I'm getting a Cloudfare error page today:
SSL handshake failed Error code 525
You:
Browser
Working
London:
Cloudflare
Working
forumserver.twoplustwo.com:
Host
Error
What happened?
Cloudflare is unable to establish an SSL connection to the origin server.
What can I do?
If you're a visitor of this website:
Please try again in a few minutes.
If you're the owner of this website:
It appears that the SSL configuration used is not compatible with Cloudflare. This could happen for a several reasons, including no shared cipher suites. Additional troubleshooting information here.
Yep. I was thinking I need to exchange numbers with people I'd like to keep in touch with, because I can't imagine dealing with this for long. Seems fine now, but this morning it was the worst. Seems to be bad every morning, clearing up around midday for whatever reason.
Interestingly enough, its been fine for me since I made this post. Hope it continues.
For me, its more often getting errors than working
Yeah, Max has changed some settings in cloudflare that hopefully will clear up the issues. So far so good.
I've been getting a CAPTCHA nearly every time I refresh the old site (forumserver.twoplustwo.com) starting right around the time the slow loading problem appeared. Doesn't seem to be a problem with the new site. Happens in both Firefox and Chrome on Linux.
