The site went down for a while due to a DDoS attack on the data center housing the Linode, Linode has informed me.

I have a notification that will not leave, even when I viewed its source

Weird. I haven't changed the notification code. What is the notification a notification of?

This
post/822416/The-headcanon-thread/#822416
I even marked them all read and yet it's still there

Sounds like the same thing that has left me with a fixed [1] PM notification, even when I've read them all.

And now its suddenly vanished

I dealt with the PM thing by clicking the "mark all messages read" option.

Maybe it's just mobile but clicking the EvaWiki link does nothing today.

Sailor Star Dust wrote:Maybe it's just mobile but clicking the EvaWiki link does nothing today.

It works at it should on my desktop (using Firefox).

Yep, EvaWiki link on mobile still just goes to/stays on the forums.

Sailor Star Dust wrote:Yep, EvaWiki link on mobile still just goes to/stays on the forums.

Works for me. I'm on mobile right now. Maybe your browser is rejecting it because it's an https link using a self-signed certificate.

I just tested it on my phone and can conform SSD's claims: the wiki link does indeed take me right back to the EGF homepage.

Any of EGF's self-signed certificate stuff I have to give the OK on mobile or laptop so I don't believe it's that.

Both of the browsers on my phone have no trouble with the link. What's everyone else using?

I can confirm the issue on my phone; later this evening I'll have a look to see whether it's a consequence of my rearrangement of the main menu, which frankly seems the most likely cause - I've taken almost no account of the "responsive" part of the theme coding which rearranges stuff on small screens, so I could easily have got something wrong in there, or just plain missed it.

EDIT:
Completely mystified right now. Safari in iOS 9.2 shows the correct URL if I tap and hold the link. It loads it correctly if I say to load in a new tab, but not if I say to open in the same tab. The simple click action should be to open in a new tab, but this isn't happening either. Changing the link to http instead of https removes the obvious security message when the link is being opened but does not change the overall behaviour, so the certificate is not the reason for this.

Something I noticed by chance: Trying to unsubscribe from a topic (Topic Tools next to Post Reply) gave me an AJAX error. Don't believe I get email alerts for topics these days so I'm not sure if unsubscribing via email link would work, anyway.

EDIT: Looks like it fixed itself? Leaving post here in case anybody else runs into this problem.

Some of those tools come up with an "insecure redirect" message and a page full of supporting diagnostics -- those have worked, but stumbled at the last hurdle trying to get you to an updated page.

The URL rewrite extension I created doesn't play nice with some other pieces of the software, such as the AJAX stuff (a subject I don't know yet to boot). I once tried to figure out why it was breaking the moderators-only quicktools but gave up after hours without progress. It was hard enough to get working as it does now that I haven't been willing since to dive back in to try to figure out why it's breaking these other things.

Also so everyone knows in case I forgot to mention it anywhere else publicly, I'm on family vacation until the 9th. I'm actually posting from the condo we're staying at right now.

Mr. Tines wrote:Some of those tools come up with an "insecure redirect" message and a page full of supporting diagnostics -- those have worked, but stumbled at the last hurdle trying to get you to an updated page.

Basically, if you get this sort of thing (many file/line/call records omitted), whatever you did worked, apart from getting you to the page you wanted

pwhodges pointed out to me a case where a topic page breaks partway through, causing a very obvious visual anomaly. It's the second instance I've seen of what turns out to be a result of closing BBCode tags in the wrong order. If you have a quote box that encloses a spoiler box, close that spoiler box before the enclosing quote, or it'll break the page.