The great possibility of having fields in core, and even more great possibility with fields on user profile may raise the problem, when the user account edit page simply has too much content. On the other hand, there are vertical tabs here and there and it could be possible to redesign user account edit form to compress all system forms, as in the included screenshot and patch. This patch has no API changes, it only moves user form fieldsets to vertical tabs. It keeps registration form untouched. To avoid scrolling, it splits username and password form into username/password and roles/status.

This issue raised when thinking about #967566: Several important Core User settings need to implement hook_field_extra_fields(), and in fact, I also included in the patch change so that username/password/roles/status can be reordered on Manage Fields tab. After all, the user account edit page looks in my opinion much more prettier

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mariusz.slonina’s picture

FileSize
5.98 KB
112.32 KB

patch and screenshots

mariusz.slonina’s picture

Status: Active » Needs review
Dave Reid’s picture

Status: Needs review » Closed (won't fix)

This was pretty much discussed to death previously. Our UX standards say it should be a logical grouping (like we currently use for all the e-mail fields), and that vertical tabs should not be the entire UI, which is what you're now doing.

Previous issues:
#434942: Vertical-tab-ify admin/user/settings
#645738: UX: Vertical-tabify the rest of the admin/config/people/accounts page
http://drupal.org/ui-standards

Dave Reid’s picture

Status: Closed (won't fix) » Needs work

Grrr, completely missed you're talking about the user edit page, not user settings page.

1. Still need to follow the UI guidelines of not having all elements in the vertical tabs.
2. Vertical tabs need JavaScript summaries to be useful.

mariusz.slonina’s picture

FileSize
7.18 KB

I don't know much about js, so I followed node.js. This patch adds initial js status support, for roles/status and administrative overlay. It also moves username/password settings outside vertical tabs, since it is rather critical information and should be always available. I don't know if verticaltabs-js for all core modules which are interacting with user module should be included in user.js or rather in module.js.

Dave Reid’s picture

Version: 7.x-dev » 8.x-dev

It's also waaaaaay to late to change UI since we are now post RC1. This has to get bumped to D8.

mariusz.slonina’s picture

ok, in that case, is there a way to override this user edit page with contrib module? I tried using hook_form_FORM_ID_alter, which works with user_register form, but I couldn't get it working on user_account_form / user_profile_form...

mariusz.slonina’s picture

Issue tags: +#d8ux, +D8UX usability

I got some problem with caching. I am able to do such change in contrib module, but anyway, redesign of user edit page should be considered

mariusz.slonina’s picture

With patch from http://drupal.org/node/967566#comment-3818726 I can redesign the user account edit page with help of Fieldgroup module.

Tlommy’s picture

Version: 8.x-dev » 7.0

Im just wondering if anyone ever solved this issue, Im on D7. The vertical tabs works fine when using it with content types, But when I attempt to use them on the user account edit page I run into problems. If I just have one field group set up as a vertical tab it works...but when I add multiple my fields groups and fields disappear. Does anyone know whats goin on with this?

Tlommy’s picture

Status: Needs work » Needs review

#1: 993592_1.patch queued for re-testing.

mariusz.slonina’s picture

Version: 7.0 » 8.x-dev

Well, I think it should be 8.x issue -- right now there are two possibilities: 1) move Fieldgroup into core, and make user account edit page customizable, or 2) fix user account edit page with vertical tabs. Both of them are huge UI change, and for sure will not be the case of D7. You can try Fieldgroup module, with my patch http://drupal.org/node/967566#comment-3818726. To do so, You have to create a vertical tabs group and then vertical tabs for your fields. If there are fieldsets inside (i.e. user name and password fields) you have put them into additional fieldset. So, it is possible to fully customize user account edit page. I agree, however, it should be solved -- with so many core improvements, shame we forgot about such thing like user account edit page. Even if User will get there once or twice, it should rock, too. What we really need right now, is #967566: Several important Core User settings need to implement hook_field_extra_fields() solved, because without it, the D7 looks unfinished.

sun’s picture

Component: user system » user.module
Issue tags: -#d7ux, -D7UX usability, -#d8ux, -D8UX usability +Needs usability review

Replacing with proper tag, so hopefully the usability team notices this issue.

droplet’s picture

Status: Needs review » Needs work

1. Patches need works, some unnecessary space there.
2. "Username and password" not inside the group (-dev version)
3. some inputs broken under Bartik, and I think a lot of theme will have same issue because vertical tabs make the main content more narrow. (most of sides have a sidebar)

using horizontal tabs more better IMO.
#1168364: Add horizontal tabs supports to FAPI

Rob C’s picture

Subscribe! This is awesome.

RobLoach’s picture

Category: bug » task

Would be great to prettify this a bit.

Bojhan’s picture

Category: task » feature
Priority: Major » Normal
geerlingguy’s picture

Subscribe. Been working on the profile edit form a while on my site, and having it prettier by default would go a long way towards saving me time.

juampynr’s picture

Here is an implementation that separates user account fields from the rest of the fieldsets.

Here are screenshots to what does it look like:
* Account tab
* Personal tab
* as opposed to the current Edit page with all the fields in one place.

Looking forward for reviews/opinions in that issue.

Cheers

klonos’s picture

...subscribing.

bryancasler’s picture

subscribing

karschsp’s picture

subscribe

yoroy’s picture

Yup, still worthwhile to pursue this. Looking at the screenshot in #1 I see only the real name field excluded outside of vertical tabs. I think we should first have a good look at what the primary fields for this page are and expose more of them outside (above) the vertical tabs. User picture and email for example. We don't want to hide too much, only the secondary things that are less likeley to be revisited often.

karschsp’s picture

Status: Needs work » Needs review
FileSize
6.98 KB

Here's a re-roll of what's in #5.

karschsp’s picture

Ugh. Fixing some whitespace issues.

Bojhan’s picture

I am a bit worried about this one, its not really a good pattern - nor is it what we want for our normal users to see.

klonos’s picture

@Bojhan: Can you please elaborate more on that? What would be a good pattern? What do we want normal users to see?

Status: Needs review » Needs work

The last submitted patch, 25: 993592-user-vertical-tabs.025.patch, failed testing.

alansaviolobo’s picture

Issue summary: View changes
Issue tags: +Needs reroll
Nitesh Sethia’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll +#drupalgoa2015
FileSize
154.88 KB

Rerolled patch.

Status: Needs review » Needs work

The last submitted patch, 31: vertical_tabs_on_user-993592-31.patch, failed testing.

lpalgarvio’s picture

Version: 8.0.x-dev » 8.1.x-dev

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.