Forum seems to be broken mostly on desktop, but mobile also not reflecting posts current also. Neat, page continually reloads on desktop, it is on a loop..

Nope, not just you. @Robb M.

Same here(I've been to this thread three times and it still shows unread)

It doesn't show new posts. You can go into a thread and not see new posts. Refresh the thread and then see new posts.

I knew they were jacking up the site earlier.

They really did it this time.

@Robb M.

can confirm. on it.

Dude. You guys are incredible. I've been on forums since about.... 2001ish. I've never in my entire life seen a forum as consistently broken as this one.

This is the bottom of the page. I can't scroll any farther. I can't see Tom's message, i can't reply, nothing.

@Robb M.

https://farm8.staticflickr.com/7874/...4ca3ccff_b.jpg
MT forums support team is bad by concealer404, on Flickr

Can we just do a hard reset to how the forum was the day before this thread started? And then just not touch it?

Where is that happening? I haven't been able to replicate yet.

Randomly about 1 in 4 threads yesterday. Isn't doing it today so far, but i'm sure we'll find something else stupid by end of day.

thanks for that, please tag me in any thread it happens in if you see it again.

Well, i can't. Because you see, in the case where that happens, i can't get to the "reply" button.

It appears as though you could use the quote button on the last visible post to successfully tag me.

Oh good call. This is why we have you around.

Is the site broke?

When I go to "new posts" and click on the post I want to view I get a database error.

This is on mobile on the full site. Don't see issues navigating to the thread I want manually. I will update if I see anything else unusual.

Seems to be working here. Can you link me to a thread that doesn’t work for you please?

Nevermind. It either fixed itself or it was just on my end...

:bigtu:

Kitty picture for tax.

https://cimg2.ibsrv.net/gimg/www.mia...c29cc6959a.jpg

https://cimg9.ibsrv.net/gimg/www.mia...923d76c17.jpeg

It WAS happening earlier, must have corrected itself.

We did a software update today, may have been during the update.