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 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.
 
Last edited by a moderator:

Lawrence

Well-known member
Seems to me the time you spent here putting down my situation your time would have been better spent adding the option for admins to control the amount of time they may or may not need before a potential user is removed for ever. Anyway thanks for the insight into your priorities and negative attitude towards me and my request

I don't think you realise how much time the XF team spends discussing as to how to implement a feature, or what options should be included and what they should be set to. One person does not make the decisions, all staff members do, collectively. It has always been that way. And when they reach a decision it does not mean it is set in stone, as a use case may present itself that wasn't considered. You probably have them talking now, that is just how they work.

@Chris D isn't being negative, he, in my opinion, is just pointing out that your your situation is an edge case. That happens. Should a feature be changed for a single use case, or a handful? Probably not, but I bet you got them thinking on it, :)
 

mjda

Well-known member
@NixFifty please consider porting this as a XF2.1 paid add-on for those of us that won't make the XF2.2 jump right away due to custom add-ons made for our community.

Aren't minor point releases usually safe upgrades? I mean, I know there will be exceptions, but for the most part I thought the 2.1 to 2.2 upgrade should be safe with most add-ons. At least I hope that's the case. I have a bunch of custom add-ons, too, but I don't think I had to update any of them from 2.0 to 2.1. Maybe I'm mis-remembering?
 

Chris D

XenForo developer
Staff member
We can/do make breaking changes in second point releases occasionally, though we keep them fairly minor and to a minimum.

Regardless, for a new update, we'd always recommend you follow a rigorous backup and testing regime before proceeding with the upgrade and by doing that it gives you the time to work out any issues if there are any.
 

Cooking Ketogenic

Active member
Aren't minor point releases usually safe upgrades? I mean, I know there will be exceptions, but for the most part I thought the 2.1 to 2.2 upgrade should be safe with most add-ons. At least I hope that's the case. I have a bunch of custom add-ons, too, but I don't think I had to update any of them from 2.0 to 2.1. Maybe I'm mis-remembering?

From my understanding on it, they are changing the framework in 2.2 which eliminates any call to <xen> to the new framework instead. I can't find the post on this now, but I could had sworn it was in a HYS from @Chris D
 

Brogan

XenForo moderator
Staff member
You're probably thinking of this.

 

Chris D

XenForo developer
Staff member
And that’s not what that thread is about. We use some components from a third party library called Zend Framework that framework now has a new name.

It has nothing to do with XenForo or <xen> tags (we haven’t used those since XF1 anyway) and will very likely not affect the sheer majority of existing code.
 

Cooking Ketogenic

Active member
You're probably thinking of this.



Yes! Thank you @Brogan as I was pulling my hair out looking for it trying to convince myself it wasn't a dream 😴 Zend, not xen explains why it didn't come back with the thread in search 🙊
 

Karelke

Well-known member
Aren't minor point releases usually safe upgrades? I mean, I know there will be exceptions, but for the most part I thought the 2.1 to 2.2 upgrade should be safe with most add-ons. At least I hope that's the case. I have a bunch of custom add-ons, too, but I don't think I had to update any of them from 2.0 to 2.1. Maybe I'm mis-remembering?

I don't think XenForo follows semver, so technically the team can change whatever they find necessary.
 

Faust

Active member
Sorry for an off topic question , but with release would Media Gallery and Resources will be updated , as I think they need to be updated, especially media Gallery.
 
Top