Site Updates 2020

[Kong Wen]

At the top there use to be a thing that would show all the forum folders I'm in. For example for this thread it would say This Old Neon < Forum Index < Public Council < Site Updates 2020 however now it only says This Old Neon < Forum Index < < this seems like a bug and it's really frustrating if I just want to go back one forum thread to check our threads yet it forces me back to the forum index. There is a work around with the < Return to "Insert thread here" button at the bottom but that only goes back one and not multiples.

Is there anyway of fixing this?

Aye lad, we had it fixed for a time yesterday but that version update introduced new problemos, so we'll get back there soon.

[Kong Wen]

OK, the theme is completely up-to-date now and breadcrumbs are back.

Now I have to get a couple of old disabled extensions back online (custom spoiler functionality and our lightbox for auto-resizing images in the chat).

[Kong Wen]

OK, sheesh, got the spoiler extension added back in again—let's see if it works now that the style sheets are all up to date.

Spoiler

This is a random spoiler.

this is some junk

This is a titled spoiler.

Spoiler

This is a spoiler inside a spoiler:

Spoiler

Hot damn!

[Kong Wen]

I found one! I found a bug still. On the front page of the forum, if you're not signed in, there's a small login section in the footer. Trying to sign in there gives me an error and takes me to the normal dedicated sign-in page. I'll look into this.

[MerlinDrazziw]

I found one! I found a bug still. On the front page of the forum, if you're not signed in, there's a small login section in the footer. Trying to sign in there gives me an error and takes me to the normal dedicated sign-in page. I'll look into this.

Probably a difference in POST (bottom login) vs. GET (login page) when it comes to username and password.
Btw. passwords are sent unencrypted it seems, was this always the case?

[Kong Wen]

Probably a difference in POST (bottom login) vs. GET (login page) when it comes to username and password.
Btw. passwords are sent unencrypted it seems, was this always the case?

Make sure you're visiting and have bookmarked https://thisoldneon.com/forum (https with the s)—that should be secure site-wide. I had a minor scare when I was testing this in another browser and just went to thisoldneon.com/forum and it took me to the unsecure page rather than the secure page

(Which shouldn't be possible, I'm not sure why it does that. We have code to auto-redirect http requests to the https page... I'll have to double-check that it's working. That's a separate issue and only applies to people with TONe bookmarks older than like 2018, but worth looking into.) — I believe I've got this fixed by forcing redirects now, even if you deliberately try to come to the non-secure version of the page.

[Kong Wen]

I found one! I found a bug still. On the front page of the forum, if you're not signed in, there's a small login section in the footer. Trying to sign in there gives me an error and takes me to the normal dedicated sign-in page. I'll look into this.

Just got this one resolved. We're down to very minor, not-front-facing stuff now, or stuff I just haven't found yet.

[MerlinDrazziw]

Probably a difference in POST (bottom login) vs. GET (login page) when it comes to username and password.
Btw. passwords are sent unencrypted it seems, was this always the case?

Make sure you're visiting and have bookmarked https://thisoldneon.com/forum (https with the s)—that should be secure site-wide. I had a minor scare when I was testing this in another browser and just went to thisoldneon.com/forum and it took me to the unsecure page rather than the secure page

I was on the https:// site and checked the network messages in the devtools. That's how I got to the POST vs GET with login and also the readable passwords in the message body vs. query parameters.

[Kong Wen]

Probably a difference in POST (bottom login) vs. GET (login page) when it comes to username and password.
Btw. passwords are sent unencrypted it seems, was this always the case?

Make sure you're visiting and have bookmarked https://thisoldneon.com/forum (https with the s)—that should be secure site-wide. I had a minor scare when I was testing this in another browser and just went to thisoldneon.com/forum and it took me to the unsecure page rather than the secure page

I was on the https:// site and checked the network messages in the devtools. That's how I got to the POST vs GET with login and also the readable passwords in the message body vs. query parameters.

Ah the post & get things are browser language. I think the difference in how the site login handles them here is because the full login page is a navigable page in your browser history, whereas the quick login at the bottom of the index page will load and dump you right at the forum index page on successful login. The reason it wasn't working is because I missed a JS token when updating this specific page but not the other pages.

Not sure what you mean or what you're seeing about the password encryption, but nothing there has technically changed since the installation of the SSL cert, whenever that was.