I created and saved a view, with one or more displays (in the case in question, it had two page displays). I save the view, and go back a few times to edit it.
I haven't yet figured out when this happens, but sometimes I am unable to edit one of the displays. When this is the case:
- when I select the view and click on the "Edit" link, I see briefly the warning "You have unsaved changes". However, it quickly disappears again.
- In my case, I can without problems edit one of the two displays, and save the changes.
- However, the other display I cannot edit. Again, when I click on the display tab, I briefly see the warning "You have unsaved changes", but it disappears again. There is no hint of the view display being locked for editing, so I cannot force to break the lock.
When I now click on any of the view elements to try to change it, or try to add a field or whatever, I briefly see that something seems to be happending (the spinning wheel appears for a longer or shorter amount of time), but then nothing happens.
Trying to figure out how I can make that view display editable again, I noticed that I can edit the view again when I delete the row from the cachetags table with the tag config:views.view. .
If the view is locked, I would expect to see the respective warning and be offered the option to break the lock (editing as administrator and/or with uid1), so that I could edit it.
Comments
Comment #1
Anonymous (not verified) commentedAndreas Speck created an issue. See original summary.
Comment #2
Anonymous (not verified) commentedI have to correct myself: it seems deleting the respective entry in the cachetags table does not always solve the problem.
Comment #3
Strutsagget commentedI get the same problem. For me a lot of the time i just delete the whole view and start over again. And depending on what order i do stuff it usually works. Seems to happen often when there is no url on a page in the beginning.
Comment #4
wenwenwu99 commentedIt hardly believe there are so few to report this problem. I have the same issue, does this relate to the environmental I used? I use wamp.
Comment #5
stella commentedI've been able to trigger it with two different scenarios:
Scenario 1:
1. Create a new view, add a block or page or whatever display you want from the wizard.
2. Add a second page view - note no page path is set on a new page display.
3. You get an error about no path set for the view.
4. Click to edit the path - little spinning wheel appears and then disappears.
5. Same thing happens when you click to edit anything else.
6. Trying to save the view or clicking cancel button causes the "You have unsaved changes." message to appear.
Scenario 2:
1. Create a view with a couple of different displays, but with shared filters.
2. Add a new filter to one of the displays. This should ideally be a filter where you have to click "one of" and select from a list of allowed values.
3. On the filter config screen switch the drop down to "override for this display"
4. Limit the filter to one of the allowed values
5. Save the filter
6. You will now get "No valid values found on filter: Tags" or similar for the other display as the filter was added there but not fully configured before the "override this display" option was chosen.
7. Trying to save the view or clicking cancel button causes the "You have unsaved changes." message to appear.
The only way I've found to get past this issue is to delete the display, or in some cases when it's the only display, is to delete the view.
Comment #6
sonfdI'm not sure if I was experiencing the exact issue here or just a similar issue.. I was able to work around this with
drush cr.Comment #9
quietone commentedI tested this on 9.3.x and was not able to reproduce this error. I followed the steps given in #5. In Scenario 1, step 4 succeeded and in Step 5 clicking anything else worked as well. In Scenario 2, step 5 succeeded and there were no error messages such as given in step 6.
Therefore, closing as cannot reproduce. If you are experiencing this problem reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").
Thanks!