XF 2.2 Writing before registering

1591365714263.png
Participation. It's the life blood of a forum, and once you have a group of dedicated members creating and discussing content, your forum will flourish.

But there's a barrier to entry when it comes to participation. When a new visitor stumbles upon your forum from a search engine, they may read the content that piqued their interest and then feel inclined to add their own thought-provoking response, but at that point they are confronted with the dreaded

1591364826548.png


... at which point, in many cases, the whim disappears and they disappear like a stranger in the night.

The prospect of having to complete a form and go through the rigmarole of signing-up to a new service is quite a turn-off to new visitors, for obvious reasons. Visitors have a reticence to registration because they often consider it not to be worth their time.

So, what if they had something to lose by not completing the registration process?

This is the thought behind Writing Before Registering. When enabled, guest users will be granted access to the New Thread button and the Quick Reply editor and various other tools that are available to registered members. The experience is almost identical to that of a logged-in user, allowing the guest to create rich content before having registered, such that they can compose the message they want without obstructions.

What a lovely post. Now register or lose it.

And then, when they've spent time lovingly crafting their message and hit the submit button, then we smack them with the registration form.

Now, the hapless visitor has a conundrum. Are they prepared to have wasted the time they spent composing their message and abandon their contribution, or will they spend a few moments completing the annoying registration form? We're betting that a good proportion will choose the latter.

1591365808123.png


Once the guest has completed registration, the content they composed will be submitted automatically, and they'll be sent an alert with a link to it.

1591365714263.png

The landscape has changed

Occasionally, there may be instances where the environment in which the content was created changes during the registration process, such as the thread being locked by a moderator or moved to a forum to which regular users do not have access. In these cases, where the created content can no longer be submitted, the newly registered user will receive an alert similar to the one below.

1591365769396.png

Setup

The experience afforded to guests is configurable. Behind the scenes, administrators can configure how this works by setting which permissions should be inherited by guests. For example, if users in the "Registered" user group are able to post in a particular forum, it'll be possible for guests to also post in that forum but they will need to register before their post is submitted.

Normally, you will want to inherit permissions from whichever group or groups users automatically become members upon registration, but the scope is there to allow whatever weird and wonderful combinations may be required by your particular setup.

1591365213189.png


Of course, sometimes visitors will not complete the registration process, especially if they are not particularly committed to a short response they composed. In order to prevent that stuff clogging up your database, content that was submitted but did not lead to a completed registration will be pruned after a short period of time.

Developer goodies

Initially, we're supporting the creation of threads and replies but as you'd expect from a XenForo core system, "writing before registering" is entirely open and extensible and can apply to any registration-privileged action, so third-party developers will be able to incorporate this functionality within their add-ons, wherever it makes sense to do so.

Post scriptum

A few questions have been raised already as to what happens if email verification or manual registration approval is enabled on your forum.

In these instances, the content that has been posted is kept in a pending state, awaiting whatever steps are required for registration to complete. The content is automatically posted as soon as registration is completed, whether that is by means of email verification, manual approval or whatever other things may be set up in the registration process.

If registration is not completed within a reasonable period, the content is purged.
 
Last edited by a moderator:
tl;dr

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Hang on , hang on.

I didnt have this voice in my head for @Kier

I read everything @Mike in a Glaswegian twang. I didnt have a clue what @Chris D sounded like but I had a Kidderminster accent assign to him. Kier just didnt sound like this.

Sorry chaps. Great feature addition. As you were.
 
Participation. It's the life blood of a forum, and once you have a group of dedicated members creating and discussing content, your forum will flourish.

But there's a barrier to entry when it comes to participation. When a new visitor stumbles upon your forum from a search engine, they may read the content that piqued their interest and then feel inclined to add their own thought-provoking response, but at that point they are confronted with the dreaded

View attachment 227011

... at which point, in many cases, the whim disappears and they disappear like a stranger in the night.

The prospect of having to complete a form and go through the rigmarole of signing-up to a new service is quite a turn-off to new visitors, for obvious reasons. Visitors have a reticence to registration because they often consider it not to be worth their time.

So, what if they had something to lose by not completing the registration process?

This is the thought behind Writing Before Registering. When enabled, guest users will be granted access to the New Thread button and the Quick Reply editor and various other tools that are available to registered members. The experience is almost identical to that of a logged-in user, allowing the guest to create rich content before having registered, such that they can compose the message they want without obstructions.

What a lovely post. Now register or lose it.

And then, when they've spent time lovingly crafting their message and hit the submit button, then we smack them with the registration form.

Now, the hapless visitor has a conundrum. Are they prepared to have wasted the time they spent composing their message and abandon their contribution, or will they spend a few moments completing the annoying registration form? We're betting that a good proportion will choose the latter.

View attachment 227015

Once the guest has completed registration, the content they composed will be submitted automatically, and they'll be sent an alert with a link to it.

View attachment 227013

The landscape has changed

Occasionally, there may be instances where the environment in which the content was created changes during the registration process, such as the thread being locked by a moderator or moved to a forum to which regular users do not have access. In these cases, where the created content can no longer be submitted, the newly registered user will receive an alert similar to the one below.

View attachment 227014

Setup

The experience afforded to guests is configurable. Behind the scenes, administrators can configure how this works by setting which permissions should be inherited by guests. For example, if users in the "Registered" user group are able to post in a particular forum, it'll be possible for guests to also post in that forum but they will need to register before their post is submitted.

