Problem/Motivation

The Field list and Used in views pages list all fields with a link to the entity or views that uses them. The Views plugins page links to all the views that use them.

Both are useful resources for users working with fieldable entities or views. With the exception of user accounts, these are all located under Structure in the admin menu, but the list pages are are located under Reports.
Other report pages are more about the kind of changing information that is required on a production site (status, log, errors etc.), while these list pages are a tool during site-building.

Users might not expect these site-building resource under reports, and therefore miss out.

Proposed resolution

Move those pages in the admin menu form Reports to Structure.

Remaining tasks

User interface changes

Before

And scrolling way down...

After

API changes

Data model changes

CommentFileSizeAuthor
#40 interdiff_38-40.txt3.06 KBsourabhjain
#40 2895832-40.patch11.93 KBsourabhjain
#38 interdiff_37-38.txt8.07 KBAkram Khan
#38 2895832-38.patch11.88 KBAkram Khan
#37 2895832-37.png818.07 KBNikhil_110
#37 2895832-37.patch11.48 KBNikhil_110
#24 structure_link_list.png74.49 KBsavkaviktor16@gmail.com
#24 interdiff_2895832-14-24.txt619 bytessavkaviktor16@gmail.com
#24 2895832-field-list-menu-item-24.patch9.3 KBsavkaviktor16@gmail.com
#23 structure_after_applying_patch.png16.55 KBmohit1604
#23 reports_after_applying_patch.png15.07 KBmohit1604
#23 structure_before_applying_patch.png15.57 KBmohit1604
#23 reports_before_applying_patch.png17.75 KBmohit1604
#14 interdiff-2895832-5-14.txt8.75 KBifrik
#14 2895832-field-list-menu-item-14.patch9.29 KBifrik
#11 2895832-field-list-menu-item-11.patch3.13 MBifrik
#8 views-plugins-tab-after.png4.43 KBifrik
#8 field-list-views-after.png4.47 KBifrik
#8 field-list-tabs-after.png3.82 KBifrik
#8 menu-after.png13.96 KBifrik
#8 interdiff-2895832-5-8.txt5.95 KBifrik
#8 2895832-field-list-menu-item-8.patch3.13 MBifrik
#6 structure_after.png67.12 KBxjm
#6 reports_before.png73.21 KBxjm
#6 structure_before.png65.02 KBxjm
#5 2895832-field-list-menu-item-5.patch1.06 KBifrik
xjm-tweet.png14.77 KBifrik
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ifrik created an issue. See original summary.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Title: Move "Field list" pages from Reports to Structure » Move "Field list" and "Views plugin" pages from Reports to Structure
xjm’s picture

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

Yes, let's move them!

The only downside is that it's even more menu items (well 1) in the already overloaded Structure section. But I think it' a worthwhile tradeoff because it's actually the answer to accidentally clicking on comment types when you want content types.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Related issues: +#2755613: Restructure the admin interface Information Architecture

I'm working on it.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Status: Active » Needs review
FileSize
2895832-field-list-menu-item-5.patch1.06 KB

I've moved both the Fields list as well as the Views plugins.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue summary: View changes
FileSize
structure_before.png65.02 KB
reports_before.png73.21 KB
structure_after.png67.12 KB

The paths are still /admin/reports/fields and /admin/reports/views-plugins. Maybe/probably they should change to reflect the new parents in the IA?

I think the "Views plugins" link should probably go under "Views" (or maybe be a tab on "Views") rather than being a first-level item under "Structure". Not sure if we want that one in the same scope here or not since I think it's of a different level of relevance (related only to Views) vs. the field list (related to every fieldable entity type).

Added some before screenshots to the summary. Here's the current "after":

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue summary: View changes

Editing to make the screenshots not giant; forgot to fix the high-res thing.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
FileSize
2895832-field-list-menu-item-8.patch3.13 MB
interdiff-2895832-5-8.txt5.95 KB
menu-after.png13.96 KB
field-list-tabs-after.png3.82 KB
field-list-views-after.png4.47 KB
views-plugins-tab-after.png4.43 KB

Sorry for forgetting about the paths. I already thought that this was much less work then expected...

I've now corrected the pathes, and while I was on it also made the page and tab titles a bit more consistent which each other, because a page title like "Used in views" is not very clear in itself. I've also changed the help text that refers to it. See screenshots.

I also realized that the existence of these views pages and the views settings pages are missing from the help so I make an issue for that as well.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Issue tags: +String change in 8.4.0

Status: Needs review » Needs work

The last submitted patch, 8: 2895832-field-list-menu-item-8.patch, failed testing. View results

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Status: Needs work » Needs review
FileSize
2895832-field-list-menu-item-11.patch3.13 MB

I've also fixed the Views_UI test. The Field UI does not seem to have a test that checks for the pages.

Status: Needs review » Needs work

The last submitted patch, 11: 2895832-field-list-menu-item-11.patch, failed testing. View results

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented

