Tonight we have made a significant change to the Pligg Pro shop. Fellow developer Chuckroast and I (Yankidank) came to a decision that the number of hours that we were spending fixing user errors was becoming a problem. Many people purchasing modules were not reading the provided support documents or viewing videos that we provide on the product pages that demonstrate setting up and configuring modules or templates. Too many support tickets were being added and it was no longer economical for us to spend so much time working on these unnecessary support tickets.
Pligg Content Management System 1.1.4 is out now, and we urge you to upgrade as soon as possible. This release patches a number of security issues brought to our attention by a couple different third party sources. These updates are critical to keep your site secure and will make you less vulnerable to certain types of attacks.
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.
This year we thought that we would show our love and appreciation to our users by offering everyone a 20% OFF coupon code to celebrate Valentine’s Day. Use the coupon code VALENTINES2011 during checkout to receive this discount on orders of $20 or more.
Whoopsie! We seemed to forget to include some database changes in the installation files for the Pligg CMS 1.1.3 release. This resulted in the vote feature not working for new 1.1.3 installations. If you are upgrading your website from a previous version of Pligg, you can safely ignore this message. If you have installed Pligg 1.1.3 for the first time on December 28, 2010 or earlier you should continue reading for a quick fix.
Today we announce the latest version of Pligg CMS, version 1.1.3. This version includes a few bug fixes, security updates, and a new and exciting voting method that makes use of the new Karma module. Karma has been a concept that has never been realized until these last few months. We are thrilled to finally provide Pligg users with a new way to encourage more participation on your websites through this new voting method.
Happy Thanksgiving everyone! This holiday season we will be celebrating our 5th year of development for Pligg CMS and we are excited about the amount of progress made over the past 18 months. Our previous release introduced some new features related to user Karma scores and a ranking system, and the next version of Pligg will make use of those Karma scores in a new voting method that is Karma weighted. More information on this update will be covered in a future blog article, but for now lets go over some equally exciting news… Black Friday and Cyber Monday sales!
We’ve noticed that spammers are creating Pligg accounts across multiple Pligg websites and they are using the user profile homepage field to insert links to spam websites. To help you fight this kind of spam we have added a small change to the Akismet module that will have it check user profile fields for spam and block suspicious profile changes. This update will be included in the next version of Pligg CMS, along with a few other features to help prevent this unwanted content from appearing on your domain.
Today we are releasing version 1.1.2 of Pligg CMS. This update includes a number of bug fixes and general improvements to make Pligg CMS compatible with the latest version of the EVB module as well as the new Karma module. There has been at least one security fix applied to this version of Pligg, so it is highly advised that all users make the upgrade in an appropriate amount of time. The most recent security fix was pointed out to us by Mike from Sitewat.ch, who contacted us a few days ago about the potential exploit. We prepared a fix within a day and have decided to release this new version to make sure that this issue does not get exploited before members have a chance to patch their sites through the 1.1.2 update.