Query not running but no errors...

[The14thGOD]

I have a page that updates a press release and it runs one query but not the other. No errors as far as the query goes (some 'undefined variables' in other parts of the script).

 

Here's the code:

<?php
$updateQuery = "UPDATE website AS w INNER JOIN preview AS p ON (w.uid = p.uid) SET w.navtitle=p.navtitle, w.title=p.title, w.keywords=p.keywords, w.description=p.description, w.url=p.url, w.body=p.body, w.the_date=p.the_date, w.status=p.status WHERE w.uid = '$_GET[uid]'";
	mysql_query($updateQuery);
	$updateQuery2 = "UPDATE preview SET draft='false' WHERE uid='$_GET[uid]'";
	mysql_query($updateQuery2);
	echo $updateQuery2;
	echo mysql_error();
	exit();
	header("Location: $_SERVER[php_SELF]?edit=true&uid=$_GET[uid]&edit_suc=true");
	exit(0);
?>

 

Query:

UPDATE preview SET draft='false' WHERE uid='5pjm94ap98'

 

I have no idea what it could be.

Any help is appreciated,

Justin

[Pikachu2000]

Which query doesn't run? The first or second one?

[The14thGOD]

sorry, the 2nd one doesn't run.

[Zane]

$_GET[uid] needs to be $_GET['uid']

and you can't do that without concatenating... well, or using curly brackets, but anyway

 

$updateQuery2 = "UPDATE preview SET draft='false' WHERE uid='" . $_GET['uid'] . "'";

[The14thGOD]

$_GET[uid] needs to be $_GET['uid']

and you can't do that without concatenating... well, or using curly brackets, but anyway

 

$updateQuery2 = "UPDATE preview SET draft='false' WHERE uid='" . $_GET['uid'] . "'";

Didn't work, plus it works in all the other queries as is :/ that's the only reason I didn't try that method.

It makes no sense, not sure what else I can do.. oh and just so there's no question about it, I have verified that the 1st query works.

[Pikachu2000]

Go into phpMyAdmin, and copy the echoed query into it. See if it works there. If not, try just a simple SELECT * FROM preview WHERE uid='5pjm94ap98' and see what you get.

[The14thGOD]

Argh sorry, I was troubleshooting it with someone while making this post, apparently I left that out too. I tested in phpMyAdmin and it worked in there just fine.

[Zane]

when in doubt... use "or die()"

mysql_query($updateQuery2) or die("Failed Query: 
\n" . $updateQuery2 . "
\n" . mysql_error());

[Pikachu2000]

when in doubt... use "or die()"

mysql_query($updateQuery2) or die("Failed Query: <br />\n" . $updateQuery2 . "<br />\n" . mysql_error());

My next suggestion was going to be what he said ^  . . .

[Zane]

My next suggestion was going to be what he said ^  . . .

Tryin' to jack some runner-up credit are ya? Like an assist in Halo.

[Pikachu2000]

Shameless, ain't I? 

[Zane]

No more shameless than a Pokemon.

[Pikachu2000]

Well, I reckon you're right!

[The14thGOD]

Nothing

In the database, draft is still set to 'true'

I'm unfamiliar with the 'or die()' but I even put exit(); under it but I just got a blank page.

Does die() stop the whole script?

[Zane]

Does die() stop the whole script?

Yes, and if there were something wrong with your query it should have shown your an error.

 

Now you're at the point where you have to go to the top (the very top) of the script and put

error_reporting(448191);
ini_set("display_errors","on");

[The14thGOD]

All the errors I get are normal from what I can tell:

 

 

Notice: import_request_variables() [function.import-request-variables]: No prefix specified - possible security hazard in /path/to/press.php on line 5

 

Notice: Undefined variable: date in /path/to/press.php on line 9

 

Notice: Undefined offset: 1 in /path/to/press.php on line 10

 

Notice: Undefined offset: 2 in /path/to/press.php on line 10

 

Notice: Undefined variable: send in /path/to/press.php on line 11

 

Notice: Undefined variable: edit in /vpath/to/press.php on line 44

[Zane]

ok.... so or die() ceases to do it's job for some reason today??

 

 

Try this and see what happens

$query2 = mysql_query($updateQuery2) === false ? die("Failed Query: 
\n" . $updateQuery2 . "
\n" . mysql_error()) : mysql_query($updateQuery2);

[The14thGOD]

ok.... so or die() ceases to do it's job for some reason today??

 

lol I have no idea dude, this is so simple it's stupid, at first I was thinking it had something to do with me not looking at this for a while, but everyone is scratching their heads...

 

The new code didn't produce anything new, just went through like normal.

[DavidAM]

$updateQuery2 = "UPDATE preview SET draft='false' WHERE uid='$_GET[uid]'";

 

There's no smiley for "graspping at straws" ...

 

What is the datatype for "draft"? Is it actually a char (or varchar) or is it a BOOLEAN.  Boolean is a INT(1) and you would need to set it to 0 (zero) or 1 (one).

[The14thGOD]

varchar, i know its better to use boolean in this case, but i just like reading true/false, I'm not worried about db performance for this site =D

[DavidAM]

I was just thinking that if it was boolean, the update would fail trying to set it to a string.

 

Again, grasping at straws, is there some kind of protection issue with that table? When you ran the code in phpMyAdmin were you using the same login that your code is using?

 

Is there an UPDATE trigger on that table? or some other constraint?

 

Are you sure you are not falling into some other code that is setting it back to false? I guess that would be kind of hard since you have an exit() right after it.

 

I really do not see any reason that that code would not execute as expected. Is this your actual code? or did you leave out stuff that you think is not significant? (I'm just asking)

[The14thGOD]

I'm not sure how it logs in to phpmyadmin, this server is on visi, but this user has all permissions.

Not sure what an update trigger is on the table...I'd assume no, I don't typically mess with sql other than data inserting etc.

 

It's all the code that is triggered in the event it is 'published.' It's in an if statement, but it runs as testing has proved.

 

Double checked code and there's nothing else that could set it back to true without conditions are met (also tested to see if conditions were being set off on accident, and they were not)

 

Ya..I'm with everyone at the moment. No idea what could be going wrong...

[DavidAM]

Well, just for grins, try reversing the two updates, run updatequery2 first then updatequery. See which one works.

 

Also, check all the server logs, Apache, MySql, and OS if you have access to them.

 

At this point, I would normally delete several lines of code and retype from memory, assuming there's something there I just can't see.

 

Sorry, I can't be more help.