Need Some Advice Please
 

I have been tasked with redesigning the following site http://www.naturalhealthdirect.com/ it's spilt over 2 hosting accounts 1 of which isn't valid anymore and this is the part i need advice on, if you go to the site and click the upgrade advert button, you'll see a form this is filled in, for a new add or to update an exisitng one, it then posts via an asp form which doesn't exist anymore as the account is invalid...it also sends it to an admin panel which is then approved or rejected, if approved it goes into a database..

So i need advice on what to replace the asp pages with to submit the form to the admin panel/database,


or (my preference)

Use phplinkdirectory, but is there an easy way to transfer the database over with the data being from a custom database

from what I can see, it doesn't post to an asp form on the old account.
it posts to a file called "pending_advert.php", and then redirects to the old host.

question is: whats the code in pending_advert.php do?

from what i can find in the code theres this
header("Location: http://www.sasltd.biz/naturalhealthdirect/notify.asp?UID=$New_UID");

but there are a couple of other pages that do the following
<form method="POST" action="https://sslrelay.com/naturalhealthdirect.sasltd.biz/processorder.asp" name="NHForm">

one being, if you click the low price NH books, so i need that function also, but i think for the main part i'll use phplinkdirectory, because
a) theres sooooo many files to theme
b) i have no clue whats in the asp files that are missing and his new host doesn't support asp anyhow
c) it'll probably cost to fix than to start again...

Originally Posted by ReaperUK

from what i can find in the code theres this header("Location: http://www.sasltd.biz/naturalhealthdirect/notify.asp?UID=$New_UID");

a)
And it doesn't insert the form values into a db before doing that redirect?
I suspected that the uid in the url was the new primary key resulting from a db insert. If not, it shouldn't be a big problem to insert the form values into the db?

b)
probably better off moving to phpld anyway. to justify the extra time involved in writing a script to import into phpld, you could tell the client that they will be moving to a standardised platform which is supported, and which brings advantages such as security patches, feature upgrades, and a large pool of developers already familiar with the codebase.