One new feature of Pligg 2 is the ability to override a module’s template files with a copy stored in your template’s directory. The great thing about this feature is that it allows you to upgrade a module without losing design changes, since the template files are being stored in a different directory. In this post I’ll describe how you can set up your first example template override.
Pligg’s template system is based on Template Lite, and one of the built-in features for this system is that it comes with plugin functionality. This allows you to make use of a number of pre-installed plugins (located in the /plugins directory), or you can even add your own plugins. In this post I’ll be demonstrating how you can add a new template plugin to return an embedded Youtube video. This is a very quick example that should provide enough direction for you to craft your own template plugin for custom functions.
In this post, you will learn how to set up a domain alias for the purposes of pointing a domain to your local server files. This is useful so that you can develop a website locally before deploying it to a live server. We used a domain alias when developing the new design for Pligg.com so that we could test for broken URLs that might occur due to many large changes to the site structure. Below is a video guide that you can follow along with demonstrating how to set up a domain alias, or you can read the full article for step by step directions.
One trick that spammers use to mass post to Pligg sites is by creating a lot of accounts. What is annoying is that there isn’t much that we can do to block these account creations if we can’t discover a pattern to them. Your best option to prevent these bot accounts is to rename the register.php file to something random. You can even go one step further, and frequently keep renaming the registration file which really would throw a curve ball and make life more difficult for spammers.
Interested in joining the cloud revolution? Want to try it out for free? Get your start with cloud hosting with AppFog by following this step-by-step tutorial.
For quite some time now, Pligg has included an API system with the CMS package. This API allows you to perform a few different actions like get your Pligg User ID number, find the site categories and their IDs, and even submit a story from a simple POST form. Today I’m going to explain all of these API functions, since it is something that we haven’t talked about much in the past even though it is one of the most interesting things that you can do with Pligg.
While diagnosing possible causes for a Pligg site running slower than I would like, I came up with some SQL queries to perform some spring cleaning on a Pligg database. The following 3 queries will remove stories and comments flagged as spam, then remove inactive members who haven’t interacted with the site by submitting content or casting votes. I don’t suggest that everyone use these methods to clean up their database. Pligg doesn’t discard spammer data from your database by default so that the spammers can’t just register again on your site. We maintain their user information (email, username, IP address) so that we can use that information to block them.
I have been working with Pligg for over four years now, and during that time I have collected several useful snippets of code that I found found to be quite useful when designing a Pligg template. This article includes some of those snippets, as well as some general tips for using Pligg CMS.
Transferring your site to a new webhost doesn’t have to be a pain, today I’m going to provide you with an easy to follow guide for backing up your website and changing webhosts. This tutorial will guide you through using SSH, FTP, Pligg and phpMyAdmin methods for moving your data to a new server. TheseContinue reading »