Mikey

Well if you ran two queries, you can then check if your adminpost query returns results. If it does, perhaps you could do something like array_merge it into your main array and that way it wont appear on every day?

Well if you want to use PayPal's donation features, first ensure you have a business account on PayPal. Then visit PayPal and get their button code, and you'll also need to use the PayPal IPN in order to get things like response codes to your site which you can then log in your database and even grab details like the email address from.

Split it into two queries. Remove the OR, and have a separate query for your adminpost stuff and then do things based on that.

The HTML you have posted is not valid unfortunately. For one you're not closing your IMG tag... Unless you perhaps need something like this: <td><a href='#' onclick='trigger("{$row[LocationPix]}");'><img src='http://www.menuhead.net/Images/Buttons/PShotClear.png' /></td> Otherwise, as Jessica said I'm not entirely sure what you're asking.

I suppose there's no reason. Personally I'd like transaction ID's to be more random/unique than the current timestamp + the current auto_increment ID. Using the current date/timestamp for instance limits to numbers only.

uniqid isn't usually random enough, for example it may (extremely slim chance here) generate the same integer twice. Though you may be able to use uniqid in conjunction with a MySQL field which has a unique index set on it. Personally I'd make a php function which generates a random string or a pre-determined length, (for example, PO9028341), and then check the database within that function to see if that string already exists as a purchase ID. If it does, recursion, if it doesn't, return.

As has been said, move <form> inside your loop, that will create a new form per-article.

Hi all! Come across the site so much via Google, figured it was past time that I joined!

Say, fancy seeing you here. *whistle*