Error
Anybody know why the main page was screwed up last night? How was it fixed?
Anybody know why the main page was screwed up last night? How was it fixed?
Presumably unrelatedly, the IRC box in the sidebar is also broken - even if it says “Talking: Nobody.”, there may be some people in there.
The sidebar was visible, but the list of blog posts was replaced by an error message reading “Parse error: syntax error, unexpected T_STRING in /home/.magnum/blognomic/www/ee/system/core/core.functions.php(634) : eval()‘d code on line 87”. Other posts could be read and commented on through the sidebar, except for the Crisis Proposal in question, which displayed the same error message instead of the blog entry (although it could still be commented on).
Hmm… do you mind if I briefly revert that post back to how it was when it caused problems to see it myself?
No, go for it. Stick an explanation in the blog header if you’re going to be playing around for more than a few minutes, though.
Yeah, lets split up this problem.
> (whether you clicked through any of the settings before posting, or made it from a particularly unexpected web browser), Keba?
I was using Firefox 3.5 on Ubuntu 9.10 and I have not changed anything, if I remember correctly. I postet another Proposal a few minutes before this “bad” one, so I dont think its the fault of my browser or OS.
hm, there was the same error after posting the last comment. After a couple of minutes the website was useable again.
That’s because Wakukee was briefly reverting that post back to how it was when it caused problems to see it himself.
The problem is definitely related to the “posts” template, perhaps at line 64 which is
if($mystatus != “open”) {
. Perhaos you could look at this template, Kev?
@Kevan: as for the IRC box, normish.org’s DNS registration lapsed. The server behind it is still there, at IP 209.20.80.194, but doesn’t currently have a name.
Kevan: Concierge he/him
This proposal broke it; I was only able to fix it by removing the flavour text entirely, and haven’t had time to go through exhaustively to work out which line or character broke it.
I’m not aware of such a problem ever arising before. Was there anything particularly different about this post (whether you clicked through any of the settings before posting, or made it from a particularly unexpected web browser), Keba? It did seem to have its timestamp set back eight hours, which Keba says he didn’t do - I don’t know whether another admin made that change in an attempt to fix the bug…