The forum is going to be jumping half away around the "World" (that is in American terms from Iowa to Atlanta) sometime in the next 2 days.
This should be fairly transparent. By "Fairly" I mean you'll might think, for a short period of time, the site has been attacked by a large bulldozer (or that Tart has released a new skin).
If something goes wrong - you know who to blame. (Pedro of course)
Dan
Full Version: Badgerfest Moving Servers
well it died for a bit but it should be back soon.
testing, testing, one, two two, tew chew, testing yeah yeah, twoooo, hey hey twoo.
yeah i think it works dan
yeah i think it works dan
well - the forum works.
the front page doesn't though.
not got a lot of time to fix it at the moment. Anyone with time and php knowledge, email me for the ftp password and i'll send it over. Looks like it might be some database index problem.
the front page doesn't though.
not got a lot of time to fix it at the moment. Anyone with time and php knowledge, email me for the ftp password and i'll send it over. Looks like it might be some database index problem.
QUOTE(DanSon @ 8-Feb-07, 22:01)
Anyone with time and php knowledge, email me for the ftp password and i'll send it over. Looks like it might be some database index problem.
I have time and PCP knowledge; mmmm Angel Dust....
It's funny 'cos it's completely untrue.
Also the 'TM' on my sig has gone...
Thats a stupid error.
Query:
Error:
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
EDIT:
Dan, did you dump the DB and reinstate it?
Sometimes you get character encoding issues (kings TM for example).
I will give this some more thought at some point. shouldn't be to much issue it's just the portal at least and not the whole site....
Query:
CODE
SELECT t.tid, t.title, t.state, t.last_vote, p.*, v.member_id as member_voted
FROM ibf_topics t, ibf_polls p
LEFT JOIN ibf_voters v ON (v.member_id=18 and v.tid=t.tid)
WHERE t.tid=252 AND p.tid=t.tid
FROM ibf_topics t, ibf_polls p
LEFT JOIN ibf_voters v ON (v.member_id=18 and v.tid=t.tid)
WHERE t.tid=252 AND p.tid=t.tid
Error:
CODE
Unknown column 't.tid' in 'on clause'
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
EDIT:
Dan, did you dump the DB and reinstate it?
Sometimes you get character encoding issues (kings TM for example).
I will give this some more thought at some point. shouldn't be to much issue it's just the portal at least and not the whole site....
QUOTE(Tart @ 9-Feb-07, 18:38)
Thats a stupid error.
Query:
Error:
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
EDIT:
Dan, did you dump the DB and reinstate it?
Sometimes you get character encoding issues (kings TM for example).
I will give this some more thought at some point. shouldn't be to much issue it's just the portal at least and not the whole site....
Query:
CODE
SELECT t.tid, t.title, t.state, t.last_vote, p.*, v.member_id as member_voted
FROM ibf_topics t, ibf_polls p
LEFT JOIN ibf_voters v ON (v.member_id=18 and v.tid=t.tid)
WHERE t.tid=252 AND p.tid=t.tid
FROM ibf_topics t, ibf_polls p
LEFT JOIN ibf_voters v ON (v.member_id=18 and v.tid=t.tid)
WHERE t.tid=252 AND p.tid=t.tid
Error:
CODE
Unknown column 't.tid' in 'on clause'
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
EDIT:
Dan, did you dump the DB and reinstate it?
Sometimes you get character encoding issues (kings TM for example).
I will give this some more thought at some point. shouldn't be to much issue it's just the portal at least and not the whole site....
I was saying all of that only the other day.
QUOTE
Also the 'TM' on my sig has gone...
QUOTE
Sometimes you get character encoding issues (kings TM for example).
The character encoding is set to 'ISO-8859-1' in the http header. Dan is going to get one of his web monkeys to set the encoding in php.ini to UTF-8.
If you want the TM symbol:
firefox, View -> Character Encoding -> UTF-8
QUOTE(Tart @ 9-Feb-07, 19:38)
Error:
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
CODE
Unknown column 't.tid' in 'on clause'
of course "t.tid" is a known column, if you remove it from the "on" clause in the query it runs fine, which means it can handle the WHERE statement which also references 't.tid'. craziness.
So, in conclusion, I blame Pete.
The database error might be a symptom of a problem with 'conf_global.php'. I'm working on it.
QUOTE(Pete @ 9-Feb-07, 20:33)
If you want the TM symbol:
firefox, View -> Character Encoding -> UTF-8
Hey; that works. I understood something...OK so you spelled it out to me but the warm glow persists.
QUOTE
The database error might be a symptom of a problem with 'conf_global.php'. I'm working on it.
Seems odd though, best of luck...
EDIT: I just noticed. Go on then, what was the problem?
Two things:
1. What was wrong with the old version? It was all working perfectly fine and we were all perfectly happy until you came along with your tinkering and your fancy language.
2. Bunch of cretins
The end
1. What was wrong with the old version? It was all working perfectly fine and we were all perfectly happy until you came along with your tinkering and your fancy language.
2. Bunch of cretins
The end
QUOTE(Tart @ 10-Feb-07, 18:40)
QUOTE
The database error might be a symptom of a problem with 'conf_global.php'. I'm working on it.
Seems odd though, best of luck...
EDIT: I just noticed. Go on then, what was the problem?
Changed some of the paths in 'conf_global.php'. Didn't fix the front page problem but we should be able to upload files now.
Invision board 2.0.0 is not a fan of mysql 5, which is unfortunately what Dan's new server is running. To get the front page working, I had to add parentheses to one of the sql queries; mysql 5 is more strict about syntax.
In 'mysql_queries.php', changed
CODE
FROM ".SQL_PREFIX."topics t, ".SQL_PREFIX."polls p
to
CODE
FROM (".SQL_PREFIX."topics t, ".SQL_PREFIX."polls p)
This site helped me out.
We'll probably see more sql errors crop up as we try different features of the forum script.
QUOTE(Sammyboy @ 10-Feb-07, 18:52)
Two things:
1. What was wrong with the old version? It was all working perfectly fine and we were all perfectly happy until you came along with your tinkering and your fancy language.
2. Bunch of cretins
The end
1. What was wrong with the old version? It was all working perfectly fine and we were all perfectly happy until you came along with your tinkering and your fancy language.
2. Bunch of cretins
The end
1. Nothing - apart from you were all far TOO happy.
2. Yes but only on Tuesdays.
Dan
anyone noticed any difference in the speed of this forum? Faster / Slower?
I think it might actually be a bit faster for me...want to know if I'm imagining it.
I think it might actually be a bit faster for me...want to know if I'm imagining it.
Bollocks
just as i predicted. Thank you Mr. Sboy.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.