So I finally ran the 2.0 compatibility check and turns out most of my incompatible extensions aren't a big deal — I can just drop them or wait around for updates, no biggie. But there's one that's a total dealbreaker for me right now: clarkwinkelmann/flarum-ext-email-whitelist — no compatible release yet (still sitting at 1.0.0). #28377 I use this to lock down registrations to a specific set of email domains via regex, so it's kind of essential to how my forum runs: /^[\w.+-]+@(gmail\.com|proton(mail)?\.(me|com|ch)|pm\.me|outlook\.(com|[a-z]{2,3})(\.[a-z]{2,3})?|[\w-]+(\.[\w-]+)*\.edu(\.[a-z]{2,3})?)$/i if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Without this working, registration basically turns into a free-for-all on my forum, so I can't pull the trigger on 2.x until there's some kind of fix or alternative. Clark posted an update back in April #2528741 saying he'd prioritize 2.0 compatibility for his "actively maintained" extensions. That was months ago though, so no idea if email-whitelist made the list — just hoping it's still coming. Anyway, that got me wondering — for everyone else out there still on 1.x, what's the one extension that's actually stopping you from upgrading? Curious how much overlap there is across the community, might be useful to see what's the biggest pain point holding people back.

Upgrading to 2.x — blocked by Email Whitelist, curious what's holding you up?

DLBB

So I finally ran the 2.0 compatibility check and turns out most of my incompatible extensions aren't a big deal — I can just drop them or wait around for updates, no biggie. But there's one that's a total dealbreaker for me right now:

clarkwinkelmann/flarum-ext-email-whitelist — no compatible release yet (still sitting at 1.0.0). #28377

I use this to lock down registrations to a specific set of email domains via regex, so it's kind of essential to how my forum runs:

/^[\w.+-]+@(gmail\.com|proton(mail)?\.(me|com|ch)|pm\.me|outlook\.(com|[a-z]{2,3})(\.[a-z]{2,3})?|[\w-]+(\.[\w-]+)*\.edu(\.[a-z]{2,3})?)$/i

Without this working, registration basically turns into a free-for-all on my forum, so I can't pull the trigger on 2.x until there's some kind of fix or alternative.

Clark posted an update back in April #2528741 saying he'd prioritize 2.0 compatibility for his "actively maintained" extensions. That was months ago though, so no idea if email-whitelist made the list — just hoping it's still coming.

Anyway, that got me wondering — for everyone else out there still on 1.x, what's the one extension that's actually stopping you from upgrading? Curious how much overlap there is across the community, might be useful to see what's the biggest pain point holding people back.

ClaudiusH

DLBB I get that you have more control to which domains you actually block registrations from using Clarke's extension. But did you know that #33698 also checks new registrations against known spammers and auto rejects those? Maybe that would work out for you instead.

DLBB

Thanks for the suggestion! I'm actually already running fof-anti-spam 2.0.0-rc.1 — but I still want Email Whitelist on top of it. Just want that extra peace of mind, lol.

I actually tried using extend.php in the meantime, but Gemini sucks at it and kept giving me broken code. Just waiting for my Claude usage to refresh so I can try again properly.

DLBB

Update: wrote a temporary extend.php snippet enforcing an email domain whitelist while waiting on the official extension. It hooks into Saving, with an admin bypass:

<?php

use Flarum\Extend;
use Flarum\Foundation\ValidationException;
use Flarum\User\Event\Saving;
use Illuminate\Support\Arr;

return [
    (new Extend\Event())
        ->listen(Saving::class, function (Saving $event) {
            if ($event->actor->isAdmin()) {
                return;
            }

            $email = Arr::get($event->data, 'attributes.email');

            if (is_string($email) && !empty($email)) {
                $pattern = '/^[\w.+-]+@(gmail\.com|proton(mail)?\.(me|com|ch)|pm\.me|outlook\.(com|[a-z]{2,3})(\.[a-z]{2,3})?|[\w-]+(\.[\w-]+)*\.edu(\.[a-z]{2,3})?)$/i';

                if (!preg_match($pattern, $email)) {
                    throw new ValidationException([
                        'email' => 'Registration is limited to Gmail, Outlook, Proton, and .edu email addresses.',
                    ]);
                }
            }
        }),
];

It runs on every save, not just registration. Anyone see risks with this approach — conflicts with other extensions, edge cases, etc.?