No announcement yet.

Self Moderated

  • Filter
  • Time
  • Show
Clear All
new posts

  • Self Moderated

    We are trying to set up a new Usergroup where members are allowed to post without moderation after 30 days registered and 5 approved posts.

    We have created a new usergroup named "Self Moderated" and a scheduled task to move members that qualified members into that group when those conditions are met. We ran the task successfully after creating the usergroup, and it found and changed all member who were qualified. It is set to run every hour.

    The problem is that although we have set the forum post permissions to what seem to be needed, those who are in the new Self Moderated group are still put into moderation as before.

    Any ideas?


  • #2
    Do you have the spam scanner enabled?


    • #3
      No, we do not.


      • #4
        Can you apply the changes here:

        Clear your system cache, and then resave all of your usergroup permissions in the usergroup manager. See if the issue persists.


        • #5
          I'll do it first thing in the morning here in California. Thank you.


          • #6
            See PM to you please.


            • #7
              Please do not pm me, you can start a ticket if you require private support.


              • #8
                I apologize, I thought that since you sent me the instructions in that mode it would be better to follow suit. Here is my question again:

                Just to be clear, is this what you are suggesting for me to do?
                And I suppose I would use the usergroupid that I want to be promoted to self moderation, correct?

                Thanks for your help.

                open the file /core/includes/adminfunctions.php, and add "//" (without quotes) at the beginning of the following lines:
                vB_Cache::instance()->write('channelperms_' . $usergroup[usergroupid], array(), 0, 'perms_changed');
                vB_Cache::instance()->write('channelperms_' . $groupid, $chanperms, 1440, 'perms_changed');
                vB_Cache::instance()->write($hashkey, $perms, 1440, 'perms_changed');
                These will be at lines 3772, 3789 and 4118 respectively.
                After making this change to the file, clear cache in admincp.


                • #9
                  Follow the bug reports instructions.


                  widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.