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.
The upcoming release 1.1.0 will introduce a new “widget” system for Pligg. This new feature has been added to make managing your Pligg site from the Pligg Admin Panel an easier process. The Admin Panel homepage will be replaced with a new widget interface, which will allow you to customize the information that appears when you log into the Admin Panel.
We have created a new wiki article that we will begin using as our Official Roadmap. We realized that developers and users were being kept in the dark about some of our more specific plans for future releases, and that is why we are now detailing most of our upcoming fixes in this new Roadmap document.
Today I wrote a new Shell script that will add the latest SVN files to your server and prepare them for a Pligg installation. This new file allows me to perform very fast Pligg installs. In roughly 55 seconds I can transfer the SVN files to the server, rename the necessary files, CHMOD files and directories, run the Pligg installer, and log into the Admin Panel for the first time.
A bug caused by the new Admin News Management page has been fixed, causing us to re-release Pligg 1.0.4. The News Management page was changing the story status for multiple stories that were not meant to be changed whenever you would hit the “Apply Changes” button. This bug caused all of the articles that were marked as published on the News Management page to re-save their publish timestamp. Because Pligg uses this publish timestamp to sort stories on the homepage, it would cause problems with the sort order. Multiple stories had the same timestamp and Pligg didn’t know how to order them, so it would sometimes mix the publish order. The issue is now fixed with the latest release and it’s as simple as overwriting your 1.0.4 files to benefit from this update.
Sometime in the past 24 hours we passed the 300,000 download mark for Pligg CMS. This figure represents a great milestone in our success and we can’t wait to see how quickly we will get to the next hundred thousand downloads. Our previous release, Pligg CMS 1.0.3 racked up enough hits to earn the position as the most downloaded file on the Pligg.com.
The 1.0.4 version of Pligg CMS is now out. You can download it and read the extensive changelog list from the 1.0.4 announcement thread. This version includes an improved admin panel, a better killspam feature, and a large number of new features and bug fixes.
This spring we are offering a massive 50% discount at Pligg Pro to celebrate our 4th year. For six days only you can receive 50% off by using the coupon code PLIGGSPRING when checking out. This deal only lasts until midnight Wednesday evening EST and is the absolute best deal we’ve ever offered. Sale starts Friday March 26th and ends on Wednesday March 31st, 2010.
The Pligg Forums seem to be the only portion of Pligg.com that is still suffering from slow page load times. We will continue working on resolving this problem, but in the meantime we would like to share a minor bug fix to address a problem caused by the slowed Pligg.com server. Since the forums are still mostly inaccessible, the Pligg Module Management page may be taking a very long time to load for some people. To fix this we have added a timeout value to the module version check code so that if the Pligg server is inaccessible it will continue loading the page without the information. You can download the new admin_modules_center.tpl file here, which should be used to replace the file with the same name in /templates/admin/.
Currently the Forums are the most affected by our server issues. They are mostly inaccessible at the moment, and we are working on addressing this issue as soon as possible. Throughout the day you may receive error messages or pages that never complete. We are doing our best to address these issues and we should have the site back to normal soon.