User Essentials [Paid] [Deleted]

  • Thread starter Thread starter Syndol
  • Start date Start date
In my opinion opening and closing threads is a moderator privilege. When someone wants his thread closed, he can report his thread/post and request it. It should be closed immediately once a moderator notices the report.

The only places where I would allow users to close/open their own threads are in a WTB/WTS marketplace and in their personal blog. If by chance a blog entry or a marketplace thread is in violation of the rules moderators can delete them or move them to an internal trash can forum.
 
Thanks for your reply, however, it does not answer my question in regards to those who do assign the lock permission to certain user groups.
 
While I agree with the above, what happens when the reverse applies?
When a user locks his thread but a moderator opens it. Should that user be forced to entertain replies and not be able to re-lock it?
That seems to defeat the purpose of giving that user permission in the first place. What do you think?
That is a good question... I believe once moderator/administrator has opened the thread, it would be "back to normal", meaning that if the permissions still allow the thread creator to lock the the thread, he or she could do so.
 
I think it all depends on what type of forum you grant the open/close privilege.
The open/close privilege would be specially handy on classified forums, that's where I would use it.

Sell your stuff and when the produkt is sold you can close your thread. A moderator wouldn't re-open that thread, it wouldn't make sense.

When your forum has strict rules on when top open/close a thread, I think it would never be a problem.
 
Syndol updated User Essentials with a new update entry:

Version 1.0.7

What's new:
  • This release only affects those who assign the user group permission that allows users to lock/unlock their own threads.
  • Added a restriction that prevents such a user from unlocking his/her thread after an Administrator or a Moderator has locked it.
Upgrade Instructions:
  1. Upload the folder 'Upload/library/UserEss/' to your server, overwriting the old one
  2. Upgrade the addon-UserEss_107.xml
Thank you.

Read the rest of this update entry...
 
Syndol updated User Essentials with a new update entry:

Version 1.0.8

What's new:
  • Fixed a bug that caused an error when searching thread posts.
Upgrade Instructions:
  1. Upload the file 'Upload/library/UserEss/Model/Post.php' to your server, overwriting the old one
  2. Upload the file 'Upload/library/UserEss/Model/Thread.php' to your server, overwriting the old one
  3. Optional (to display correct version) - Upgrade the addon-UserEss_108.xml
Sorry for the inconvenience.

Read the rest of this update entry...
 
Hello,

Ever since the 1.0.8 update no one on my board has been able to view post edit history, I did not touch any of the settings and after looking around, the options are the same as they were prior to the upgrade.

The last edited by text is just not clickable as a link any more, any ideas?
 
The last edited by text is just not clickable as a link any more, any ideas?
There were no changes to this feature since version 106 so it should work same as always.
The actual edit history (comparing posts) is only available to admins or admins & mods (set via the options page).
This has always been like this and regular members have never been able to view previous versions of the post. They can only view the 'Last edited by' note.
 
There were no changes to this feature since version 106 so it should work same as always.
The actual edit history (comparing posts) is only available to admins or admins & mods (set via the options page).
This has always been like this and regular members have never been able to view previous versions of the post. They can only view the 'Last edited by' note.
Oh I know, I was referring to the fact that staff could not see any post edit history by regular members, however we have just learned after some experimenting that we can see that of other staff members only.

Last Edited by regular members are just not clickable to us staff.
 
Your moderators must be proper moderators assigned to a forum not just part of the "moderating" user group.
If that is the case and they still cannot access the edit history link then I recommend you re-upload all the files and re-upgrade the add-on.
Have you installed any other add-ons since upgrading to 108?
 
Your moderators must be proper moderators assigned to a forum not just part of the "moderating" user group.
If that is the case and they still cannot access the edit history link then I recommend you re-upload all the files and re-upgrade the add-on.
Have you installed any other add-ons since upgrading to 108?
No sir I have not installed any other addons. They are also proper moderators, and my admins nore my self can see regular history by members but we can see the history of staff, that is so weird D:.
 
It works for me both as an admin and a moderator.
I can view the post edit history of both regular members and moderators.
Try upgrading the add-on again.

And make sure you have the Post Edit History option set to 'Yes' as without it the pre-edited post will not be saved!
 
It works for me both as an admin and a moderator.
I can view the post edit history of both regular members and moderators.
Try upgrading the add-on again.

And make sure you have the Post Edit History option set to 'Yes' as without it the pre-edited post will not be saved!
It seems to work now after reupgrading it.

I will keep you posted if we find any more problems, great addon so far!
 
This addon appears to conflict with the Advanced Forum Statistics addon (http://xenforo.com/community/resources/advanced-forum-statistics.597/). I'm not exactly sure why, but when this addon is enabled the threads list uses the thread starter's username and doesn't style it. However, when the addon is disabled, it shows the latest poster in the threads, and styles their username properly. It also displays properly when logged out.
 
Why is it that it is always this add-on that is conflicting with another and never vice versa?

Your issue is due to code in the Forum Statistcs add-on.
In that add-on, open file ******AdvStats/XenForo/Model/Thread.php
locate (line 66):
if (!empty($fetchOptions['******AdvStats_join_last_post']) AND empty($fetchOptions['join'])) {

replace with:
if (!empty($fetchOptions['******AdvStats_join_last_post']) AND !($fetchOptions['join'] & self::FETCH_USER)) {

EDIT:
correction, try:
if (!empty($fetchOptions['******AdvStats_join_last_post']) AND (empty($fetchOptions['join']) || !($fetchOptions['join'] & self::FETCH_USER))) {
 
Back
Top Bottom