| Moving Pligg Installations |
After changing a template, I wanted to install Pligg in a test location, mixing together different elements: - The new template from the dev environment (with standard Pligg code)
- Existing installation's user-viewable text (libs/lang.conf)
- New database, but...
- Existing installation's database data
- Existing installation's avatars
- New base URL
Here is what I did - From Pligg admin interface, back up database, database structure, files, and avatars; save to local disk.
- Save database structure and database backups as SQL files to your local disk.
- Editing the database SQL file, change the two Location Installed lines
- Open the MySQL console (GoDaddy offers one from Starfield Technologies) on this new database.
- With the MySQL console, create a new database.
- With the MySQL console, import the db structure and db with standard options.
- Adjust settings.php in your local Pligg files to reflect base location.
- Adjust libs/dbconnect.php in your local Pligg files to reflect database connection info.
- Move your local Pligg file directories into the test installation from your development environment.
- 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.
- 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.
- Fix the 'category' internal database ids with a database editing tool. See the forum for details.
|