I think this is critical extension for flarum. I should be updated for beta14 and next releases. I hope fof team lead to this extension.

    fakruzaruret right now that probably wouldn't change much. FoF has a lot of responsibility already, and as an FoF member myself I would probably be end up being the one assigned to it in any case.

    My solution to keep those made-for-clients extensions updated is to have individuals sponsor the updates they need (most are 30min to 1h of work), or have people sponsor my GitHub account which then allows me to make updates and new features based on popular request.

    14 days later

    Version 0.2.4 for beta 13

    • Added queue support
    composer require kilowhat/flarum-ext-mailing:^0.2.4

    Version 0.3.0 for beta 14

    • Added queue support
    • Flarum beta 14
    • The package has changed namespace!
    composer require clarkwinkelmann/flarum-ext-mailing

    To update from beta 13 to beta 14 you will probably need to remove the old extension with composer remove kilowhat/flarum-ext-mailing before starting the update, then install it again once you are running beta 14.

    This update was sponsored by @glowingblue . Thanks!

      clarkwinkelmann

      Thank you. I am not sure if this is caused by another extension, but I've got an issue installing from the beta 13 namespace (kilowat) and for some reason it is requiring beta 14. There are also some mentions to another extension which I already have installed, so not sure why composer is complaining about it when I try to add this one.

      EDIT: sorry just noticed even though I specified old namespace it was still trying to install 0.3.0, I've added the version into the composer require # composer require kilowhat/flarum-ext-mailing:^0.2.4 (not sure if the above command in your post needs it added to for other users installing). Below was what I was getting before.

      # composer require kilowhat/flarum-ext-mailing
      ....
      
          - kilowhat/flarum-ext-mailing 0.3.0 requires flarum/core >=0.1.0-beta.14 <0.1.0-beta.15 -> satisfiable by flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1].
          - Conclusion: don't install flarum/core v0.1.0-beta.14.1

        ctml glad you found a solution.

        I didn't expect this to happen. I thought that once abandoned the package would stop pulling new releases from GitHub. Apparently I was mistaken. I didn't expect the 0.3.0 release to pop up under the kilowhat extension.

        I have now deleted the 0.3.0 release from the kilowhat package, but it might come back automatically. I'll update the command in my post above just in case.

        Unless you're using one of the Redis Queue extensions it's not necessary to install the new version from beta 13. It doesn't change anything to the way the extension works unless you also have an extension ready to handle queuable jobs.

        a month later

        I realize this is provided with minimal support, but just in case it is ever worked on or forked I have a couple of ideas.

        • Allow admins to save HTML templates for emails
        • HTML template can be selected when sending an email
        • The email form would accept inputs for any placeholders created in the email template with validation
        • Preview the generated HTML email once placeholder values are provided before sending
        • Once an email is sent store it in history, similar to your formulaire extension where forms would be equivalent to an email template, and submissions would be sent emails (along with all details)
        • Create saved recipient lists (users, groups, and also allow entry of additional emails that are not registered users)
        • Schedule an email (like scheduled drafts)

          clarkwinkelmann not sure if I could realistically sponsor or not, but I sent you an email to get some more info 🙂

          8 days later

          fakruzaruret and I'm still not actively supporting this extension 🤷‍♂️ Please get in touch if you would like to sponsor some time to update my minimal support extensions.

          a month later

          Bishwas-py you mean the ability to use variables inside of the message body? There currently no such feature, but it could be added as a sponsored feature.

          2 months later