Pligg Content Management System


Requirements: Pligg requires a modern version of PHP and MySQL and some PHP functions. To test if your server is capable of running Pligg please view the Troubleshooter. If any elements appear in red on that page you may have a problem with either installing or running Pligg.

  1. Create a mysql database. If you are unfamiliar with how to create a mysql database, please contact your web host or search their support site. Please pay careful attention when creating a database and write down your database name, username, password, and host somewhere.
  2. Rename the /language/lang_english.conf.default file to lang_english.conf. Same instructions apply to any other language file that you might use that are located in the /languages directory.
  3. Rename the file approvedips.txt.default to approvedips.txt
  4. Rename the file bannedips.txt.default to bannedips.txt
  5. Rename the file settings.php.default to settings.php
  6. Rename the file local-antispam.txt.default to local-antispam.txt
  7. Rename the /libs/dbconnect.php.default file to dbconnect.php
  8. Upload the files to your server.
  9. CHMOD 755 the following directories and files. If you experience any errors try 777.
    • /admin/backup/
    • /avatars/groups_uploaded/
    • /avatars/user_uploaded/
    • /cache/
    • /cache/admin_c/
    • /cache/templates_c/
    • /languages/ (And all of the files contained in this folder should be CHMOD 777)
    • approvedips.txt
    • bannedips.txt
    • local-antispam.txt
  10. CHMOD 666 the following files
    • /libs/dbconnect.php
    • settings.php
  11. Open /install/index.php in your web browser. If you are reading this document after you uploaded it to your server, click on the install link at the top of the page.
    • Select a language from the list.
    • Fill out your database name, username, password, host, and your desired table prefix.
    • Create an admin account. Please write down the login credentials for future reference.
    • Make sure there are no error messages! If you see an error message, or if installation fails, create a new thread on the Pligg forums
  12. Delete your /install folder.
  13. CHMOD 644 libs/dbconnect.php
  14. Open /index.php
  15. Log in to the admin account using the credentials generated during the install process.
  16. Log in to the admin panel ( /admin ).
  17. Configure your Pligg site to your liking. Don't forget to use the Modify Language page to change your site's name.


  1. Log into your site as admin
  2. Click on admin panel link
  3. Click on File and MySQL backup link
  4. Backup your files (and avatars) and your database
  5. Download the backup .zip files to your computer
  6. Delete the files from the backup manager


Please be sure to make a backup of your MySQL databases and files before upgrading to the latest version of Pligg. Some upgrades might require that you upgrade your MySQL database, so please make backups whenever upgrading.
These instructions do not support upgrading your template. Template upgrades require manual changes and should be carefully handled by the template author.
The directions below are recommendations that we have come up with to mininimize the number of problems that might come from upgrading your site.
  1. Backup your MySQL database
  2. Backup your old Pligg CMS files.
  3. Rename your template folder so that the data is not overwritted by upgrade files. If you use a template name that is not included with Pligg, skip this step.
  4. Disable all of the modules from your admin panel.
    You will need to re-enable them after upgrade.
  5. Delete all of the files from your server EXCEPT:
    1. /avatars/ (entire directory)
    2. /libs/dbconnect.php
    3. /.htaccess
    4. /favicon.ico
    5. /settings.php
  6. Upload all of the new files to your server.
    If you are able to I suggest uploading a zip file to the server and extracting it server-side. This will minimize the chances of files being corrupted during FTP transfer, which is a common issue.
  7. Confirm that the CHMOD permissions for the following files or directories are all set to 777.
    • settings.php
    • /admin/backup/
    • /avatars/groups_uploaded/
    • /avatars/user_uploaded/
    • /cache/
    • /cache/admin_c/
    • /cache/templates_c/
    • /languages/
    • /languages/lang_english.conf
  8. Run the upgrade from /install/upgrade.php
    If there are no error messages, delete the /install directory from your web server.
  9. Log in as a "god" level user.
    In some cases you may already be logged in from your previous version of Pligg.
  10. Either update your template to work with the latest version or navigate to /admin/admin_config.php?page=Template and change the template name to "wistie"
  11. Re-activate the disabled modules from step 4, navigate to /admin/admin_modules.php


Pligg is an Open source project, but that doesn't stop us from having a rock-solid support team. Pliggers from all across the world are watching the forum 24 hours a day helping each other out. If you have any questions, ideas, modifications or bugs to discuss please let us know through the Pligg forum.

Creating a forum account is also important because it allows you to download additional free templates and modules from Not only can you download free files, but you can keep track of updates for your modules and templates by marking them as "installed". You will then be notified automatically when a developer updates any of your installed files.


This code was originally written by Ricardo Galli for the open source project known as Meneame.

Many thanks to those who donated time and money to the Pligg project. Without their support we wouldn't be able to keep this project alive. If you are interested in becoming a part of the development team please contact us through the forum.

A special thank you to all of the Pligg developers and translators.


Pligg's source code is published under the Affero General Public License. You can view the license in the file LICENSE.txt and in the default "About" page that is included when you install Pligg.

Questions / Comments?

Support questions should be posted as a thread on the Pligg Forum

Please report security flaws to the Security Issue Contact Form on Please don't contact us directly for any other purposes.

If you would like to translate Pligg to another language you can apply to do so here, and please join the Translate Pligg Group on Google Groups.