[AddonFlare] XF2 Ignore/Block Essentials [Deleted]

This should be a 5 minute fix and therefore should be implemented as soon as possible. As it stands, this resource doesn't comply with resource standard #11, particularly the point in bold:
11. The following should be adhered to with respect to schema changes:
  1. New tables must be prefixed with xf_ and additionally an identifier for the add-on e.g. xf_mg_.
  2. New columns to core tables must be prefixed with an identifier for the add-on e.g. xfmg_.
  3. New columns to core tables must have a default value or be nullable.
  4. Any new tables or columns added must be removed on uninstall.
  5. Where possible, an add-on should not change the definition of a core column.
Please let us know when the issue will be rectified.
 
Appreciate the update.

I guess I misunderstood how this plugin works...it REPLACES the existing Ignore with one that's far more aggressive...instead of adding a new Block feature.
 
Hi @AddonFlare ,

we did try to use our Licence in our Test Forum ( Live Data in example.com our testforum is at test.example.com ). We get following error Message:

1583015967689.webp

Is the Licence not eligible to be used in a Test Forum beside to the life Data

Kind Regards
 
Looking for this kind of addon to allow users to ignore threads especially. Do I understand correctly that this is ONLY in order to ignore users?

Have you had time to have this done?

This should be a 5 minute fix and therefore should be implemented as soon as possible. As it stands, this resource doesn't comply with resource standard #11, particularly the point in bold:

11. The following should be adhered to with respect to schema changes:
  1. New tables must be prefixed with xf_ and additionally an identifier for the add-on e.g. xf_mg_.
  2. New columns to core tables must be prefixed with an identifier for the add-on e.g. xfmg_.
  3. New columns to core tables must have a default value or be nullable.
  4. Any new tables or columns added must be removed on uninstall.
  5. Where possible, an add-on should not change the definition of a core column.
Please let us know when the issue will be rectified.

Also, what if a member decided to ignore admins or moderators, is there an option to protect against that?

Thanks!
 
Do I understand correctly that this is ONLY in order to ignore users?
Yes, this is currently for ignoring users and their content. Not specific content
Have you had time to have this done?
Yes, an update was released that same day
Also, what if a member decided to ignore admins or moderators, is there an option to protect against that?
Users aren’t allowed to ignore “staff”. They’ll get an error if they try
 
Would like two abilities:

1> Admin/mod can add two people to a ignore for each other. Force Users A and B not to be able to interact.

2> Can have a usergroup automatically added to the global ignore, instead of the manual way it is done right now. This is useful as a warning/punishment tool. Someone acts out, you don't have to go to admin panel. instead you could just add warning points, they are added to the user group that is then global ignored. When the warning runs out over time, they would be auto unignored. This would be a very powerful moderating tool. Just silence the trouble maker for a breath for everyone else and not have to remember to undo it.
 
Would like two abilities:

1> Admin/mod can add two people to a ignore for each other. Force Users A and B not to be able to interact.

2> Can have a usergroup automatically added to the global ignore, instead of the manual way it is done right now. This is useful as a warning/punishment tool. Someone acts out, you don't have to go to admin panel. instead you could just add warning points, they are added to the user group that is then global ignored. When the warning runs out over time, they would be auto unignored. This would be a very powerful moderating tool. Just silence the trouble maker for a breath for everyone else and not have to remember to undo it.
These are good suggestions, we'll see how we can implement them moving forward.
 
Hey. I purchased five licenses and tried to get one of my domains to work - but there was a licensing issue. Is this a common issue? I actually tried using two of my licenses as the first was http and the second I used https...
 
Got this error:

Code:
Server-Fehlerprotokolle

[E_NOTICE] Undefined index: reaction_id
Gestern um 08:17 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php:56
[E_NOTICE] Undefined index: reaction_id
Gestern um 08:16 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php:56
[E_NOTICE] Undefined index: reaction_id
Gestern um 08:16 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php:56





