I also have gotten redirected to a "server cannot be found" page when just clicking on the GWW link from my message center. It worked the next time I tried, so I don't think it was a major problem. Just thought I throw that into the discussion in case it's related.
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Earlier today I had trouble threadsucking the first LotR thread. I thought the problem was with my server at work.
Is the Mark function working differently now? I'm (happily) noticing that when I hit it, it brings me back to the post I just marked, placing it at the top of the page I was reading. I seem to recall that this didn't happen before, because I think I remember having to search back through the thread to find my place (which I guess is silly, because I could've just clicked on the bookmarked post to get back, but really not the point here). I think I even remember exchanges (when the user filter was being tested) about how nice it would be if Mark worked like Edit.
And now it does. So, yay. And thanks.
Note: Apologies if the change has already been noted and I just missed it. Or if I'm just imagining things and nothing is different.
Is the Mark function working differently now?
It's working the same for me. It reloads the page I'm visiting and I still need to scroll down to pick up from where I left off.
Really? Wow. Nope, for me it's definitely now marking and shifting on reload so that the marked post is at the top of the page. Which I love. And hope I have not jinxed.
It was doing that for me, but I marked something today and it didn't do that.
No mark code has been changed. But it was noted during the testin (not yet complete, oops) of the block code that it's browser dependent (at the very least) wrt where you end up post-mark.
(As a work around, I click on the post number (which makes the post I'm going to mark, the first post on my page) and then I mark the post.)
What about the threadsuck, well, sucking?
it was noted ... of the block code that it's browser dependent (at the very least) wrt where you end up post-mark
Ah. Thanks. I started to wonder if that might be it. Not that I've changed browsers, but something must be different. Anyway. Mystery solved.