10 days later

Feature request:
A requirement for tag.
Example: Create a criterion for discussions made in tag, or posts made within a specific tag.

    ctml you mean like a number of discussions in a certain tag? It might be useful in some cases.

    Personally, I'd love to see "Auto Moderator" for posts - where you can automate certain tasks in moderation. Like closing a post if it matches certain criteria. Or automatically add tags etc. But this is really out of the scope of this discussion 😆

        GreXXL you mean like a number of discussions in a certain tag? It might be useful in some cases

        Yes exactly, discussions/posts by a particular user within specific tags. So I can call someone an expert in specific categories, and grant them specific badges for those.

        GreXXL I don't necessarily think it is that out of scope at all, sounds exactly like what it's meant to do! 😃 So many possibilities, just need third party extension developers to add their own integrations (+ any relevant core extensions).

        There could also be actions for

        • Lock discussion (provided by AM core integrations or the lock extension itself)
        • Add moderator warning (would need to be added by the mod warnings/notes extension)
        • Post contains text or discussion title contains text (probably added within AM since it is a core feature)
        • Add tag (could be integrated from tags extension or AM)
              4 days later

              I don't know if it is the problem with this extension. When I was testing, the executor of the "Suspend" behavior was shown as the rule creator. is this normal?

                This error will be prompted after opening

                Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/ActivateEmail.php on line 30

Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/ActionDriverInterface.php on line 37

Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/AddToGroup.php on line 34

Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/RemoveFromGroup.php on line 36

Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/Suspend.php on line 40

Deprecated: Required parameter $lastEditedBy follows optional parameter $settings in /www/wwwroot/wyz.xyz/vendor/askvortsov/flarum-auto-moderator/src/Action/Unsuspend.php on line 32

Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in /www/wwwroot/wyz.xyz/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:24 Stack trace: #0 /www/wwwroot/wyz.xyz/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(40): Laminas\HttpHandlerRunner\Exception\EmitterException::forOutputSent() #1 /www/wwwroot/wyz.xyz/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2 /www/wwwroot/wyz.xyz/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(98): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit() #3 /www/wwwroot/wyz.xyz/vendor/flarum/core/src/Http/Server.php(44): Laminas\HttpHandlerRunner\RequestHandlerRunner->run() #4 /www/wwwroot/wyz.xyz/public/index.php(22): Flarum\Http\Server->listen() #5 {main} thrown in /www/wwwroot/wyz.xyz/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 24
                  5 days later

                  shebaoting shebaoting I'm not sure if @askvortsov wants to fix that warning but in any case you can silence the deprecation messages in your PHP configuration and this will solve the issue.

                  If you can edit php.ini, look for the error_reporting directive. If your hosting is managed, this might be called slightly differently. In php.ini there is an example with a recommended value for production which doesn't include any deprecation or warning of any kind.

                      15 days later

                      How can I make like this if user receivelike in more than or equal to 10 in 5 seconds then suspended the user does it possible?

                        8 days later

                        I make a badge (First Like) of metric 1 ≤ x ≤ max / 100000. I tried on other roles also with different user IDs .... It didn't work

                          askvortsov I tried on a group also.

                          I will try with recalculate script.
                          Should I run the recalculate script daily (for good working)?

                            Akito you'll need a custom requirement driver for this.

                            shebaoting I don't know how to solve this problem

                            I would appreciate if you could open a Github issue for this.

                            Silverteal When I was testing, the executor of the "Suspend" behavior was shown as the rule creator. is this normal?

                            Yes, as suspension currently requires an actor. IIRC we are considering anonymizing this, there should be a PR on the suspend repo.

                            ctml I don't necessarily think it is that out of scope at all, sounds exactly like what it's meant to do!

                            I'm planning (another) rewrite of this extension into a generic engine for "When X If Y do Z" rules. Trust levels will go back to being trust levels (the criteria vs metrics vs requirements naming is confusing), just that the actual actions will be generic, and could be applied to all models. We'll also have "when gets trust level" and "when loses trust level" triggers, and "if in trust level" requirements.

                            But yeah this should generalize very nicely across all models. So "when posting, if post contains link and author in trust level "new", flag post for approval" should be just one of the possibilities.

                                    14 days later

                                    @askvortsov How can I give badge like sportive, nature-friendly, emotional etc. to who has more than 10-20 discussions or entry in a specific tag?

                                    For example, someone who created 20 discussion in nature tag should has nature-friendly badge. Is it possible?

                                      Akito that's right, you'll need to set up rules for an extension that supports awarding badges.