[Joe]

Well today I got some time to work on all this. And I have gotten this done:

Gone through all the HTML pages for the entire legacy site, stripped all header info, and cleaned it up to just be HTML code for the body of the articles/reviews.

I have the legacy site importer script working so that I tell it what files went to which articles, who wrote it, when, and categorize it. Then it imports the HTML files into the DB, and outputs a file named the same as the orginals but empty with only a PHP HEADER refresh to forward people going to the old HTML files to the DB generated version.

Really those are the main things I needed to get written and tested to let me get all the old site data into teh new site. Now it will take me a few nights of work to import all the old site data into the DB. Once that is done I will work on the article display portion.

Once I can get the article display function to work as expected with the Legacy articles, then I can get the site posted, and work on the new article posting action after that.

This whole deal is stupid complex for what I was expecting it to be... but atleast its a long term solution. It just sucks having to semi manually get 600 pages of HTML code into a DB! And getting 6 year old HTML formatted to a way that it will work with a new database driven app.