Problem/Motivation

The current option summary for 'Link display' in the DisplayPluginBase class is unclear and can lead to confusion. This issue aims to improve clarity by updating the option summary text to 'Destination.'

I would suggest to use the word "Destination" to replace "Link display".

The settings box for this option displays a title
'Which display to use for path' and help text
'Which display to use to get this display's path for things like summary links, rss feed links, more links, etc.'
These seem hard to understand. Should we change that?
Screen Shot 2013-09-12 at 1.34.11 AM.png

Steps to reproduce

* Navigate to a Views view with a Block display
* On the Block display, observe the 'Link display' option in the pager category.

Proposed resolution

Update the title of the 'link_display' option from:
'title' => $this->t('Link display'),
to:
'title' => $this->t('Destination'),
This change provides a more descriptive and understandable label for the option.

User interface changes

Before
Screen Shot 2013-09-12 at 1.30.37 AM.png

After
Screen Shot 2013-09-12 at 1.36.26 AM.png

Now, double click on the 'Link Display' option, a pop-up settings box appears with title
'Which display to use for path' and help text
'Which display to use to get this display's path for things like summary links, rss feed links, more links, etc.'

Test plan

* Navigate to a Views configuration page.
* Verify that the 'Link display' text in the option summary is now replaced with 'Destination.'

API changes

Data model changes

Release notes snippet

Issue fork drupal-2087139

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

dawehner’s picture

Could we not just add a new group, as the link display really simply not belongs to the pager.

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.

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.

smustgrave’s picture

Version: 9.5.x-dev » 11.x-dev
Assigned: jiv_e » Unassigned
Category: Task » Feature request
Issue summary: View changes
Issue tags: +Needs issue summary update, +Needs tests, +Needs Review Queue Initiative

Slightly reviewing very old tickets as part of needs-review-queue-initiative

This still appears to be the case and agree "Link display" is slightly off.

smustgrave’s picture

Issue tags: +Novice

Probably a good task for new users.

Drupaler_Kushal made their first commit to this issue’s fork.

drupaler_kushal’s picture

Status: Active » Needs review

Completed the text change as suggested. Please review the PR https://git.drupalcode.org/project/drupal/-/merge_requests/6282.

sandeep_k’s picture

Assigned: Unassigned » sandeep_k

Hi @Drupaler_Kushal, I've Tested the shared MR- MR !6282 mergeable on the Drupal- 11.0-dev version, The Patch was applied successfully and looks good to me.

Testing Steps:

  • Install Drupal- 11.0.
  • Go to> admin/structure/view-
  • Create/edit view- Scroll down the Pager section to view the label, Attached before results
  • Download the shared patch & apply.
  • Create/edit view- Scroll down the Pager section to re-verify this.

Testing Results:
After applying the patch, the text label is changed now. RTBC++

sandeep_k’s picture

Assigned: sandeep_k » Unassigned
StatusFileSize
new109.51 KB
new82.72 KB

Attaching Test results here

smustgrave’s picture

Status: Needs review » Needs work

Was tagged for issue summary and tests.

pooja saraah’s picture

Issue Summary:
Problem/Motivation:
The current option summary for 'Link display' in the DisplayPluginBase class is unclear and can lead to confusion. This issue aims to improve clarity by updating the option summary text to 'Destination.'
Steps to Reproduce:
* Navigate to a Views configuration page.
* Observe the 'Link display' option in the pager category.
Proposed Solution:
Update the title of the 'link_display' option from:
'title' => $this->t('Link display'),
to:
'title' => $this->t('Destination'),
This change provides a more descriptive and understandable label for the option.

Test Plan:
* Before applying the patch:
* Verify that the option summary for 'Link display' is present on a Views configuration page.
* Confirm that the text is currently set to 'Link display.'
* Apply the Patch:
* Apply the provided patch to update the 'Link display' text to 'Destination.'
* Confirm that the patch applies cleanly without conflicts.
* After applying the patch:
* Navigate to a Views configuration page.
* Verify that the 'Link display' text in the option summary is now replaced with 'Destination.'

smustgrave’s picture

Issue summaries shouldn’t go in a comment. And full template should be used.

Test could be as simple as an assertion somewhere

pooja saraah’s picture

Issue summary: View changes
pooja saraah’s picture

Status: Needs work » Needs review
smustgrave’s picture

Status: Needs review » Needs work

Please read the comments and tags. This was tagged for a simple test which isn’t done.

drupaler_kushal’s picture

What is pending now in this?

sumit-k made their first commit to this issue’s fork.

sumit-k’s picture

Status: Needs work » Needs review

I've added a simple functional test to validate the changes made to the label.

lendude’s picture

Status: Needs review » Needs work
Issue tags: -Needs issue summary update, -Needs tests

Please search the Views and Views UI modules (and maybe others?) for 'Link display' and update all occurrences everywhere. Please make sure the changed sentences still make sense, not sure a find/replace is going to work everywhere

Did anybody ever look into moving this out of the pager section? I agree with @dawehner in #1 that this feel like a weird place for this.

Do we need to think about updating the machine name of the setting too? We now have a big difference between the name of the field in code and the name in the UI which can lead to more confusion but now from a DX perspective

Do we need to run the new label past some UI experts and make sure we all agree this is the best we can come up with, 'Destination' feels a bit vague to me.

johnv’s picture

Title: Change the misleading and unclear wording in Pager -> Link display » Change unclear wording for Pager option 'Link display'
Issue summary: View changes

ITMT, on D11.1, I cannot find the 'Link display' option in the pager setting, or anywhere on the view settings page, whereas #19 states it is still there on D11.0.
(EDIT: That is on a Page display - when checking a Block display, I can see the option. --> Updating summary with test

As suggested in #30, indeed, the term 'Link display' is still used elsewhere, amongst other in the 'more' link setting. These still must be addressed.

As dawehner suggests in #1 "Could we not just add a new group, as the link display really simply not belongs to the pager", the setting may move to a better location (affecting only the UI, not the saved configuration setting itself)
Now is the time!

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.