Comments

Blanca.Esqueda created an issue. See original summary.

blanca.esqueda’s picture

StatusFileSize
new2.73 KB
blanca.esqueda’s picture

Issue summary: View changes
blanca.esqueda’s picture

Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 2: views_more_link_target-2743631-2.patch, failed testing.

blanca.esqueda’s picture

StatusFileSize
new2.8 KB
blanca.esqueda’s picture

Status: Needs work » Needs review

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.

kristen pol’s picture

Status: Needs review » Needs work

Thanks for the patch. Not sure this would be accepted but I took a look at the code and noticed a couple small things:

  1. +++ b/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php
    @@ -1761,6 +1765,12 @@ public function buildOptionsForm(&$form, FormStateInterface $form_state) {
    +          '#description' => $this->t("Open in new tab/window"),
    

    Would be good to simplify to 'Open in new window' and use single quotes instead of double.

  2. +++ b/core/modules/views/src/Plugin/views/display/DisplayPluginBase.php
    @@ -2090,6 +2101,10 @@ public function renderMoreLink() {
    +      if ($this->getOption('link_display_target') == true){
    

    Don't need the "== true" part.

deepak goyal’s picture

Status: Needs work » Needs review
StatusFileSize
new14.12 KB

Hi @Kristen Pol
The patch #6 not applying on Drupal version 9.1.
So I have created new patch for version 9.1 please review and there were some coding standandard issues I also fixed that.

kristen pol’s picture

Status: Needs review » Needs work

Thanks for the update but the patch failed to apply via the testbot.

suresh prabhu parkala’s picture

Status: Needs work » Needs review
StatusFileSize
new5.79 KB

Re-rolled patch please review!

Status: Needs review » Needs work

The last submitted patch, 19: 2743631-19.patch, failed testing. View results

kristen pol’s picture

Thanks for the updates.

@Deepak Goyal and @Suresh Prabhu Parkala Please add interdiffs when you are updating patches to it's easy to see the changes, thanks: https://www.drupal.org/documentation/git/interdiff

hardik_patel_12’s picture

Status: Needs work » Needs review
StatusFileSize
new5.83 KB
new671 bytes

Tried to solve failed test cases. Kindly review a patch.

samiullah’s picture

StatusFileSize
new72.05 KB

@hardik patel , I m not seeing any changes in view UI when i apply the patch.
Can u provide steps to test along with expected screenshots

kristen pol’s picture

StatusFileSize
new54.72 KB

I don't see it either.

kristen pol’s picture

Status: Needs review » Needs work
StatusFileSize
new77.13 KB
new13.26 KB
new47.23 KB

I found the setting.

1) This is for more than just more links. I thought it was only for more links based in the title and issue summary.

2) See the alignment issue in screenshot.

3) Even after choosing it, it's not obvious from the top level because it just says "None".

4) It didn't work for me when I changed a view (recent content) to use it. The target wasn't added.

kristen pol’s picture

Issue tags: +Needs issue summary update
StatusFileSize
new130.24 KB
naresh_bavaskar’s picture

Assigned: Unassigned » naresh_bavaskar
naresh_bavaskar’s picture

Assigned: naresh_bavaskar » Unassigned
vakulrai’s picture

StatusFileSize
new692 bytes
new5.81 KB

@Hardik_Patel_12 , #22 is working as expected for more link.
Though i have made one change in the following snippet :

$form['link_display_target'] = [
          '#type' => 'checkbox',
          '#description' => $this->t("Open in new window"),
          '#default_value' => $this->getOption('link_display_target'),
        ];

as

$form['link_display_target'] = [
          '#type' => 'checkbox',
          '#title' => $this->t("Open in new window"),
          '#default_value' => $this->getOption('link_display_target'),
        ];

This will take care of the alignment issue raised by #25.

vakulrai’s picture

Status: Needs work » Needs review
amietpatial’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new37.92 KB

#30 works fine on checking option "open in a new tab" and then clicking on "view more" it's opening on new tab .

amietpatial’s picture

amietpatial’s picture

StatusFileSize
new73.77 KB
quietone’s picture

Status: Reviewed & tested by the community » Needs work

@amietpatial, thanks for verifying that this patch works! That is good to have recorded. There are other things that need to be done before setting an issue to RTBC. This one is tagged as needing an issue summary update, so that, at least needs to be done. There is more information about the process in the community guides, in particular reviewing patches has lots more details. One thing I like to keep in mind is that the issue should be easy for a reviewer to review and completely ready for the committer.

This is tagged as needing an issue summary update so setting to NW for that. Please add before and after screenshots to the issue summary so they can be found. And although I am not tagging this for tests due to my lack of knowledge of views, I suspect that is needed as well.

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.

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.