a month later

0.4.0

  • Flarum beta 15 support
3 months later

0.5.0

  • Update for beta 16
Updating
composer require fof/spamblock:"*"
php flarum cache:clear
2 months later

1.0.0

  • Flarum 1.0 ready
Installation
composer require fof/spamblock:"*"
    17 days later

    IanM Can we change 20 years? I want to prevent user to create e new discussion for 5 days without attaching to another group. How can I do this?

    3 months later

    1.0.1

    • Fixes incorrect composer.json syntax which breaks on Flarum's master branch

    Updating

    composer require fof/spamblock:"*"
    php flarum cache:clear
    4 months later

    CyberGene I don't think so, but through the flarum/suspend extension it should prevent them from liking or un-liking anything anymore.

    This could however be added as a feature to this extension, just like it integrates with suspend.

    a month later

    Spamblock kind of doesn't work anymore:

    /api/users/27/spamblock:1 
    Failed to load resource: the server responded with a status of 404 ()

    I get this message: The requested resource was not found.

    Flarum core 1.2.0
    PHP version: 8.1.2
    MySQL version: 5.5.5-10.3.31-MariaDB-0+deb10u1
    Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache
    +------------------------------------+---------+--------+
    | Flarum Extensions                  |         |        |
    +------------------------------------+---------+--------+
    | ID                                 | Version | Commit |
    +------------------------------------+---------+--------+
    | flarum-flags                       | v1.2.0  |        |
    | flarum-suspend                     | v1.2.0  |        |
    | flarum-markdown                    | v1.2.0  |        |
    | flarum-tags                        | v1.2.0  |        |
    | flarum-likes                       | v1.2.0  |        |
    | afrux-forum-widgets-core           | v0.1.6  |        |
    | fof-spamblock                      | 1.0.2   |        |
    | flarum-subscriptions               | v1.2.0  |        |
    | flarum-approval                    | v1.2.0  |        |
    | v17development-seo                 | v1.8.0  |        |
    | therealsujitk-gifs                 | v4.1.1  |        |
    | sycho-move-posts                   | v0.1.5  |        |
    | nearata-no-self-likes              | v1.2.0  |        |
    | michaelbelgium-profile-views       | v6.0.1  |        |
    | justoverclock-last-post-useravatar | 0.1.7   |        |
    | justoverclock-guestengagement      | 1.0.3   |        |
    | justoverclock-events-countdown     | 0.1.8   |        |
    | justoverclock-contactme            | 0.2.3   |        |
    | fof-username-request               | 1.0.1   |        |
    | fof-user-directory                 | 1.2.2   |        |
    | fof-upload                         | 1.1.0   |        |
    | fof-terms                          | 1.1.2   |        |
    | fof-stopforumspam                  | 1.2.0   |        |
    | fof-split                          | 1.0.1   |        |
    | fof-sitemap                        | 1.0.3   |        |
    | fof-share-social                   | 1.0.1   |        |
    | fof-recaptcha                      | 1.0.0   |        |
    | fof-pretty-mail                    | 1.0.1   |        |
    | fof-polls                          | 1.0.5   |        |
    | fof-pages                          | 1.0.1   |        |
    | fof-nightmode                      | 1.2.0   |        |
    | fof-merge-discussions              | 1.2.0   |        |
    | fof-links                          | 1.0.3   |        |
    | fof-linguist                       | 1.0.3   |        |
    | fof-ignore-users                   | 1.0.2   |        |
    | fof-html-errors                    | 1.0.0   |        |
    | fof-forum-statistics-widget        | 1.0.2   |        |
    | fof-formatting                     | 1.0.2   |        |
    | fof-follow-tags                    | 1.1.1   |        |
    | fof-drafts                         | 1.0.3   |        |
    | fof-disposable-emails              | 1.0.0   |        |
    | fof-default-user-preferences       | 1.0.0   |        |
    | fof-cookie-consent                 | 1.0.2   |        |
    | fof-byobu                          | 1.1.1   |        |
    | fof-bbcode-details                 | 1.0.0   |        |
    | fof-ban-ips                        | 1.0.0   |        |
    | fof-analytics                      | 1.0.0   |        |
    | flarum-sticky                      | v1.2.0  |        |
    | flarum-statistics                  | v1.2.0  |        |
    | flarum-mentions                    | v1.2.0  |        |
    | flarum-lock                        | v1.2.0  |        |
    | flarum-lang-german                 | 1.2.1   |        |
    | flarum-lang-french                 | v3.5.0  |        |
    | flarum-lang-english                | v1.2.0  |        |
    | flarum-emoji                       | v1.2.0  |        |
    | flarum-bbcode                      | v1.2.0  |        |
    | darkle-fancybox                    | 1.0.0   |        |
    | clarkwinkelmann-likes-received     | 1.0.0   |        |
    | clarkwinkelmann-emojionearea       | 1.0.0   |        |
    | clarkwinkelmann-circle-groups      | 1.0.0   |        |
    | askvortsov-moderator-warnings      | v0.6.1  |        |
    | askvortsov-categories              | v3.0.4  |        |
    | afrux-online-users-widget          | v0.1.5  |        |
    | acpl-mobile-tab                    | 1.1.0   |        |
    +------------------------------------+---------+--------+

      m4v3rick Did this start happening after installing an ext? There used to be issues in the past when some exts resolved some stuff a bit too early, which broke other exts that registered routes after them. Looking at the code it seems to me this ext should still be working.

        datitisev

        Can't really tell since we have many extensions. It used to work but I don't really know since when exactly it stopped.
        What could I possible try? Disabling all extensions isn't possible because it's a prod system.

        Another update: I have a local system with almost the same amount of extensions. Spamblocker does work there.
        But I have no idea why not online. I always get: "The requested resource was not found."

        The user is already suspended. So I tried to unsuspend and mark him as spammer again. Didn't work.

          m4v3rick No code in the ext makes it return a 404 (unless I didn't see it) so it has to be another ext doing it. And it is probably an accident.

          It may work locally if the load order is the same. Try copying extensions_enabled from prod DB to local DB to imitate the load order of extensions, and see if you can reproduce the problem locally. If not, add the missing exts that aren't in local and see if any of them trigger it.

            datitisev It may work locally if the load order is the same. Try copying extensions_enabled from prod DB to local DB to imitate the load order of extensions

            Where do I find this? Sorry for that question. 😬

              m4v3rick From the settings table in DB. The entries there have a key and value columns, I believe, so the key should be extensions_enabled.

                datitisev

                Ok, tried to copy it (3 extensions were missing so I skipped them) but it didn't help. Locally still okay.

                21 days later

                m4v3rick Hm, interesting. That error originates from stop forum spam (see the /data/attributes/sfs part of the response).

                That error seems to be different though, as that is status 422 (validation error) vs 404 (not found). Does it give this same error?

                /api/users/27/spamblock:1 
                Failed to load resource: the server responded with a status of 404 ()

                To solve this one, perhaps changing the regional endpoint for StopForumSpam would fix it? Though that is an issue with SFS now and not Spamblock (perhaps error should be clearer on that side too?)

                  datitisev

                  That actually helped a lot. Thanks.
                  Turning StopForumSpam Extension off made Spamblock work.

                  What to do next, if I try to get both extensions working?

                    15 days later

                    m4v3rick Turning StopForumSpam Extension off made Spamblock work.

                    What to do next, if I try to get both extensions working?

                    Push. thx