When I try to duplicate a block view as a page, views module says (correctly) that the page view uses a path and it's not defined. But if I click on the path to set it, nothing happens. Therefore I cannot set the path neither save the new view because of the error.

Comments

Alex72RM created an issue. See original summary.

aveach.bfr’s picture

aveach.bfr commented

I've replicated this issue, but it's a larger issue. I created a block display and it was working properly. I then duplicated the block display without changing anything. The overlay no longer appears when trying to change a value or setting in either the original display or the duplicate. I have 2 other displays in this view and they both work properly.

It looks like the real issue here is that if you duplicate a display (possibly just a block display) you can no longer see the overlay when attempting to change a setting.

vbouchet’s picture

vbouchet
Location Toulouse
commented

Duplicating from page to block worked perfectly for me. But when I duplicated the block display to REST export, then I faced the same issue and was not able to set the path.

Workaround: Disable Javascript on your browser so the modal to set the path will open as a normal page.

dawehner’s picture

dawehner
Primary language German
commented

@vbouchet
Does this mean there is some JS error happening?

vbouchet’s picture

vbouchet
Location Toulouse
commented

@dawehner
I am not able to reproduce it anymore. There was no error in logs but I am not sure I checked the JS console. I will update the ticket if I reproduce it or have more info.

sagesolutions’s picture

sagesolutions commented

When I duplicated the block display to REST export, I was getting a This display has no path. message.

It turns out I had to change the format from Unformatted list to Serializer. In my mind this should happen automatically when duplicating the block as a REST export.

Version: 8.1.0 » 8.1.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.1.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. Branches prior to 8.8.x are not supported, and 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.

quietone’s picture

quietone commented
Status: Active » Closed (outdated)
Issue tags: +Bug Smash Initiative

@Alex72RM, Thank you for reporting this problem. We rely on issue reports like this to improve Drupal core.

I tested this on Drupal 10.1.x, standard install, and was not able to reproduce this error. I followed the steps given in the Issue Summary.

Therefore, closing as outdated.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!