Warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL..

alliax - June 3, 2006 - 01:17

Hello, just a few hours ago I've noticed my website shows a bad warning, then stupid as I am I went to the database and delete all the cache table.

Then not much was working, as you can see on http://www.senserely.com

Now I realised that several other 4.7 drupal sites hosted on 1&1 show the same behavior, so what is it? Don't you have a problem with your own 1&1 hosting?

My site and others have been running fine for over a month and it suddenly happened today, I didn't do anything special today, at first I thought it was a hack, but my site is patched up to 4.7.2

So what can it be? Is it a new version of PHP? MySQL?

I know when I created the database I used MySQL 5 I don't know what version of PHP was before but honestly can it be a problem from MySQL version?!?

Cheers,
James

» Login or register to post comments

I've just saw in 1&1 they

alliax - June 3, 2006 - 01:30

I've just saw in 1&1 they write :
For security reasons your 5.0.3 PHP has beeen updated you now have PHP 5.1.1
but I don't know how old is this message. Maybe it was like that when I install my site since the php 5.1.1 dates from 28-Nov-2005

I will ask them, but do you think it can come from PHP?

Just to clarify: I didn't

alliax - June 3, 2006 - 15:32

Just to clarify: I didn't drop the database, simply truncated it, ie. EMPTY

NOW I have a new problem, the mysql message doesn't appear anymore, but I can't access any of the old urls, like admin or user.. PAGE NOT FOUND

So what can be the problem and how can generate the variables again, so Drupal knows how to get back on its feet?

Cheers,
James

Thank you for nothing, I

alliax - June 3, 2006 - 19:02

Thank you for nothing, I solved my problem, thank you all!

Good work! What was your

hansrossel - November 6, 2007 - 15:01

Good work!

What was your solution?

Hans
KOBA - Webdesign with Drupal

I honestly don't remember,

alliax - November 11, 2007 - 03:10

I honestly don't remember, and yes I should have stated my solution instead of being cynical about the lack of help/support.

One thing I've learn since then is to screw 1and1, they really suck!

I had a problem with the

thehandyman - April 10, 2008 - 16:35

I had a problem with the same error code, as a result of clearing the cache manually. In my case it turned out to be a problem with views... to fix, I went to edit each custom view and without changing anything I saved. After that the SQL errors went away.