and the Heartbleed Bug

As many of you may have already heard, early last week a major web vulnerability nicknamed “Heartbleed” was discovered related OpenSSL, a technology used by many websites to encrypt data between users and a website. We at addressed this issue and applied a fix on our own server shortly after the public announcement of the bug, but there are still security precautions that you may want to take to make sure that your account remains secure.

Pligg Vendor Commission Increase

Today we are announcing an immediate change to Pligg’s Vendor program. Vendors now earn a 66% commission, which is a 6% increase over what we previously offered! If you aren’t already familiar with’s Vendor program, it’s setup so that anyone can sell Pligg add-ons. It’s a great, low fee method for selling digital products on the official website. Vendors have the ability to add and edit product listings, and send out update notices when a new module version becomes available. Using Paypal’s Adaptive Payments API, we split the payment at the time of transaction so that you earn your commission as soon as the order has completed. There’s no waiting period, no minimum payout requirements. The only thing that we require is a Paypal account email address.

Pligg CMS 2.0.1 Release

The 2.0.1 update for Pligg CMS improves on a number of Pligg features and design elements, but it mainly addresses a number of small bugs patched since Pligg 2.0.0. We recommend that everyone updates to 2.0.1 to benefit from the latest Bootstrap changes as well as a small security update.

Pligg CMS Celebrates 8 Years of Development!

Today marks 8 years since Pligg CMS was first created back in 2005. Since that time, Pligg has grown from a basic web script to a fully functional content management platform. We’re really proud of our accomplishments over the years and would like to share with you some highlights.

What are {literal} tags?

A common issue Pligg users come across when trying to add CSS or JavaScript to a template file is that it will sometimes result in a broken (blank white) site. What causes this is the use of {curly} brackets in the code, which confuses Pligg’s template engine. Pligg uses curly brackets as opening and closing delimiters, which basically means that curly brackets are Pligg’s way of figuring out when you are trying to use template variables or perform other template logic. Curly brackets are associated with JavaScript and CSS coding, which means that you will need to take an extra step when embedding these types of code in your template files.

Pligg 2.0.0 Final

After over a year since initial development, Pligg 2.0.0 is now available to download in a final form. The 2.0.0 version of Pligg CMS represents a stable point in the project and we are happy to recommend this version for production servers, and encourage users to now make the upgrade from Pligg 1.2.2 to 2.0.0.
Continue reading »

Overriding Module Template Files

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.

Pagename Variables

Pligg CMS assigns ‘Pagename’ variables to PHP scripts as a way for template designers to figure out what script is being used to generate the page. Variables are often used in Pligg templates to determine whether or not you should display content by using template logic, much like how you can construct logical operators with programming languages such as PHP or JavaScript. This is useful when you want to set an ‘active’ state to an element like a navigation menu.

Pagename variables are defined in Pligg’s .php files to determine what page you are currently viewing. Typically the $pagename variable is equal to the name of the php file that is generating the page. Read the full post for code examples.

Embedding Youtube Videos with a Template Plugin

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.