vBulletin Registration – Condensed changelog
This is the short summary for operators who want to copy the registration-related changes into a separate document.
2026-05-10
- Public wording now uses clearer registration language instead of leaning on the word onboarding.
- The default Messenger and email templates are now more pedagogical and explicitly tell recipients to contact
support@tornevall.net and the person who sent the invite if the code or link does not work.
- The audit trail now shows more clearly when someone opens the registration page, uses the invite code to create a registration request, and reopens the personal registration status page.
2026-05-07
- Invite keys can now store the recipient's email address.
- Admins and delegated key creators now have a built-in Messenger/email composer directly on the key pages.
- The same invite flow can now send a real HTML email to the recipient or a test copy to the current Tools account.
2026-05-06 to 2026-05-07
- The Snöbollseffekten guide and the public wording now explain the registration flow more clearly step by step.
- The key pages make it easier to see who received which invite key and where approved users should continue afterwards.
2026-05-02 to 2026-05-05
- The existing-forum-account-first flow became clearer: the invite code can be stored in the profile field first and the Tools-side registration step can be started afterwards.
- Invite keys can now be batch-created with more flexible expiry handling.
- Default group
155 is now used when a registration flow has no explicit allowed groups configured.
- History is stored when an older invite value is replaced in a profile field.
2026-04-27 to 2026-04-30
- The public vBulletin registration flow and the related admin pages were launched in Tools.
- Each registration flow got its own slug, intro text, rules, status page, and review queue.
- Invite keys support both reusable invite links and one-time keys.
- Public pages and status pages are available in both Swedish and English.
- Limited group handling towards vBulletin was added so approved registrations can grant the correct forum group directly.
Practical summary
If you only need the most important points right now:
- use words like registration, registration link, registration code, and registration status in communication
- use the built-in Messenger/email templates as the starting point
- always mention
support@tornevall.net and the inviter when the code does not work
- use the admin audit trail to see when the link was opened, when the code was used, and when the status page was checked