[Yankidank]

Reserved for future use.

After changing a template, I wanted to install Pligg in a test location, mixing together different elements:

1. The new template from the dev environment (with standard Pligg code)
2. Existing installation's user-viewable text (libs/lang.conf)
3. New database, but...
4. Existing installation's database data
5. Existing installation's avatars
6. New base URL

Here is what I did

1. From Pligg admin interface, back up database, database structure, files, and avatars; save to local disk.
2. Save database structure and database backups as SQL files to your local disk.
3. Editing the database SQL file, change the two Location Installed lines
4. Open the MySQL console (GoDaddy offers one from Starfield Technologies) on this new database.
5. With the MySQL console, create a new database.
6. With the MySQL console, import the db structure and db with standard options.
7. Adjust settings.php in your local Pligg files to reflect base location.
8. Adjust libs/dbconnect.php in your local Pligg files to reflect database connection info.
9. Move your local Pligg file directories into the test installation from your development environment.
10. Take the avatars backup from your local disk, and upload to new location; or else move the avatars directly from your existing installation to the test installation. You may have to download to local disk, then re-upload.
11. Take lang.conf file from your files backup or online host (you may have to use your local disk as an intermediary) and place in libs of testinstallation.
12. Fix the 'category' internal database ids with a database editing tool. See the forum for details.