What changed?

Super Firebug · August 12, 2015, 05:29:39 AM

I was going to ask why I now couldn't read hidden "spoiler" sections of posts, no matter how much I clicked on "Show". (It used to be that I only needed to have Javascript on in order to show them.) But, when I logged in, I could then read them as before. So now, my question is, "Why do we now have to be logged in in order to read hidden sections of posts? What's the benefit there?"

Aggelakis · August 12, 2015, 05:48:51 PM

Spoiler for Hidden:

Aggelakis · August 12, 2015, 05:49:44 PM

Confirming. Paging Sekoia :)

Noyjitat · August 12, 2015, 10:51:23 PM

Most torrent communities require you to be logged in to see download links using same feature that they call spoiler here. I would guess it was part of a recent forum software update and needs to be disabled. Perhaps it was enabled sometime when they downgraded the titan server sometime ago?

Paragon Avenger · August 13, 2015, 01:25:39 AM

Do we really want

Spoiler for Hidden:

to see spoiler text? After all, they're not even logged in.

Valtyr · August 13, 2015, 01:39:11 AM

Do you want

Spoiler for Hidden:

Because that's how you get

Spoiler for Hidden:

Paragon Avenger · August 13, 2015, 03:23:46 AM

What kind of

Spoiler for Hidden:

are we talking about here?

Codewalker · August 13, 2015, 03:32:36 AM

They aren't working for me even when logged in, so I think they're just broken in general. I can, however, quote the post and see what's in the spoilers that way.

Chances are the seeming disparity has something to do with cached css/javascript that might be referenced by a different URL when logged out, making it seem to be related.

Super Firebug · August 13, 2015, 05:23:53 AM

Quote from: Codewalker on August 13, 2015, 03:32:36 AM
They aren't working for me even when logged in, so I think they're just broken in general. I can, however, quote the post and see what's in the spoilers that way.

If nothing else works, you can right-click, elect to see the page's source code, and read it that way. (At least, that works for me in Firefox.)

Sekoia · August 13, 2015, 02:32:00 PM

Thanks for the report. I believe I found and fixed the error. Please let me know if you still see the issue persisting anywhere. :)

Paragon Avenger · August 14, 2015, 02:13:31 AM

Quote from: Sekoia on August 13, 2015, 02:32:00 PM
Thanks for the report. I believe I found and fixed the error. Please let me know if you still see the issue persisting anywhere. :)

Let me guess, it was a semicolon missing or in the wrong place; those <expletive> semicolons.