Pligg Support

I want to add extra comment field. I have tried as following:

1. Created extra column "extra_comment_field" into "pligg_comments" table

2. Added following code to comment_form.tpl
input type="text" name="extra_comment_field" id="extra_comment_field" 

3. Added following lines into comment.php

$extra_comment_field= $db->escape($this->extra_comment_field);

And changed following line:

 $sql = "INSERT IGNORE INTO " . table_comments . " (comment_parent, comment_user_id, comment_link_id, comment_karma, comment_date, comment_randkey, comment_content, extra_comment_field, comment_status) VALUES ($comment_parent, $comment_author, $comment_link, $comment_karma, FROM_UNIXTIME($comment_date), $comment_randkey, '$comment_content', '$extra_comment_field', '$comment_status')";

But it is not writing data to db column ? What am I doing wrong, please help me. I am new to php and pligg.

If the Group creator "Banned" a Group member, it has no effect and the banned member can still share stories to that Group. The banned member's profile shows he's still joined in that group.

If the Group creator edit the member to become Admin or Moderator, the edited member still doesn't have permissions as an Admin or moderator.

The Group creator can even banned himself and still he's the Admin of that group. IMO, the original Group creator should not be able to banned himself or set it's role to just Normal & Moderator.

The Last Logged in Users Widget is not working at all. I found and fixed the following (click the link to view the explanation):

You can get the fix from my Pligg fork at:
[ASK] how to limit the number of characters that appear in the notice publish news?

please see the pictures that I attach
As of Pligg CMS version 2.0.2, the Voting feature on comments is not visible due to some code. To fix it, follow these steps:

Open /templates/bootstrap/comment_show.tpl
LINE # 10 ..... CHANGE THIS {if $Enable_Comment_Voting eq 1} TO THIS {if $Enable_Comment_Voting eq true}
LINE # 12 ..... CHANGE THIS {if $Enable_Comment_Voting eq 1} TO THIS {if $Enable_Comment_Voting eq true}
Save and close

Open /templates/bootstrap/user_comment_center.tpl
LINE # 72 ..... CHANGE THIS {if $Enable_Comment_Voting eq 1} TO THIS {if $Enable_Comment_Voting eq true}
Save and close

An error is generated when the statement that evaluates the comment_buries_spam value. To fix it, see the last section of the attached link.
Spam Trigger Module

Is not working as intended. I fixed it and submitted the complete fix to Pligg Support and posted it also on

How it works:

Submit a Story or Comment

1- Upon submission of a story, the Module now checks for spam based on three levels: Light Trigger, Medium Trigger and Hard Trigger:

a- Light Trigger: the story will be held for moderation.

b- Medium Trigger: the story will be discarded.

c- Hard Trigger: the user will be 'Killspamed' and subsequently all his/her stories, comments, saved stories, etc. will be deleted.

NOTE: the Spam Trigger Module comes with the Light Trigger populated with common spam words and phrases. You have to populate the Medium and Hard Triggers. You can go through the Light Trigger and edit/remove according to your liking and even move some to the medium and Hard Triggers.

Be careful, some of the included words and phrases may be used innocently in a normal story.

Editing a Story or Comment

Say that a "smart" user/spammer submitted a normal story first and immediately edited the content, title and tags to include spam. It will be caught. Same procedure applies to Comments.

I already moved 4 entries from the Light trigger to the Medium Trigger for the purpose of this demonstration.

Watch how it works
Can we use Pligg as collaborated blogging platform? When I checked Pligg I found that its mainly using to publish articles from some other websites and comment on that. I want to use Pligg as Wordpress but many users can log in and blog or write articles themselves than linking to somebody's article in some other website. I do not want to use Wordpress since WP is not having default user registeration plug in. Apart from that if we use any plug in also, WP shows the dashboard of WP for the users. Please help. I am not a coding expert.
After upgrading to 2.02, i am always getting this error while submitting url
URL is invalid or blocked
The Statistics Widget was returning "UNKNOWN" for the MySql version. To fix it:
Open /widgets/statistics/templates/widget.tpl
On LINE 138, delete this bloc of code between the {php} and {/php}. It is returning an empty array:
function find_SQL_Version() {
$output = shell_exec('mysql -V');
preg_match('@[0-9]+.[0-9]+.[0-9]+@', $output, $version);
if ($version[0] != ''){
return $version[0];
return 'Unknown';
echo find_SQL_Version();

Replace it with the following block, between the {php} and {/php}
$link = mysqli_connect(localhost,EZSQL_DB_USER,EZSQL_DB_PASSWORD);
/* check connection */
if (mysqli_connect_errno()) {
printf("Connect failed: %sn", mysqli_connect_error());
$my_sql = mysqli_get_server_info($link);
//$my_sql returns will be something like the version and -log (5.5.24-log). we have to just grab the version number
$my_sql_version = substr($my_sql, 0, strpos($my_sql, "-"));
echo $my_sql_version;
Step One

If we set the value of “Negative votes to remove submission” in Admin Panel -> Settings -> Voting to any number other than zero, all submitted stories after this change will be discarded. The code is inaccurately processing the “buries_to_spam” variable which reflects the value set above.

To fix this bug see the link:

Step Two

In Admin Panel -> Settings -> Voting -> Negative votes to remove submission is set to 0 by default. However, in the current code, this defined variable that is assigned to buries_to_spam does not achieve its goal to set the story status to 'discard' when it reaches the number we set in here. As a matter of fact, even with the default value of 0, the story will be sent to discard. The fact is that the function evaluate_formulas () in \libs\link.php is what decides the status of the story when the formula set in the table_formulas is evaluated.

See the complete trace and fix: