Thread Reply Ban Teeth 1.1.1

[Xon]

Xon submitted a new resource:

Thread Reply Ban Teeth - Give thread reply bans more bite.

Give thread reply bans more bite, by providing global options to disable the following functionality in a thread someone is reply banned from;

• Edits
• Deletes
• Likes.

Supports Post Ratings.

I recommend using Install and Upgrade by waindigo or Add-on install & upgrade to install.

If you appreciate...

Read more about this resource...

 

[CTXMedia]

Great idea - and just what I was looking for. Thanks.

 

[CTXMedia]

Just wondering, does this apply retro-actively to already issued reply bans, or does it only apply to new bans after the plugin is installed?

Cheers,
Shaun

 

[Xon]

Just wondering, does this apply retro-actively to already issued reply bans, or does it only apply to new bans after the plugin is installed?

Cheers,
Shaun

It will retroactively apply to all reply-bans.

 

[CTXMedia]

It will retroactively apply to all reply-bans.

Excellent - another great add-on from @Xon - thanks a lot.

 

[Xon]

Xon updated Thread Reply Ban Teeth with a new update entry:

Maintenance update

• Minor code cleanup.
• Remove extra queries in favour of a join for:
  • Viewing watched threads.
  • New posts.
  • Search results by thread.

Read the rest of this update entry...

 

[Marcus]

should be common sense to include this functionality in the core thread ban

 

[Xon]

Xon updated Thread Reply Ban Teeth with a new update entry:

Compatibility update

• Some add-ons may trigger N+1 queries where each post alerts checks the reply ban status of the thread which requires a separate DB query.

Read the rest of this update entry...

 

[jonoathome]

Upgrade to the latest version of addon with Xenforo 1.5.14

Getting this error...

Error Info
ErrorException: Fatal Error: syntax error, unexpected T_STRING, expecting T_CATCH - library/SV/ThreadReplyBanTeeth/XenForo/AlertHandler/DiscussionMessage/Post.php:12
Generated By: LarryHagman, 1 minute ago
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
  ["url"] => string(230) "http://www.sixcrazyminutes.com/index.php?account/alerts-popup&&_xfRequestUri=%2Findex.php%3Fforums%2Fthe-football-forum.4%2F&_xfNoRedirect=1&_xfToken=381%2C1496791850%2C3c9dac064f88fe207eaafef23f3be3401f6c8014&_xfResponseType=json"
  ["_GET"] => array(5) {
    ["account/alerts-popup"] => string(0) ""
    ["_xfRequestUri"] => string(39) "/index.php?forums/the-football-forum.4/"
    ["_xfNoRedirect"] => string(1) "1"
    ["_xfToken"] => string(55) "381,1496791850,3c9dac064f88fe207eaafef23f3be3401f6c8014"
    ["_xfResponseType"] => string(4) "json"
  }
  ["_POST"] => array(0) {
  }
}

 

[Xon]

This add-on requires php 5.5+(updated the add-on description), php 5.4 or php 5.3 do not support the required syntax.

I'ld recommend you upgrade if possible, otherwise can you PM me to discuss pricing to make the required changes for backwards compatibility.

 

[jonoathome]

This add-on requires php 5.5+(updated the add-on description), php 5.4 or php 5.3 do not support the required syntax.

I'ld recommend you upgrade if possible, otherwise can you PM me to discuss pricing to make the required changes for backwards compatibility.

Darn I had a feeling it would be that

When I get some time I will have to build a new server with updated PHP and then migrate the site..

I can't update PHP version on current server as the version of Linux it runs is so old..

I'm Happy to make a donation in the mean time if you can make it backwards compatible, but that being said moving forward, the long term solution I first mentioned is really the better option.. It finding the time to do it though is the problem..

 

[Xon]

XF2 version: https://xenforo.com/community/resources/thread-reply-ban-teeth.5991/

 

[Xon]

Xon updated Thread Reply Ban Teeth with a new update entry:

1.1.1 - Maintenance release

• Reduce SQL queries for global RSS feature.

Read the rest of this update entry...