navigate

server side failure

the site has gone bananas, and for no reason at all. i have done nothing to the sources or the database structure in like 1.5 years, and all of a sudden it throws query errors all over the place. methinks the priovider has done an update to mysql or some such. i'd rather not believe such a great open source project would suddenly spawn a release that isn't backwards compatible with one of its precedents, but i have no other explanation for the trauma my precious website is currently sustaining.

anyway, i'll try to figure something out and fix it for the approximately 2 people a day that visit. mainly because one of those people is usually me... i've already looked into it briefly, but found no quick and easy way to get around this. i may have to partially destroy the core page's ultra-neat search functions. which is a shame.

posted by cadra at Dec 22, 2008 16:34

at least the forum still works, eh? :)

(but on the other hand, comments do not.)

posted by cadra at Dec 22, 2008 16:35

at least the forum still works, eh? :)

...partially... :/ though it's only the send-back-to-what-you-just-posted bit (for lack of a better term), so the posting process itself is intact. ok, i'm gonna stop talking to myself now.

posted by cadra at Dec 22, 2008 16:38

Good luck fixing it, I just found this website and I hope you can get it back up and running.

posted by Kevin at Jan 4, 2009 5:02

(lot of cursing going on)

...

posted by cadra at Jan 4, 2009 17:22

throwing elegance to the wind pays off, it would seem: the goto-post (and, in a minute, goto-comment) bits are back to their functional self, albeit in 2 stept instead of 1.

the real deal is the "core". even if i'd choose to go the easy way and destroy the search-code as it is, it's going to take time. ugh.

posted by cadra at Jan 4, 2009 17:38

boom. part of the "core" is now broken. you can't see the tracks, comments or poster from the main view. i killed all the subqueries, because for some reason mysql5 treats those differently from earlier versions and refuses to eat my code, being written for 3.23...

sad fact is that i don't care enough to fix it properly; besides, i'm working on a new and even more spartan site. (which may still take years to complete, after all i'm not in school anymore.)

posted by cadra at Jan 4, 2009 21:59

The site seems fixed, thanks for your hard work. I'm not sure how many people visit this site but I hope I haven't inconvenienced you in anyway. I look forward to listening to the tracks of this label, too bad I'm pretty busy with school.

posted by Kevin at Jan 8, 2009 0:33

well, it wasn't that hard... it turns out the new mysql (to which my hosting company upgraded without informing me -- i didn't get so much as an email) is pickier about left join syntax, which this site uses a lot. they did this to be more compatible with other sql packages. the only problem is, my (apparently sloppy) queries stopped working because of this. i haven't taken the time to figure out how i should be doing it yet, and i'm in cambodia right now, so i can't really sit down with my code and a cup of coffee -- but i'll be back 8 days from now, and sometime after that i'll get to it eventually.

eh, enough tech-talk. i'm on vacation for crying out loud.

posted by cadra at Jan 30, 2009 14:42

[ login | register ]

[ optional ]

[ required - this stops spambots ]


please consider what you're posting and do it in english. use bbc, not html.
spam will be deleted, so don't bother (also: get a life).