Navigation

Pligg Support

This release addresses a number of issues related to using Pligg in a language other than English. We have tested and bug fixed both the installation process and user language selection feature.
The installation and upgrade script are no longer dependent on the pligg.com server for installation language files. An added benefit is that the upgrade process now performs much faster.

The Simple Messaging module and story comment permalinks are other major fixes included in this release.

https://github.com/Pligg/pligg-cms/releases
This release addresses a number of issues related to using Pligg in a language other than English. We have tested and bug fixed both the installation process and user language selection feature.
The installation and upgrade script are no longer dependent on the pligg.com server for installation language files. An added benefit is that the upgrade process now performs much faster.

The Simple Messaging module and story comment permalinks are other major fixes included in this release.

https://github.com/Pligg/pligg-cms/releases
Pligg has 3 default story statuses: Published, Upcoming, and Discarded. I realize what the first two terms mean, but what is a "Discarded" submission?
Where can I see a working demo? I would like to see how it looks and works. Thank you.

This section of Pligg.com is for asking questions and helping other Pligg CMS users by posting and voting on answers. This area, as well as the future Showcase Gallery, is powered by Pligg CMS.

This site displays the highest voted comments first, which helps you find answers faster. Vote up the most helpful answers, and vote down incorrect or irrelevant answers to help filter out less useful information.

The following file types can be attached to either a new question or answer: .jpg, .png, .gif, .diff, .patch, .css, .default, .gz, or .zip. If you want to include a filetype not mentioned, please compress it into a .zip archive.


If you need to wrap a block of code...
use a <pre> tag like this area.
3 files have been edited.

/kmessaging/class.KMessaging_v1.2.3.php
/templates/user_navigation.tpl
simple_messaging_main.php

### class.KMessaging_v1.2.3.php
replaced the word "read" with "readed" as that's what the database field is called.

### user_navigation.tpl
added a button to send a private message to the user's profile page.

### simple_messaging_main.php
changed the function name from GetMessege() to GetMessage() and you no longer need to be friends with a user to be able to send him a message.

Warning: apply these fixes at your own risk. Pligg's official team has not verified this yet.
Pligg is great but it doesn't really work as a forum. I feel the old pligg support was much more user friendly and that this format is holding pligg development back. Anyone else agree?
For those that are unaware disaster struck the other day. My entire house collapsed into a sinkhole and I'm now homeless. I've lost everything but the clothes on my back. The Red Cross has me set up in a motel till tomorrow. I am doing everything I can to find a place to live right now and my resources are very low so I've set up an Indiegogo page about it and updating it as I go. I won't be able to do any custom work, installations, or provide support here until I can get into a place and set up again. Please help me get back to Pligging full time again.

http://www.chuckroast.net/news/everything-has-collapsed/
When you manually delete, as a user and publisher of the story, or as admin delete a story or remove all discarded stories from the Admin panel, the tag_cache table is deleted as well and you are left with no tags in the sidebar or the cloud, until you manually edit a story and add/remove tag or after a new story submit.

To fix this bug, follow these steps:
1- Open adminadmin_delete_stories.php
2- Go to line 82 or look for:

$query="DELETE FROM " . table_tag_cache;
if (!mysql_query($query)) {error_page(mysql_error());}

Insert right after it this code:

$sql="INSERT INTO ".table_tag_cache." select tag_words, count(DISTINCT link_id) as count FROM ".table_tags.", ".table_links." WHERE tag_lang='en' and link_id = tag_link_id and (link_status='published' OR link_status='new') GROUP BY tag_words order by count desc";
if (!mysql_query($sql)) {error_page(mysql_error());}

Save and close
3- Open delete.php
4- Go to line 133 or look for:

$db->query("DELETE FROM ".table_tag_cache);

Insert right after it this code:

$db->query($sql="INSERT INTO ".table_tag_cache." select tag_words, count(DISTINCT link_id) as count FROM ".table_tags.", ".table_links." WHERE tag_lang='en' and link_id = tag_link_id and (link_status='published' OR link_status='new') GROUP BY tag_words order by count desc");

Save and close.

What we did here is we rebuilt the tag_cache table after every delete.

Dear Pligg Developers,

First great job on Pligg 2.0 and the new Pligg site. Thanks!!

Second, I am getting 'Story already in database!:' message with every story that I submit
on Pligg 2.0. . What could be causing this? I did click on clear cache button and try it.