The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I used a machine name "default" for my default page display, and it wiped out that display because of duplicate entry.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 1212916-validate-display-id-big.patch | 647 bytes | dawehner |
Comments
Comment #1
drjonez commentedFYI, using Views 6.x-3.x-dev (2011-Jun-25) - will update to the latest one (jul7) soon.
This isn't that critical for me, as I had other displays that had most of the same data. But I did have to rebuild some things. Just have to remember not use "default" as the machine name for a page display.
Thanks for all your hard work everyone!
Comment #2
merlinofchaos commentedOk yes that's a bug, we should be validating that you don't try to change a display's machine name to one that already exists.
Comment #3
drjonez commentedIt actually does validate for ones that do exist... duplicate names are caught... unless you use "default"
hopefully an easy fix, i haven't had time to dig into the code to investigate, but I thought I'd report.
Comment #4
drjonez commentedComment #5
dawehner'default' is already checked, the problem is that you wrote it with big letters. Views currently allowed this.
Changed this here.l
Comment #6
trevortwining commentedTesting this now...
* Created a new view, set up some basic settings in the defaults. (node display, sort by date)
* Created a new display (block). Called it 'default'. Received error "Display id should be unique."
* Machine-Named the display 'block1', saved the view. Save happens okay.
* Edited the display again and tried to change machine name to 'Default.' Received same error as above.
Based on this it looks as if the patch works as advertised.
Comment #7
dawehnerThanks for testing it out! Commited to 7.x-3.x and 6.x-3.x
Comment #8.0
(not verified) commentedwanted to remove views info for security purposes.