ISSUE SUMMARY: Registration form is bugged. If the inpatient user clicks multiple times on the 'Next' and 'Submit' buttons, it turns this error:

'500 - Registration failed. Missing user object.' error

I also tried it on the Jomsocial's demo site, and the same thing happens. I guess the registration form has no protection against multiple clicks for the inpatient user, so that the form is sending multiple empty requests, or at least it confuses it. As I recall in the previous Jomsocial versions, the 'Next' button was disappearing showing the ajax-loader.gif after being clicked (perhaps to prevent that). Another thing you should know, is that I had to renew my Jomsocial subscription just to be able to report this bug. Please fix this ASAP. I'm sure nobody wants this on their websites.

Thanks for your help and understanding.

STEPS TO REPLICATE:
1 Click Next and Submit multiple times on the registration form
2
3
4
5
RESULT See attached image
EXPECTED RESULT A bright beautiful avatar select and upload page
BROWSER Any

HI.

I'm sorry but this is NOT a bug (you're first user that reported this).
This is user caused malfunction. Why anyone click "next" multiple times if see page loading indicator?

I understand. Will try this on other social platforms, and see how they manage the multiple clicks behavior. Damn, this inpatient users. I will post a note above the registration form:

'Please do not click buttons more than once. Our platform cannot handle your slow connection speed or impatience.'
If it happens for us to have a slow server, we might add 'Please use carefully, our servers might not handle all of your requests.'

Hi.

Ok. You see many users - even if they are familiar a bit with web sites - have no clue how to use browser.
They don't see wait indicator on tab...

The same goes for e.g Windows users... unpatient user clicks multiple times on icon... and system tries to handle all the request and become slower and slower.

Hello again.

You see, I actually opened this topic/ticket for finding a solution to this. Being the first to report this, doesn't makes you less responsible for escalating this issue. Perhaps the other Jomsocial customers haven't went through deep testing as I did, or haven't really thought about that. I am well aware of the inexperienced users behavior, but this is not my point. The point is that we, as community owners, it's not in our interest to lose users due to their lack of experience, and no one wants that for his business. Therefore, we live in 2015 where code evolved significantly and it became friendly for ANY type of user. Considering finding a fix for this would be a more professional approach rather than explaining me how some users don't know how to use a browser. That doesn't fixes my problem. It's in Jomsocial's interest to offer a seamless code to it's customers, having in mind the less-experienced user when writing it, offering some kind of protection when these events occur, and do something about it. Most of my targetted users are women over 40 years old.

With all this being said, what do you suggest? Leaving the issue as is, or do you have a solution for your software? And to be honest, I'm kinda intrigued by your feedback. With all the respect towards you, would you mind having this topic handled by some other member of your support team?

Thank you

Hi.

I talked with Project Manager regarding issue that you reported... and yes, you have a point here.
Software should be user proof...
So I'll report this issue to our developers and we implement this feature in future release but for now I can't specify when it will be ready.

Finally someone got the point. I was just about to give up. That's the spirit. It doesn't matter if it takes time, what matter the most is that it's going to be fixed.

Thanks Michal!

Hi.

Please, could you help us to test this new feature?
Do a safe copy of this file:

ROOT/components/com_community/templates/jomsocial/layouts/register/base.php

Then replace original file with patched one from package.

Hi there,

Oh well, meanwhile I've seen version 4.1.2. has been released, and i upgraded. I noticed that ajax-loader.gif was added, to show the user his request is being processed. Then i modified the code myself and i came up with a better solution which solves the issue entirely and it looks pretty good. I attached my solution to this message and please confirm if this can also be used. :)

I made the 'next' button disappear when pressed and to show only the ajax loader. When the form is incomplete or fields are invalid, I made the button show. If you think this is not a proper solution, I will apply yours. Thanks a lot for your time.

Yes, I have tested it and it works. I combined your solution with mine, making the submit button disappear and show the loading message. Hope this will be implemented in 4.1.3.