If you create a view of Nodes, Comments, or Taxonomy terms, and choose the Entity option for your row display (instead of Fields), you get a rendered entity that includes the title/subject/name of the entity with a link to the entity.

However, if you try the same for a User view, you will see just the "Member for" information and any custom fields you have added. No user name, no user ID, nothing identifying the user and no link to the user page.

This is not good. It makes the entity view of User in Views completely useless.

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

It may not be showing much else either. All I'm really getting is Member For. :(

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented

While this would be useful, this is not something that was ever possible, so I don't think this is a major bug? #2227381: Apply formatters and widgets to User base fields 'name' and 'email' might make this possible, in case we add a formatter for the username there.

handling of the label in rendered entities is always a problem, the current implementation for other entities is way too static, it's still based on the dated concept of $is_page and can't be controlled from the outside.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

If a rendered entity does not include the label, it is totally useless in a view. So yes, I think it is major.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented

Yes, and if you try this in 7.x, it's exactly the same behavior, so how can it suddenly be a major bug? :) Not saying that I don't want to see this fixed, but we have a lot more important bugs than this.

As I said, the only solution that core currently has for this problem is the $is_page flag, which shows the node title only when you're not viewing that node, aka node/$nid, because there, we don't want to repeat the node title/user name, whatever.

Maybe we could make the user name formatter/view configurable but not show by default, then you could solve it by adding a custom view mode and then configure that to show the username.

swentel’s picture

swentel CreditAttribution: swentel commented

Yeah, adding a formatter in #2227381: Apply formatters and widgets to User base fields 'name' and 'email' will make this easy to fix. If we commit ourselves to add it there, we can close this one, or follow up here to add the formatter.

cilefen’s picture

cilefen CreditAttribution: cilefen commented
Status: Active » Postponed
Related issues: +#2227381: Apply formatters and widgets to User base fields 'name' and 'email'

This still exists in HEAD. I vote for making this Normal priority because it does not cause "significant repercussions" and a site builder can display the user fields instead. If it is blocked on #2227381: Apply formatters and widgets to User base fields 'name' and 'email' then it is postponed.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Issue tags: +Usability
jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

Demoting fairly major usability problems to "normal" will lead to shipping Drupal 8 with a crappy UI. The UI is all most people will see. If it is crappy, then Drupal 8 will be perceived as crappy.

Right now if you create a User view from the UI you get a completely useless view. That is not really OK.

ivanstegic’s picture

ivanstegic CreditAttribution: ivanstegic at TEN7 commented
Issue tags: +UMN 2015
xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented

@jhodgdon, but it is still possible to display this information using a field row style, right? Just not for the entity display row style.

If a view like this existed in core, I'd agree that it was a major bug. However, since this is rather about new views created by the user not providing the desired functionality, I think I'd call this a major feature request.

I agree that we should not just downgrade usability issues, and in general I think it is also important to make the entity row display work well, because they are really the best practice (vs. field views). I think fixing this would be an excellent target for a minor version, because I agree that the current result is pretty useless.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Parent issue: » #2665694: [meta] Make entity view mode row style the preferred way to build a view (with feature parity for site builders)

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

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

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Title: Default entity view for User does not show user name » Default entity view for User should show user name
Version: 8.1.x-dev » 8.2.x-dev
Category: Bug report » Task
Priority: Major » Normal

The core committers and Views subsystem maintainers agreed that this does not need to be filed as a major bug. However, this is part of #2665694: [meta] Make entity view mode row style the preferred way to build a view (with feature parity for site builders) and definitely something we should fix as part of improving the usability of Views in general and making entity views offer feature parity with fielded views. Let's work on the entity system blocker #2227381: Apply formatters and widgets to User base fields 'name' and 'email' and then improve these views when possible.

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

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.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.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.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.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now 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: 10.1.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, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.