Problem/Motivation
The usual wording of the button to add something is "Add content type", "Add contact form" etc. but on the two Display mode pages these links are "Add new view mode" and "Add new form mode".
"New" is otherwise only used in connection with installing something new (module, theme).
Proposed resolution
1) Change the wording to "Add view mode" on the View modes page, and to "Add form mode" on the Form modes page.
2) On the View modes page, remove 'new' from each of the following:
"Add new Content view mode", "Add new Custom block view mode", "Add new Comment view mode", "Add new Taxonomy term view mode", "Add new User view mode".
Remaining tasks
Edit the wording in the field_ui.routing.yml and/or field_ui.links.action.yml, and update the hook_help text in field_ui.module if necessary
User interface changes
This is a UI text change and therefore the help text might need to be edited as well.
API changes
none
Data model changes
none
Comment | File | Size | Author |
---|---|---|---|
#11 | 2752709-10.patch | 1.9 KB | pashupathi nath gajawada |
#6 | removed-new-from-view-and-form-modes-2752709-5.patch | 3.82 KB | ChandeepKhosa |
#6 | before-view-modes-1.jpg | 329.09 KB | ChandeepKhosa |
#6 | before-view-modes-2.jpg | 204.46 KB | ChandeepKhosa |
#6 | after-view-modes-1.jpg | 321.5 KB | ChandeepKhosa |
Comments
Comment #2
ChandeepKhosa CreditAttribution: ChandeepKhosa at 2Toucans commented..
Comment #3
kamalrajsahu21 CreditAttribution: kamalrajsahu21 at Intelliswift commentedText changed in this patch and no need to change anything in help text.
Comment #4
ChandeepKhosa CreditAttribution: ChandeepKhosa at 2Toucans commentedI noticed that the 'new' text needed to be removed from additional places, but on the same page & context, so I expanded the scope of this issue.
Comment #5
HazaI guess we should also change this in the tests.
See in testEntityViewModeUI()
Same here, see in testEntityFormModeUI().
Comment #6
ChandeepKhosa CreditAttribution: ChandeepKhosa at 2Toucans commentedThis patch includes all relevant changes needed above.
Unlike the patch uploaded by Kamal, my patch also includes connected changes to tests & additional view modes lower on the page.
Thank you to Marc Van Gend (marcvangend), Daniel Smith (dmsmidt) & Gabor Hojtsy (gábor-hojtsy) for mentoring assistance here at Drupal Dev Days.
Screenshots showing changes made
View modes
Form modes
Comment #7
ChandeepKhosa CreditAttribution: ChandeepKhosa at 2Toucans commented..
Comment #8
Gábor HojtsyLooks good assuming tests pass :)
Comment #10
Gábor HojtsyLooks like still fails on Line 47 of core/modules/field/src/Tests/Update/FieldUpdateTest.php:.
Comment #11
pashupathi nath gajawada CreditAttribution: pashupathi nath gajawada as a volunteer and at Melity commentedHi ,
Please find the attached patch which would fix this.
Thanks,
Comment #12
mcgovernm CreditAttribution: mcgovernm as a volunteer commentedLast patch looks good! Tested patch with simplytest.me.
Comment #13
ChandeepKhosa CreditAttribution: ChandeepKhosa at 2Toucans commentedThanks guys for all of your help. I am removing the assignee from pashupathi
Comment #14
ifrikThanks, this patch works as intended.
However, two comments about good practices in the issue queue:
Kamalrajsahu21: another user had already assigned himself to the issue and was working on it. Just jumping in and posting a patch without checking whether the other person had stopped working on it, means that the work was done double, potentially wasting time that rather could have been spend on two different issues.
And about naming patches: It's good practice to keep the name of the first patch and not just randomly rename them. A different name usually indicates a new patch done from scratch and not a continued work, so it's difficult for reviewers to see what's going on. For the same reason it's also good practice to provide interdiffs so that reviewers can see what has changed from one version of a patch to another instead of reviewing it all over again.
Comment #20
xjmI confirmed that this fixes all instances of these two overlong strings:
Similarly to #2749261: "Add view" instead of "Add new view", this removes redundancy from the UI text, which is a good usability best practice.
Committed d2cd3e6 and pushed to 8.2.x. Thanks! I've also added issue credit for the mentors mentioned in the issue.
Comment #21
xjm(Fixing the credit.)
Comment #23
Gábor HojtsyThanks, removing from UX sprint now.