Navigation

Pligg Support

6
Question: *** URGENT. NEED answers about the functionality of Groups
Answer: provided by Yankidank 77 days ago
- 2 + The site-wide moderator role should be capable of changing the story status (publish, new, discard). The killspam feature is probably too powerful for the role though, which is a feature that they currently have access to. I'm fine with giving them the ability to enable users from the admin panel, but disabling users may be excessive.

Moderators should be able to edit a story just like the author, in case they need to remove personal info or they have some other cause. Site moderators should also have the ability to manage groups or a user's profile.

Moderators differ from admins because they are applying content-specific changes. For example, editing a story, editing a group, and editing a user. Admins are making changes to site-wide settings like the Language file, configuring the site, managing modules, etc.. Using this logic, I think that the domain whitelist and blacklist pages needs to be be restricted to admins.
6
Question: *** URGENT. NEED answers about the functionality of Groups
Answer: provided by Yankidank 74 days ago
- 0 + Thanks for the update. I'm awaiting your final version before trying to integrate the changes or performing any group changes myself.
6
Question: *** URGENT. NEED answers about the functionality of Groups
Answer: provided by Yankidank 71 days ago
- 0 + First, before I respond to the video I want to say thank you to Redwine for his hard work in helping to define and execute the proper permissions for user roles across Pligg CMS. These updates will allow people to finally use these user roles as they were imagined and will address a lot of security issues that exist in previous iterations.

I am going to break up my thoughts into numbered paragraphs so that you can reference those when composing a response.

1. I didn't realize that we had an open bug that allows moderators to change user roles. I thought that was something that was patched, so it's a problem that needs fixed ASAP.

2. The only field in your permissions table that does not line up with what I imagined is the (group) Moderator value for "Edit Group Info". In the video that field is set to "YES", when it should probably be "NO". Group moderators should not be able to edit the name, description, privacy setting, or voting number for a group.

3. Your Admin permissions are more restrictive than what I imagined, but it makes perfect sense after I thought about it.

4. The "Group story status" dropdown link should not be available to the Kris account since the user is not a group moderator (it's a normal user". Additionally the "Manage Kris" link shouldn't show since moderators shouldn't have the ability to edit user account details like admins.

5. The Group Story Status discard feature was operating as I had previously imagined (deleting it from the group, but leaving it in the main site's new or home areas). This point may be up for debate because I could see it as making sense either way. The reason why I chose to not completely discard it from the site from the Group page is because the story might have been shared to other groups, or popular enough to make it to the front page, but for one reason or another someone wanted to remove it from their group. Perhaps the best solution would be to offer 2 options: Discard from Group and Discard from Site for normal users.

6. I totally agree that site admins should be able to view and moderate all group content. So yes, please give them access to see private group data. I would even recommend allowing site moderators to see what private groups are publishing, since they are the ones who are most responsible for moderating content across the site.
4
Question: I cant add new stories on my site - not sure whats broken :(
Answer: provided by Yankidank 91 days ago
- 2 + I hadn't heard of this feature being broken before, as it wasn't reported to Github. I'll have to check it out.
3
Question: URL is invalid or blocked
Answer: provided by Yankidank 97 days ago
- 2 + Here is the official fix that we will be using in re-packaged 2.0.2 release. https://github.com/Pligg/pligg-cms/commit/69b6d578f7db500cb478fffaed91563f13af7040
3
Question: FIX to settings-from-db file
Answer: provided by Yankidank 100 days ago
- 2 + Thanks for your contribution. It didn't show up as a Pull request on Pligg's Github page, but I've manually applied the changes and re-bundled Pligg 2.0.2 to include the changes in the 2.0.2.zip file found here: https://github.com/Pligg/pligg-cms/releases/tag/2.0.2
2
Question: Submit doesn't work (nginx)
Answer: provided by Yankidank 100 days ago
- 1 + If you plan on using SEO URLs on a Varnish/Nginx server, here is a link to some code that we put together for Pligg.com's own /support area.

http://pastebin.com/TxQTzU9f
1
Question: multiple website problem
Answer: provided by Yankidank 102 days ago
- 2 + If you move Pligg files from the root of a domain into a subdirectory you will need to add a $my_pligg_base value (example: '/newweb') to the settings.php file. You will also need to apply this setting to your database under Admin > Configure > Location Installed > Pligg Base Folder.

If that doesn't answer your question, you are going to have to be a lot more specific wit your question.
3
Question: ** FIX ** for the Friends and simple messaging features
Answer: provided by Yankidank 102 days ago
- 2 + It took me a while, but I eventually was able to merge your code in with the latest. I ended up needing to put a lot of additional polish work on it, but I think the whole follower system and mutual messaging works as expected. Thanks for your help.

https://github.com/Pligg/pligg-cms/commit/03fe0ef7efd2ef4df5563090e41041df1d953b1d
5
Question: *URGENT* Need feedback to proceed fixing the issues
Answer: provided by Yankidank 106 days ago
- 2 + I'm going to wait on releasing version 2.0.1 until you come up with a fix for this since you are already working on it. I agree that both people need to friend each other before they should be able to send a message.

Make sure that you are using the latest development version so that we can integrate the fix as easily as possible.

https://github.com/Pligg/pligg-cms