I'm not quite sure what happened there, but the last patch had so much in there that shouldn't be there.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Status: Needs work » Needs review
FileSize
2895832-field-list-menu-item-14.patch9.29 KB
interdiff-2895832-5-14.txt8.75 KB

Okay, this now should have all tests.

The screenshots in #8 are still correct.

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.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Status: Needs review » Needs work
Issue tags: -String change in 8.4.0 +String change in 8.5.0, +Needs screenshots, +Novice, +Vienna2017
bendev’s picture

bendev CreditAttribution: bendev commented

I work on this issue in Vienna2017

bendev’s picture

bendev CreditAttribution: bendev commented
Status: Needs work » Reviewed & tested by the community

Okay I have tested the patch against 8.5.x and it is working fine

Screenshots in #8 are still valid (checked)
Paths and titles look ok.

yoroy’s picture

yoroy CreditAttribution: yoroy at Roy Scholten commented
Status: Reviewed & tested by the community » Needs work
Related issues: +#2721727: Allow user to add display modes from respective field UI's., +#2518960: Emphasize the most important items on the 'structure' page, +#1440678: New users have difficulty finding where to adjust the content model

I agree that it would be useful to bring these listings closer to the interfaces where they are most useful. I don't think adding them to the Structure page is necessarily the best way to connect these dots. The structure page is already too much of an undifferentiated mix of primary, heavy use items (content types, views, menus) and less often used items like comment types, contact forms. (And what are Views plugins anyway?)

I don't think these items should be presented on the level where you can still choose between working on (for example) your content types, navigation or views. These lists would ideally be linked only on screens where they are relevant. Similar to what #2721727: Allow user to add display modes from respective field UI's. wants to do.

Can we look into other ways to connect these related screens? I'm thinking about #1440678: New users have difficulty finding where to adjust the content model for example. Another route would be to get busy with #2518960: Emphasize the most important items on the 'structure' page.

In it's current state of alpha sorting whatever links are on this page, adding more items to this list, where those items only *support* *parts* of the functionality on offer there is not the better trade-off.

Ivan Berezhnov’s picture

Ivan Berezhnov CreditAttribution: Ivan Berezhnov as a volunteer and at Drupal Ukraine Community for Levi9 commented
Issue tags: +CSKyiv18

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.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue tags: -String change in 8.5.0

Please only tag string changes after the issue is actually committed. Thanks!

mohit1604’s picture

mohit1604 CreditAttribution: mohit1604 at Google Summer of Code commented
FileSize
reports_before_applying_patch.png17.75 KB
structure_before_applying_patch.png15.57 KB
reports_after_applying_patch.png15.07 KB
structure_after_applying_patch.png16.55 KB

I applied patch #14 manually for version 8.4.x and observed that Views plugins is not showing in structure after applying the patch !

Before applying patch

reports
structure

After applying patch

reports
structure

savkaviktor16@gmail.com’s picture

savkaviktor16@gmail.com CreditAttribution: savkaviktor16@gmail.com at Skilld commented
Status: Needs work » Needs review
FileSize
2895832-field-list-menu-item-24.patch9.3 KB
interdiff_2895832-14-24.txt619 bytes
structure_link_list.png74.49 KB

Adjusted the patch, 'Views plugins' link has come back

kpolte’s picture

kpolte CreditAttribution: kpolte commented
Issue tags: -Needs screenshots

Seems like a screenshot is already uploaded.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Status: Needs review » Reviewed & tested by the community

The patch works as intended.
Thanks a lot!

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan at PreviousNext commented
Status: Reviewed & tested by the community » Needs work

#19 was not addressed

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.

Nikhil_110’s picture

Nikhil_110 CreditAttribution: Nikhil_110 at Srijan | A Material+ Company commented
FileSize
2895832-37.patch11.48 KB
2895832-37.png818.07 KB

Attached patch against drupal 10.1.x

Akram Khan’s picture

Akram Khan
Primary language English
Location Cuttack, Odisha
CreditAttribution: Akram Khan as a volunteer and at Srijan | A Material+ Company for Drupal India Association commented
FileSize
2895832-38.patch11.88 KB
interdiff_37-38.txt8.07 KB

try to fix CCF #37

sourabhjain’s picture

sourabhjain
Primary language English
CreditAttribution: sourabhjain at Valuebound for Valuebound commented
Assigned: Unassigned » sourabhjain

I am working on fixing #38.

sourabhjain’s picture

sourabhjain
Primary language English
CreditAttribution: sourabhjain at Valuebound for Valuebound commented
Assigned: sourabhjain » Unassigned
Status: Needs work » Needs review
FileSize
2895832-40.patch11.93 KB
interdiff_38-40.txt3.06 KB

Tried to fix the #38 error. Please review.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan at PreviousNext commented
Status: Needs review » Postponed

Folks, please don't work on this until we get buy in from the UX/product team

In #19 they expressed that they didn't support it.

I would recommend taking it to the usability team via the #ux channel

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan at PreviousNext commented

FWIW I don't agree with this change either

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.