Apr 13th, 2009, 6:17 PM
(Apr 9th, 2009, 6:06 PM)Ben Wrote: Ahh... now I get it.
I've turned up error reporting to a very high setting for the FT2 beta - just so that little errors like these get reported. They shouldn't occur, and often they can explain bigger bugs. So once FT2 is finally released as a main build, the error reporting option will be turned down to errors only and you won't see these warnings.
But to fix it in the meantime, add a "@" character before outputting each variable. For example:
PHP Code:<?php
$a1 = @$_GET['Guest_1_Given_Name'];
if (!empty($a1)) { ?>
<tr>
<td style='font-weight: bold'>Guest 1 : </td>
<td><?=@$_GET['Guest_1_Given_Name']?> <?=@$_GET['Guest_1_Surname']?> </td>
</tr>
<tr>
<td style='font-weight: bold'>Guest 1 Status : </td>
<td><?=@$_GET['Guest_1_Status']?> </td>
</tr>
<tr>
<td style='font-weight: bold'>Guest 1 Meal : </td>
<td><?=@$_GET['Guest_1_Meal']?> </td>
</tr>
<?php } ?>
The "@" symbol suppresses warnings for non-defined variables like these.
Hope this helps!
- Ben
OH, OK, thanks a lot Ben. In case we don't say it often enough, we really appreciate what you do.