There are many threads related to this issue. We scrutinized it from different angles, tested it on various OSes, different browsers versions and browser settings, however we were not able to reproduce it.
Here's some information for you in relation to the problem with join process via Chrome. Of course, it can vary from case to case and may not apply to everyone, however this is considered as a common plausible explanation why this occurs on YOUR websites:
The server got disconnected while user registration;
Different browser cookies settings - session has been removed;
Pre-set fields like age range or some custom fields, in this case server declines data because it is incorrect or invalid.
If the above is not satisfied, then a user cannot get to the first step of the registration until he clears the browser cookies.
You need to be able to reproduce that on your websites and provide us with the details:
Every step of the registration process;
How much time it takes for your to register on your website;
What profile questions you have?;
List of plugins;
Software version;
Your OS;
Your browser version and settings;
Are you logged in Chromium;
Any other valid details which you consider may be important for reproducing;
Then you need to try to reproduce this on the oxwall.org demo website, so we could do the same. Until then, we are not able to start fixing the issue.
In the meantime if you want to disable this strict check of the data by server, in ow_system_plugins/base/init.php
insert this code at the bottom: function base_addFakeQuestions( OW_Event $e ) { $e->setData(false); } OW::getEventManager()->bind('base.questions_field_add_fake_questions', 'base_addFakeQuestions');
Add a Chrome profile:
In Chrome browser, at the top right, click Profile. .
Click Manage people.
Click Add person.
Choose a name and a photo.
Click Save. A new window will open and ask you to turn on sync.
(Optional) Turn sync on in Chrome with a Google Account for the new profile.
Greetings,
Peter