what happened?
#5
Some issues with the software on the server by the looks of the error code it was throwing up (SQL error 173).
The forum was then taken out of public use untill the IB Admin had a chance to fix the issue, which they did in sterling time.
Normal service has now been resumed
The forum was then taken out of public use untill the IB Admin had a chance to fix the issue, which they did in sterling time.
Normal service has now been resumed
#7
Trending Topics
#12
Nothing fishy at all. The forum was closed for a couple of hours to repair a software issue with the SQL software that the forum is based on. Now this has been repaired, the forum is open again.
#13
He tried to let everyone know how to do it...but the post has been taken off in the cull.
#15
TBH, what happened almost certainly was IB put an untested (or not properly tested) bit of code live, then fucked off to bed, realised the next day they had fucked up and spent ages fixing it.
Ive done similar loads of times with internet sites I work on, and ones FAR more important than a ford chat site.
They fucked up, they fixed it, problem solved.
We all lost .5 day of service at 30p a day
Ive seen people lose a company Ł250,000 quid cause they put a semi-colon where they shouldnt have!
Ive done similar loads of times with internet sites I work on, and ones FAR more important than a ford chat site.
They fucked up, they fixed it, problem solved.
We all lost .5 day of service at 30p a day
Ive seen people lose a company Ł250,000 quid cause they put a semi-colon where they shouldnt have!
#16
Some issues with the software on the server by the looks of the error code it was throwing up (SQL error 173).
The forum was then taken out of public use untill the IB Admin had a chance to fix the issue, which they did in sterling time.
Normal service has now been resumed
The forum was then taken out of public use untill the IB Admin had a chance to fix the issue, which they did in sterling time.
Normal service has now been resumed
#17
I just did above, they put a bit of code on with a bug, it all went pete tong when trying to display the contents of a thread, and it took them ages to fix it.
Potentially the bug may have been there for a while before it surfaced as a problem, but most likely (judging by the severity of it) it was pretty much instant.
If they tested things better it wouldnt happen, but its a website you cant possibly test it the way that for exmaple I used to when I was writing code for power stations, it would just be too expensive and no way of justifying the cost when a "terminal failure" results in nothing more than some folk not being able to chat for a few hours.
Where as a similar bug at chenobyl killed millions of poeple and animals.
Potentially the bug may have been there for a while before it surfaced as a problem, but most likely (judging by the severity of it) it was pretty much instant.
If they tested things better it wouldnt happen, but its a website you cant possibly test it the way that for exmaple I used to when I was writing code for power stations, it would just be too expensive and no way of justifying the cost when a "terminal failure" results in nothing more than some folk not being able to chat for a few hours.
Where as a similar bug at chenobyl killed millions of poeple and animals.
#19
Well, I got up about 2pm, had to sort my grandparents phone out as they were all dead (plugged phone into master socket, still dead, hence bt network), fix my partners brother wireless (was a simple case of the wireless was using another 3rd company piece of software, so started relevant service and he was up and running in 2 minutes).
Other than that, looking for cheap things on eBay for my business...
You werent on about passionford was ya? Surely?
Other than that, looking for cheap things on eBay for my business...
You werent on about passionford was ya? Surely?
#20
#22
didn't cost any money but our intranet site completely ceased to function at the start of this week cos some twat put an apostrophe in the code they shouldn't have.
Last edited by Markb_s1; 01-05-2008 at 10:55 AM.
#23
#29
Just I posted up a thread saying its strange how they hadn't closed it while its broke, rather than letting everyone type LOADS of new topics, to only have to come along and delete them all. Around 1 min later it got closed lol
#34
Ironically with all the references to the database, it doesnt appear it was a database issue anyway, as for me the database was capable of outputting the required info and saving it (by using pages other than showthread to view and reply), it appears it was a script error in an include file that is only used on the "showthread.php" page, so not sure why its being presented otherwise, but either way its fucking irrelevant as it works now! This sort of thing happens all the time in a low quality IT environment.
#35
Ironically with all the references to the database, it doesnt appear it was a database issue anyway, as for me the database was capable of outputting the required info and saving it (by using pages other than showthread to view and reply), it appears it was a script error in an include file that is only used on the "showthread.php" page, so not sure why its being presented otherwise, but either way its fucking irrelevant as it works now! This sort of thing happens all the time in a low quality IT environment.