Normally, you will want to inherit permissions from whichever group or groups users automatically become members upon registration, but the scope is there to allow whatever weird and wonderful combinations may be required by your particular setup.

View attachment 227012

Of course, sometimes visitors will not complete the registration process, especially if they are not particularly committed to a short response they composed. In order to prevent that stuff clogging up your database, content that was submitted but did not lead to a completed registration will be pruned after a short period of time.

Developer goodies

Initially, we're supporting the creation of threads and replies but as you'd expect from a XenForo core system, "writing before registering" is entirely open and extensible and can apply to any registration-privileged action, so third-party developers will be able to incorporate this functionality within their add-ons, wherever it makes sense to do so.

Post scriptum

A few questions have been raised already as to what happens if email verification or manual registration approval is enabled on your forum.

In these instances, the content that has been posted in kept in a pending state, awaiting whatever steps are required for registration to complete. The content is automatically posted as soon as registration is completed, whether that is by means of email verification, manual approval or whatever other things may be set up in the registration process.

If registration is not completed within a reasonable period, the content is purged.
tl;dr

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
More developer goodies

But wait, there's more!

Thanks to everyone who replied to Wednesday's thread welcoming Jeremy to the XenForo team, but now please do the same for our other new member, your friend and ours, @NixFifty!

NixFifty has also been debugging and helping us out with 2.2. One of his 2.2 tasks was the implementation of Writing Before Registering, so this seems a good time to break the silence and express our appreciation to him. Welcome to XenForo :)
******* excellent idea. I write stuff then get "You must register to login and comment" and I walk away.
Well done all!

Grats to @Jeremy P @NixFifty too.
Great update.
 
So when a guest makes a post, then fails the registration process due to being caught by spam measures, what happens to their post?
Before the registration is complete it is stored as a "pre-registration action", rather than a post. Therefore:

Of course, sometimes visitors will not complete the registration process, especially if they are not particularly committed to a short response they composed. In order to prevent that stuff clogging up your database, content that was submitted but did not lead to a completed registration will be pruned after a short period of time.
 
There is no option to control it at the moment but it is set to 7 days.
So you give us an option to control a possible new user to post, then register but you don't give admins an option to control the time line before it's removed if they don't verify email address or get validated? Doesn't make sense to me especially if the new member registration requires admin approval.
 
@Chris D
If someone post at 10:12 and then register at 10:25, and in between (10:17) that registered user post something, will than after registration, post from (un)registered user be postad before or after second post. Will post have 12:12 as time of writing/posting or 10:25

There is no option to control it at the moment but it is set to 7 days
I think that you should add an option in ACP to choose (like we have for drafts)

Also, so post from unregistered people will not have alert for Staff to moderate first or just notification "this post is from ex unregisterd user"?

What is solution for forums where you can not write post before you introduce self in specific thread (you can not see other part of forum before that), or just you can see all forum, but you do not introduce self in first 1-2 posts and you recive warning
 
Hmm, so a guest can have up to seven days to complete registration after making a post, or is that just when the post gets deleted?
Both although there's a session storage component to this so if the user's session expires they wouldn't be able to complete registration anyway. They'd have to try and submit the content again.

So you give us an option to control a possible new user to post, then register but you don't give admins an option to control the time line before it's removed if they don't verify email address or get validated? Doesn't make sense to me especially if the new member registration requires admin approval.
It doesn't seem something that's particularly useful as an option. If it was an option would you set it to, and why?

@Chris D
If someone post at 10:12 and then register at 10:25, and in between (10:17) that registered user post something, will than after registration, post from (un)registered user be postad before or after second post. Will post have 12:12 as time of writing/posting or 10:25
The post date will be the date they complete registration which is when the post is actually posted.
 
there's a session storage component to this so if the user's session expires they wouldn't be able to complete registration anyway.

What controls that? Could their session be active six days later without as my further action in six days?
 
Last edited:
Maybe as a side note, when they post using this a popup states "Your post will be help for registration for <time that can be set by site admin>", with a little countdown timer. If they revisit the site it states somewhere "you still have x left to register and keep your post".

Why do I have a feeling Xenforo are giving us all the small stuff first, before they blow our minds with some truly impressive party pieces!?!.
 
Why do I have a feeling Xenforo are giving us all the small stuff first, before they blow our minds with some truly impressive party pieces!?!.

That is always the hope! 😁

There will be some still waiting for the "truly impressive" parts even when they're finished making these announcements. 🤦‍♂️
 
It doesn't seem something that's particularly useful as an option. If it was an option would you set it to, and why?
All admin options are useful, otherwise why have them at all?? I would set mine to 14 or 21 days because I am not always available to track new registrations. So depending on when I would have the time, I would set it to what I need. Other wise a very good option become useless to me.
 
All admin options are useful, otherwise why have them at all?? I would set mine to 14 or 21 days because I am not always available to track new registrations. So depending on when I would have the time, I would set it to what I need. Other wise a very good option become useless to me.
So you occasionally leave users who have taken the time to register on your forum and who may want to contribute up to 3 weeks before you have the time to approve them?

That's really not an approach that we'd recommend. If any of them become an active member of your community after that, then I'd be very surprised.

This feature doesn't really change anything for you. Any content they want to contribute won't be posted until you approve their account anyway. And by three weeks, they'll have probably forgotten you exist.
 
Back
Top Bottom