>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #100359. --> Reported by: [druvision](https://www.drupal.org/user/20312) >>> <p>Recently, I've got a requirement from a customer which will highly improve Drupal's usability: viral registration workflow. </p> <p>The challange:<br> The main goal of a new, unregistered user is to add site content.<br> Many people want to add content to my site - and can't - because they are not registered. </p> <p>My Suggested Solution:<br> The idea is simple - automatically present the registration form for anonymous users when they post content. Show the content on site only when the registration is completed. </p> <p>Why is this needed? Because it will highly improve drupal's usability and save tons of times to webmasters.</p> <p>Take a look at the following scenarios and see if you identify yourself in one of them:</p> <p>Scenario 1: You allow unregistered users to post comments, forum topics, etc... For many sites - This IS the desired situation, since it's easy to enter new content to your website. ALAS - users don't register, and you can't communicate with them.</p> <p>Scenario 2: You tried scenario 2 and you get no new content. So you try to allow anonymous users to post content but moderate it. Problem is it takes a lot of time to moderate, and still - users are not registered.<br> Happly, a solution exists - Viral registration.</p> <p>Scenario 3: You tried scenario 1 and 2 and got a lot of spam, and you feel frustrated by the time you invest in deleting blocking the spam. You decide to BLOCK all content entry for unregistered users. ALAS - you are losing alot of users which won't register unless they have a reason or you get much less content.</p> <p>SUGGESTED SOLUTION</p> <p>The idea is simple - OPPOSITE WORKFLOW. For example: </p> <p>petition signup =&gt; registeration form =&gt; user confirms registration approval =&gt; signup approval<br> forum post =&gt; registeration form =&gt; registration email confirmation =&gt; post presented on site<br> comment post =&gt; registeration form =&gt; registration email confirmation =&gt; comment presented on site<br> contact form =&gt; registeration form =&gt; registration email confirmation =&gt; comment presented on site<br> any new node =&gt; registeration form =&gt; registration email confirmation =&gt; node presented on site</p> <p>DETAILS:</p> <p>The detailed use-case is as follows:<br> 1. The unregistered user adds new content and presses the submit botton.<br> 2. The system presents the user with the registration (preferably logintobaggon's) screen with proper explanation of why it's imortant to register.<br> 3. The users fills in the registration details and submits them.<br> 4. The added content is saved in a (new) pending state.<br> 5. The user gets the registration email and clicks on the link to confirm the registration.<br> 6. Registration is confirmed. The new node now gets to the approval queue, or auto-approved (according to the site's policy) and the user my now be optionally presented with a custom confirmation screen which will allow him to invite friends using the invite module (or other similar module).</p> <p>Other requirements:<br> * Prevent content flooding and robotic auto-submissions, by checking the submission's IP.<br> * Reduce spam by integrating with challange modules (captchas or math challange) </p> <p>How to implement it? Where to start? Do you have any comments on the requirements?<br> will be happy to read.</p> <p>Do you want to implement it? We will pay 200$ for the person who submits a complete solution which works with LoginTobaggon and petitions and invite modules. </p>