Project

General

Profile

Actions

Feature #8637

closed

Remove extra fields from signup process

Added by Boone Gorges over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Daniel Jones
Category name:
Registration
Target version:
Start date:
2017-08-31
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

See https://chris0stein.github.io/commons-ux/registration/index.html

Let's remove the fields not shown in this image from the signup process.

Dan, can you have a look? You may consider using the noshow_fields trick in wp-content/themes/bp-nelo/registration/register.php, or you rebuild the process to use a whitelist instead (seems like it might be more sensible).

Actions #1

Updated by Daniel Jones over 6 years ago

This was pretty straightforward (I did the 2nd option). I do have one question though: should I delete the code that currently outputs the "Blog Details" section of the registration page, which allows users to create a new blog when they register? There was also some code related to the "College" field that had it also show the Positions field that I've just commented out for now, but will delete if you say it's alright.

Once I know what to do on those two questions, I'll go ahead and make the final changes and push the commit.

Actions #2

Updated by Boone Gorges over 6 years ago

If it's not shown in the mockup, feel free to rip it out of the template. (As you can tell, that template has been accruing junk for years.) Thanks!

Actions #3

Updated by Daniel Jones over 6 years ago

Great! Pushed some changes here: https://github.com/cuny-academic-commons/cac/commit/b3c97f7c70a1b2ee455e94336e5f37c925853b73

Right now it still splits the fields into "Account Details" and "Profile Details", with the Full Name field on the right under "Profile Details", which is different from the mock-up. Should I work on that or is that for a different ticket, and can leave this for now?

Actions #4

Updated by Boone Gorges over 6 years ago

  • Status changed from New to Resolved

Ah, I hadn't noticed that change. I assume Chris made it that way because it sorta makes more sense to think of it as "account" info rather than "profile" info. However, I understand that it's techincally profile data, and that it's not a straightforward task to switch columns.

I'm going to make the call to leave it as-is - we'll deviate from the mock-up in this respect. I've copied Chris here in case he feels strongly about the move.

Actions

Also available in: Atom PDF