one quick question.... where is the parse error in this?

philvia

<tr><td colspan=3 CLASS=CELL2><b>Moderator Applications</b> <input type=\"radio\" name=\"mod\" value=\"1\"";
if ($myrow["val"]==0) { echo " checked"; }
echo "> Closed <input type=\"radio\" name=\"mod\" value=\"2\"";
if ($myrow["val"]==1) { echo " checked"; }
echo "> Open </td></tr>";
$sql="SELECT * FROM options WHERE opid=9";
$result=mysql_query($sql);
$myrow=mysql_fetch_array($result);
echo "<tr><td CLASS=CELL1 colspan=3>
<b>Minimum Karma Needed:</b> <input type=\"text\" name=\"karma\" value=\"".$myrow["val"]."\" size=\"6\" maxlength=\"40\"><input type=\"submit\" name=\"post\" value=\"Make Changes\"></td></tr>
<tr><td colspan=3 CLASS=CELL2><b>Register Page</b> <input type=\"radio\" name=\"reg\" value=\"1\"";
if ($myrow["val"]==0) { echo " checked"; }
echo "> Closed <input type=\"radio\" name=\"reg\" value=\"2\"";
if ($myrow["val"]==1) { echo " checked"; }
echo "> Open </td></tr>";
$sql="SELECT * FROM options WHERE opid=10";
$result=mysql_query($sql);
$myrow=mysql_fetch_array($result);
echo "<tr><td CLASS=CELL1 colspan=3>
<input type=\"submit\" name=\"post\" value=\"Make Changes\"></td></tr>
</form>
</table>";
include("../include/foot.php");
?>

laserlight

on the very first line 🙂

perhaps you should give a somewhat more complete code snippet, though the first line could actually be where your parse error lies in (i.e. the unescaped double quote)

philvia

bah, here is the whole file...

philvia

oh and the ""; isn't the problem.

laserlight

I tried reading it, but I'm not used to the formatting so...

on which line is the parse error stated to be?

Weedpacket

One of the advantages of properly formatting your code when you write it is that it becomes easier to spot mistakes like this one.

The line that reads

if (($post) && ($reg)) {

Has an opening { which never gets closed. PHP got to the end of the file and got upset because the } it was expecting was missing.

philvia

the parse error is on line 184...
i'll try the bracket thing.

philvia

here is where the parse is located...

if (($post) && ($reg)) {
if ($reg==1) {
$sql="UPDATE options SET val=0 WHERE opid=10";
$result=mysql_query($sql);
}
if ($reg==2) {
$sql="UPDATE options SET val=1 WHERE opid=10";
$result=mysql_query($sql);
}

What I don't get about the bracket thing you said is it's like that on the others and there is no parse error...

philvia

~_~

laserlight

Weedpacket definitely is correct.
That your parse error is on the last line of the script is further proof of it.

Indent your script properly.

It will be obvious that
include("../include/foot.php");
is indented once, yet it isnt in a code block.
So where is it? Hanging, hence the parse error is reported on the last line.

rich_d

The parser error is a missing bracket just like Weedpacket said. Look at line 102 - that if block doesn't close properly. Stick a } on line 103 and you won't get the parse error.

The code seriously needs formatting properly.

laserlight

hmm... I think line 102 is ok, considering the use of $numrows following it.

With no comments it is hard to say.

Incidentally, it isnt a closing bracket that is needed, it is a closing brace, at least in PHP's usage.

Actually, could it be line 98 or line 93 instead?

philvia

Everything works perfect except the part i posted right before my "Bump" post... i deleted that part from the script for now so the page will work and it does. The one and only problem is the part that i posted right before my "bump" post.

rich_d

Laserlight - no, 102 is the bottom of the problem. The problem starts on line 99 - the { isn't closed. If I create a new line (103 - bumping the "if ($numrows>=1) {" down to 104) and stick a } on line 103 it then I get no parser error at all. This is without a doubt where the problem is.

philvia - the code posted originally was virtually useless to us because it's incomplete - it doesn't even start with a php command. Assuming that html at the top is part of an echo the only error in the entire block is the lack of a \" before the input type=radio. There is nothing else wrong with it and as it stands it will not cause a parser error unless you're forgetting to close something somewhere else (see my comment above).

Cheers,

Rich