ht_miel filtering currently does not seem to take into account capitalization; it filters bad word, but not Bad or bAd

This would probably require regex

    Justoverclock I go to page source, and search for the bad words I entered in admin (bad,word) and I find:
    "addItemToArray":"bad,word"

        ht_miel oops, i forgot to remove console log, u see this in browser console? 😆 i will remove this now

        ht_miel i will work on this 🙂

            0.1.1

            Console log (used for debug) removed.

            Updating

            composer update justoverclock/flarum-ext-purify:"*"
php flarum cache:clear

              Very nice work.

              The video however is giving a

              " Secure connection failed " error in the original post.

              Secure Connection Failed

              An error occurred during a connection to streamable.com. PR_CONNECT_RESET_ERROR

              The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.

                meetdilip Same here and sometimes error connection refused to connect.

                Justoverclock Is there any list that is pre made or all the words are entered by admin only as sometimes what happens, If user is using different language then what's the possible way to get rid of them.

                      1Dot you can add word through admin panel

                      For the video I think is related to streamable website, but not happen to me 🧐

                        0.1.2

                        #Changes

                        • Purifier now support both lowercase and uppercase words like "bad", "bAd", "BAD", "BaD" ht_miel

                        Updating

                        composer update justoverclock/flarum-ext-purify:"*"
php flarum cache:clear

                          • [deleted]

                          • Post #18

                          @Justoverclock an idea here would be to extend this further so that custom REGEX is supported. This is VERY useful in automatically redacting things like email addresses, which under the GDPR, should not appear on public forums without permission. Users have a habit of leaving information like this in the open, and this extension could well fix that.

                          I know @IanM did something similar before with an extension which was originally open source, but is now considered private and no longer available publicly.

                            [deleted] so u mean something that obscure email? sure i can implement this also in this extension

                            or u want a field to put your custom regex from backend?

                                [deleted]

                                0.1.4

                                • Fixed 0.1.3 version that was not compatible with flarum keywords extension (now works fine).
                                • Admin can now choose to automatically mask all email address posted into flarum discussion.


                                Updating

                                composer update justoverclock/flarum-ext-purify:"*"
php flarum cache:clear

                                not sure how can i implement a custom regex field, because i need to decide the function that regexp must have, so i need to replace what/with what?

                                  stimw Friends of Flarum do better extension so my advice is that if fof filter fits your need, go directly to this! 👍🏻

                                  I’m working on a custom regex that replace “custom-regex” simply with ********* or [obscured]…as u like [deleted]

                                      @[deleted] currently i've done a custom regexp field

                                      as u can see in the example anyone can write your own regexp without including the initial / and flags (that actually match every words in both upper and lowercase

                                      in the example above the output is:

                                      /(marco|flarum|extension)/gi (that match these 3 words).
                                      so u can replace that part with your own regexp (marco|flarum|extension)

                                      Do you think this can be an acceptable solution?

                                      regexp is replaced with [Purified] that is completely customizable with translations (like ******, [hidden])

                                      0.1.5

                                      #Changes

                                      • Admin can now setup a custom regular expression

                                      Updating

                                      composer update justoverclock/flarum-ext-purify:"*"
php flarum cache:clear