p2grace

Not knowing exactly how your code is structured, you best bet is to probably save the data into session variables, and then call the session variables in your mailer.

What does the url look like when the array is empty. Can you post the entire url so we can check if the $_GET variables are being set correctly?

Try clicking one of the links... the array should be filled with the data provided through the $_GET vars.

Can you post the latest version of your code?

Replace all instances of $_GET['dream_id'] with $_GET['id'].

What does it do when you click the link.

Change this: echo "<a href=\"{$_SERVER['PHP_SELF']}?action=show&id=$id\">Back</a>"; to echo "<a href=\"{$_SERVER['PHP_SELF']}?action=show&id=$id\">Back</a>";

Is the echo actually displaying $id, or the value of the variable $id. It shouldn't be showing $id obviously, it should should the value.

Try changing your query to: $query = "SELECT * FROM `dream` WHERE `dream_id` = '$id'";

Right - which means this query is wrong "SELECT * FROM dream WHERE dream_id=$id". echo $query; die(); copy the query into a msyql administration panel (e.g. phpmyadmin) and test the query. Could mean 1 of 2 things. One the query is wrong, or two $id is null.

Is the query working? Instead of doing if (mysql_num_rows ($result) == 0) { do if (!$result || mysql_num_rows ($result) == 0) { // this will trigger if there was an error in the sql query or if there weren't any results }

It could also be a permission problem. If apache can't write to the folder to create the directory, it'll fail. As gizmola suggested, the best approach is to write logic for debugging to see exactly what is causing the error. When all else fails, display php errors or view the php error log. error_reporting(E_ALL); ini_set('display_errors','on');

One method would be to use a cookie that expires in 24 hours, that stores the # of times each ad was displayed.

Because the only way the user can verify their email address is by clicking on the unique link from their email inbox. The other way only validates the mx record exists, but it doesn't ensure the user is using their own email address. The method I just outlined forces the user to go to their own email inbox and click the unique link, thereby proving the email address is theirs.

One such method would be to send it to a link that is not protected by the session security, but that link creates the session variables, and then redirects to the form that is secured by the session. The other method would be to adjust your security that checks for sessions and creates an exception. Although I would suggest the first route.