I am having trouble uploading a PostNuke site from my local computer to a remote web host. Any help would be greatly appreciated.

Because I was originally experimenting with PostNuke, I copied an existing static website to my laptop which is set up with Windows XP Pro, MySQL and PHP. I created a database in MySQL and installed PostNuke into a sub-directory of the site. I populated the database with a number of users, granted permissions, added DownloadsPlus and uploaded various files. I created a link from the home page to this dynamic section, which opened the login page. Everything worked fine.

I then decided to upload the complete site to my web host. They allow me only one MySQL database and it's already provided, having a different name to the one I created. I've been able to generate a dump file and populate this new file with my tables, fields and content. I've also uploaded all the files for the website to the host.

This site can be opened using my web browser but when I click on the link to the PostNuke section it fails. I've tried amending the config.php file with the new database name, password, etc. but it hasn't helped.

What am I missing?

You might find it's easier to install your (online) site like a new site and then drop the database in exchange for your backed up (local) database.

Also, you never mentioned the prefix - did you make sure your database prefix matches the one in config.php?

Frank

--
Serious hosting - all the features, bandwith and storage you could want without breaking the bank at DreamHost.com [25]


See what I do with PostNuke - http://surreal-dreams.com

Thanks for responding so quickly. I’m a bit new to this so please excuse me if my responses seem somewhat stupid…

>>You might find it's easier to install your (online) site like a new site and then drop the database in exchange for your backed up (local) database.

I don’t really understand how I’d do this. If I install the site like a new site, how would I retain all the work that I’ve done so far? And how can I exchange the databases if my host has supplied me with one?

>>Also, you never mentioned the prefix - did you make sure your database prefix matches the one in config.php?

What do you mean by the database prefix? It’s just got a name, hasn’t it?

Sorry - I thought for sure I'd answered you. Let me try again.

If you install a new site, you won't have your existing data. However, you will have a working setup. If you use the same table prefix (I'll get to this) as you did locally, then you will be able to erase the database created on your new server site and replace it with the data from your local site.

You can easily upload your polulated database and remove the empty one. Using a tool like phpMyAdmin [36], you can export all your tables to a text file. Then you edit your new database on the server, drop the tables, and run the backup file you just exported as a query. It will populate your server's database with your existing local database.

A prefix is the "nuke_" or "pn_" that precedes the name of your tables - they all have the same prefix. This value is set in your config.php file. If you use the same prefix when you set up your new site on your webserver as you did locally, you'll be able to overwrite the "empty" database your fresh install creates with your exisiting tables and things should work right away.

Frank

--
Serious hosting - all the features, bandwith and storage you could want without breaking the bank at DreamHost.com [37]


See what I do with PostNuke - http://surreal-dreams.com