Server-Fehlerprotokoll
ErrorException: [E_NOTICE] Undefined index: reaction_id src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php:56
Generiert von: Maatiin 10 März 2020 um 08:17
Stack-Trace
#0 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php(56): XF::handlePhpError(8, '[E_NOTICE] Unde...', '/var/www/html/p...', 56, Array)
#1 src/XF/Mvc/Entity/Entity.php(148): AddonFlare\GlobalIgnore\XF\Entity\Post->getReactionUsers()
#2 src/XF/Mvc/Entity/Entity.php(101): XF\Mvc\Entity\Entity->get('reaction_users')
#3 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php(18): XF\Mvc\Entity\Entity->__get('reaction_users')
#4 src/XF/Mvc/Entity/Entity.php(148): AddonFlare\GlobalIgnore\XF\Entity\Post->getReactions()
#5 src/XF/Mvc/Entity/Entity.php(101): XF\Mvc\Entity\Entity->get('reactions')
#6 src/XF/Repository/Reaction.php(110): XF\Mvc\Entity\Entity->__get('reactions')
#7 src/XF/ControllerPlugin/Reaction.php(190): XF\Repository\Reaction->getContentTabSummary('post', 1461421)
#8 src/XF/Pub/Controller/Post.php(383): XF\ControllerPlugin\Reaction->actionReactions(Object(AddonFlare\GlobalIgnore\XF\Entity\Post), 'posts/reactions', Object(XF\Phrase), Array)
#9 src/XF/Mvc/Dispatcher.php(350): XF\Pub\Controller\Post->actionReactions(Object(XF\Mvc\ParameterBag))
#10 src/XF/Mvc/Dispatcher.php(261): XF\Mvc\Dispatcher->dispatchClass('XF:Post', 'Reactions', Object(XF\Mvc\RouteMatch), Object(Andy\InsertAttachment\XF\Pub\Controller\Post), NULL)
#11 src/XF/Mvc/Dispatcher.php(113): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(Andy\InsertAttachment\XF\Pub\Controller\Post), NULL)
#12 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#13 src/XF/App.php(2184): XF\Mvc\Dispatcher->run()
#14 src/XF.php(391): XF\App->run()
#15 index.php(20): XF::runApp('XF\\Pub\\App')
#16 {main}
Status der Anfrage
array(4) {
  ["url"] => string(207) "/forums/posts/1461421/reactions?_xfRequestUri=%2Fforums%2Fthreads%2Fsieger-der-berichtswahl-august-september.39810%2F&_xfWithData=1&_xfToken=1583824555%2Cd2c763cfe4a644c56f906174e5615a9a&_xfResponseType=json"
  ["referrer"] => string(91) "https://www.pattayaforum.net/forums/threads/sieger-der-berichtswahl-august-september.39810/"
  ["_GET"] => array(4) {
    ["_xfRequestUri"] => string(63) "/forums/threads/sieger-der-berichtswahl-august-september.39810/"
    ["_xfWithData"] => string(1) "1"
    ["_xfToken"] => string(43) "1583824555,d2c763cfe4a644c56f906174e5615a9a"
    ["_xfResponseType"] => string(4) "json"
  }
  ["_POST"] => array(0) {
  }
}
 
Is there a setting that'll allow a member to BLOCK another member - but still see their new TOPICS (first post only)? As soon as I setup this add-on, a few members asked about this. It KINDA looked like this was possible in the settings - but I don't have it working - so here I am...
 
Still have this error:
Running on 2.1.7

Code:
Server-Fehlerprotokoll

    ErrorException: [E_NOTICE] Undefined index: reaction_id src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php:56

    Generiert von: Maatiin 15 März 2020 um 15:44

Stack-Trace

#0 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php(56): XF::handlePhpError(8, '[E_NOTICE] Unde...', '/var/www/html/p...', 56, Array)
#1 src/XF/Mvc/Entity/Entity.php(148): AddonFlare\GlobalIgnore\XF\Entity\Post->getReactionUsers()
#2 src/XF/Mvc/Entity/Entity.php(101): XF\Mvc\Entity\Entity->get('reaction_users')
#3 src/addons/AddonFlare/GlobalIgnore/Entity/IgnoreReactionTrait.php(18): XF\Mvc\Entity\Entity->__get('reaction_users')
#4 src/XF/Mvc/Entity/Entity.php(148): AddonFlare\GlobalIgnore\XF\Entity\Post->getReactions()
#5 src/XF/Mvc/Entity/Entity.php(101): XF\Mvc\Entity\Entity->get('reactions')
#6 src/XF/Repository/Reaction.php(110): XF\Mvc\Entity\Entity->__get('reactions')
#7 src/XF/ControllerPlugin/Reaction.php(190): XF\Repository\Reaction->getContentTabSummary('post', 1155957)
#8 src/XF/Pub/Controller/Post.php(383): XF\ControllerPlugin\Reaction->actionReactions(Object(AddonFlare\GlobalIgnore\XF\Entity\Post), 'posts/reactions', Object(XF\Phrase), Array)
#9 src/XF/Mvc/Dispatcher.php(350): XF\Pub\Controller\Post->actionReactions(Object(XF\Mvc\ParameterBag))
#10 src/XF/Mvc/Dispatcher.php(261): XF\Mvc\Dispatcher->dispatchClass('XF:Post', 'Reactions', Object(XF\Mvc\RouteMatch), Object(Andy\InsertAttachment\XF\Pub\Controller\Post), NULL)
#11 src/XF/Mvc/Dispatcher.php(113): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(Andy\InsertAttachment\XF\Pub\Controller\Post), NULL)
#12 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#13 src/XF/App.php(2184): XF\Mvc\Dispatcher->run()
#14 src/XF.php(391): XF\App->run()
#15 index.php(20): XF::runApp('XF\\Pub\\App')
#16 {main}

Status der Anfrage

array(4) {
  ["url"] => string(209) "/forums/posts/1155957/reactions?_xfRequestUri=%2Fforums%2Fthreads%2Fmeine-ausgaben-von-der-letzten-reise.32477%2Fpage-3&_xfWithData=1&_xfToken=1584283429%2Cc9dc4f83bf34bf87cd2f9373701575f1&_xfResponseType=json"
  ["referrer"] => string(93) "https://www.pattayaforum.net/forums/threads/meine-ausgaben-von-der-letzten-reise.32477/page-3"
  ["_GET"] => array(4) {
    ["_xfRequestUri"] => string(65) "/forums/threads/meine-ausgaben-von-der-letzten-reise.32477/page-3"
    ["_xfWithData"] => string(1) "1"
    ["_xfToken"] => string(43) "1584283429,c9dc4f83bf34bf87cd2f9373701575f1"
    ["_xfResponseType"] => string(4) "json"
  }
  ["_POST"] => array(0) {
  }
}
 
Top Bottom