Ban Ignored/Specified Users from Replying v2.0

Ban Ignored/Specified Users from Replying v2.0

Description
This hack will prevent ignored users from replying to your threads, as well as give you the option to ban additional users without adding them to your ignore list.

Information
This hack was previously titled "User-Defined Posting Bans (Ban specified users from replying)"

Tested on RC4, should work on RC1+

Version History
v1.0 - Initial Release
v2.0 - Added auto-ban of ignored users, created installer script for convenience

Click here for upgrade instructions from 1.0!

Planned Features
v3.0
- Who knows? You tell me.

If you use this, please click

[Allan]

After this :

PHP Code:

##############################################################
ALTER TABLE " . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250 ) NOT NULL ;
############################################################## 


this sql error

PHP Code:

requ?te SQL :  

ALTER TABLE " . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250 ) NOT NULL 

MySQL a r?pondu:


#1064 - Erreur de syntaxe pr?s de '" . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250  )  NO' ? la ligne 1
[Documentation] ? [Retour] 


an idea (on RC3) ?

[bluecat]

Is it possible that only certain usergroups (who I specify) can use the hack?

[magnus]

Originally Posted by Socrate

After this :

PHP Code:

##############################################################
ALTER TABLE " . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250 ) NOT NULL ;
############################################################## 


this sql error

PHP Code:

requ?te SQL :  

ALTER TABLE " . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250 ) NOT NULL 

MySQL a r?pondu:


#1064 - Erreur de syntaxe pr?s de '" . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250  )  NO' ? la ligne 1
[Documentation] ? [Retour] 


an idea (on RC3) ?

Hrm, are you including the ";" at the end? There's no reason for that query not to work, you can try removing the " . TABLE_PREFIX ." portion (provided you don't actually use a table prefix).

[magnus]

Originally Posted by bluecat

Is it possible that only certain usergroups (who I specify) can use the hack?

Sure, encompass the template edits with:

<if condition="$bbuserinfo[usergroupid]==XX">

<!-- TEMPLATE, BLAH CRAP... -->

</if>

Of course, replace "XX" with the usergroup you wish to allow.

[Allan]

Originally Posted by magnus

Hrm, are you including the ";" at the end? There's no reason for that query not to work, you can try removing the " . TABLE_PREFIX ." portion (provided you don't actually use a table prefix).

idem

PHP Code:

You have an error in your SQL syntax.  Check the manual that corresponds to your MySQL server version for the right syntax to use near '" . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250  )   NO' ? la ligne 1 


on a RC3 coldly to install :surprised:

[Allan]

Originally Posted by Socrate

idem

PHP Code:

You have an error in your SQL syntax.  Check the manual that corresponds to your MySQL server version for the right syntax to use near '" . TABLE_PREFIX . "thread ADD bannedposters VARCHAR( 250  )   NO' ? la ligne 1 


on a RC3 coldly to install :surprised:

veiled the solution

PHP Code:

ALTER TABLE thread ADD bannedposters VARCHAR( 250 ) NOT NULL ; 


thank at Pithchoume

[magnus]

Originally Posted by magnus

Hrm, are you including the ";" at the end? There's no reason for that query not to work, you can try removing the " . TABLE_PREFIX ." portion (provided you don't actually use a table prefix).

Originally Posted by Socrate

veiled the solution

PHP Code:

ALTER TABLE thread ADD bannedposters VARCHAR( 250 ) NOT NULL ; 


thank at Pithchoume

That's what I said to do, heh. Seems RC3 doesn't like " . TABLE_PREFIX . " .. odd.

[magnus]

BUGFIX!
With the existing preg_split() statement, users with spaces in their name could cause problems for other users which share a common world. For example, if the user "BIG BAD GUY" is banned from a thread, inherently the user "BIG BOY" would be banned because of the shared word, "BIG". With the following fix, that will be fixed:

In newreply.php:

Find: ** NOTE, THERE ARE TWO INSTANCES OF THIS, REPLACE BOTH! **

$usernames = preg_split('/( )+/', trim(strtolower($threadinfo['bannedposters'])), -1, PREG_SPLIT_NO_EMPTY);

Replace with:

$usernames = preg_split('/,+/', trim(strtolower($threadinfo['bannedposters'])), -1, PREG_SPLIT_NO_EMPTY);

The only drawback to this fix, is now users are comma delimited instead of space. So, you'll need to update the phrase (bannd_users_desc) to reflect this, personally, I use List of users, separated by commas, who cannot reply to this thread. (ie. user1,user2).

This has been updated in the attachment in the first post, only existing users need to concern themselves with this.

[Allan]

I have to install 2 times the hack, I have a sql error when I click on the button "newthread", I specify that I am in rc3, year idea on the problem?

Error Sql:

PHP Code:

There seems to have been a slight problem with the Local Rc3 database.
Please try again by pressing the refresh button in your browser.

An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.

We apologise for any inconvenience 


another thing about the bugfix, this line does not exist in the RC3 In "newthread.php":

PHP Code:

$usernames = preg_split('/( )+/', trim(strtolower($threadinfo['bannedposters'])), -1, PREG_SPLIT_NO_EMPTY); 


[magnus]

Originally Posted by Socrate

another thing about the bugfix, this line does not exist in the RC3 In "newthread.php":

PHP Code:

$usernames = preg_split('/( )+/', trim(strtolower($threadinfo['bannedposters'])), -1, PREG_SPLIT_NO_EMPTY); 


Yikes! I meant newreply.php, sorry for the confusion. I fixed that in the post above.

As for the other problem, you'll need to show me the error. View the source of the HTML page when that error is generated, and post it here.