The Disable Email Verification for Discourse plugin, created by codergautam, aims to bypass email verification during user registration by modifying core Discourse classes. While initially functional, users report it no longer works reliably after Discourse updates — many still see activation prompts despite enabling the plugin, especially with Google SSO or other SSO setups Chukwithak. A known bug also affects invited users codergautam. Although codergautam confirmed it working on their production forum, they caution against production use due to instability and deprecated code codergautam. Multiple users, including Earnie_Baird, Faizan_Zahid, and dahetosohuc, report failures post-update, with dahetosohuc noting it previously worked. codergautam acknowledges the issues and plans to investigate, citing Discourse’s frequent updates as a likely cause. Some users, like tikidave, suggest this should be a core feature, especially for SSO setups. INSIinc has released a rewritten, compatible version of the plugin. The plugin remains tagged as broken, and community members urge fixes for smoother onboarding, as extra verification steps deter modern users satonotdead.
Disable Email Verification for Discourse is a fork of the unmaintained angelim/discourse_user_auto_activation and provides an option for administrators to bypass the email verification step during user registration. No more waiting for email confirmations; get users started immediately.
Install the plugin following the provided installation guide.
Navigate to the admin panel of your Discourse instance.
Go to Plugins and ensure the Disable Email Verification plugin is enabled.
Press on settings.
Locate the disable_email_verification setting and enable it to bypass email verification.
Note: Disabling email verification might lead to potential issues with spam or fake accounts. It’s recommended to use this feature judiciously and consider alternative verification methods.
Technical Aspects
This plugin directly modifies the UsersController and User classes to circumvent the email verification step during the registration process. With the disable_email_verification setting enabled, the plugin ensures:
The email token isn’t created.
The active field of the user is automatically set to true.
For those interested, the entire codebase is open-source and contributions (and stars ) are always welcome.
Roadmap for Disable Email Verification Plugin
Skip Email Verification
Disable Sending Other Emails to Unverified Users
Prevent sending any emails to users who haven’t verified their email address
Just to note @codergautam, all questions/bug reports/support requests for third-party plugins should be asked within their respective plugin topic, as the person maintaining it is responsible for answering/looking after those.
Only questions about official plugins would get separate tagged topics.
Should be fixed now! It’s using a deprecated method (modify_user_params) but other than that works fine. If anyone knows how to use the new alternative for it, please let me know. I tried multiple things but didn’t work. Still don’t use it in production, I will be testing it on my 1.8k member Forum and seeing how it goes.
Hi, I’m using it in production here. https://iogames.forum . It’s working well, no errors so far. If any bugs are there and you find, let me know, I’ll fix it.
I have the SSO set to internal so that only people in our organization can sign in.
I’m wondering if I have some conflict with another SSO. I don’t think I should but maybe that’s the case?
I have nextend SSO set up for my WordPress site to register and sign in for an internal application because we have workspace.
I have the website pointing to my community on a subdomain. Then I have connect SSO and all the plugin stuff activated (although I don’t think my hd2 and groups is setup right)
) are always welcome.
