I got this error

./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals

[RuntimeException]
Failed to clone https://github.com/askvortsov1/flarum-moderator-strikes.git via https, ssh protocols, aborting.



require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] [<packages>]...

@askvortsov I believe there's an issue with a default email template.

Emails are displaying reset passwords and tags strings.

Hey {!! $user->display_name !!}!

{!! $blueprint->getEmailSubject() !!}

{!! $url->to('forum')->route('savePassword') !!}

{!! $translator->trans('core.views.reset_password.new_password_label') !!}

{!! $translator->trans('askvortsov-moderator-warnings.admin.permissions.manage_warnings') !!}


{!! $url->to('forum')->route('tags') !!}

The following reason was given:

---

{!! $blueprint->warning->public_comment !!}

EDIT: One more thing

Other moderators do not see warning messages in posts (not even ones set by them), despite the "View moderator warnings" permission set on public.

    hrvoje_hr Emails are displaying reset passwords and tags strings.

    Wow this is awkward... No idea how it got in there, sorry about that!

    hrvoje_hr Other moderators do not see warning messages in posts (not even ones set by them), despite the "View moderator warnings" permission set on public

    Fixed (as well as the template thing) in v0.2.1, thanks for reporting!

        askvortsov Can you please add a feature of automatic warning expiration after X duration

        For example: Warning expires in 30 days or so
        With this feature, warned users will learn what they were warned for and yet they will be given a chance to be at ease they've not been warned forever.

        This feature is available widely on many sites including facebook.

            HD3D This sounds very useful, yet very tricky. You better not forget who got warned for what, writing down notes about bad-behaving users is usually a good idea (the moderator notes extension should do the job)
            In addition to your suggestion, strikes should decide the duration before a warning gets vanished. For example, 1 strike = 1 week, 2 strikes = 2 weeks, 3 strikes = 1 month and so on... maybe leave it optional for admins to set the duartions. But yeah, definitely agreeing with this 🙂

                Mark73 I'd probably approach this so that the warnings remain permanently, but the strikes themselves expire and no longer count against the user, how's that?

                    askvortsov Love it, this will make it unnecessary to write down notes. Though, I wonder when would strikes be any useful and intergate with the suspend extension, any ETA?

                      askvortsov Could be great but if the warnings remain permanent but it will create a problem once we get this feature:

                      • Suspend integration (automatically suspend if users reach more than X warnings, with X configurable in settings)

                      If the warnings are gonna remain permanent then we may get many users suspended over the years.

                          HD3D Yeah, I was asking myself about that too, so I guess setting the strikes as the duration deciders would be good, what do you think?

                              Mark73 I prefer suspension integration with expire-able strikes as you suggested above instead of warnings if @askvortsov decides warnings to remain permanent.

                                  HD3D if I make strikes expire, expired strikes would not count towards suspend thresholds.

                                  I do think that having permanent records is good though, both to help mods and prevent abuse.

                                      askvortsov That's the point, expired strikes should not count towards suspend thresholds so only new warnings with new strikes should be counted
                                      And for permanent records I think moderator notes entry will be good enough

                                        17 days later

                                        @askvortsov What I currently not understand is the idea of the strikes. If I for example give 5 strikes to a user. What does it really mean? Is a 5 strike more serious than a 4 strike? Or do I count down with each additional warning? Maybe you can explain that a little. Many thx

                                          MrB sure! The number of strikes is representative of the severely of the warning. This is exclusively for your use as an admin/moderator. At later times, I may include integrations where users would be automatically suspended after reaching a number of strikes

                                            a month later
                                            a month later

                                            Why not set some preset warning reasons? And you can also add a warning button to the flag bar.

                                            a month later

                                            Nice extension.
                                            In the email the motivation given to the user is showed with some strange strings

                                            <t><p>You are spamming!</p></t>

                                              17 days later