Since the last 2 core updates I have not been able to make any changes to a view. When clicking the "apply" button after making a change in the "edit" page dialog pop-up, nothing happens and no error is registered in the error log.

Comments

brisath created an issue. See original summary.

xjm’s picture

xjm
she/her
Primary language English
commented
Version: 8.7.10 » 8.8.x-dev
Issue tags: -views

@brisath, this might go without saying, but have you cleared both your site and browser cache?

Also try checking the developer console of your browser for any JavaScript errors?

Did this also occur when you tried updating to 8.8.0?

brisath’s picture

brisath commented

I haven't installed the new 8.8.0 so will try that. I have cleared browsers and had the same issue on multiple computers and different browsers. Will look for JS errors too.

cilefen’s picture

cilefen commented

The browser console log could reveal something.

lendude’s picture

lendude
Primary language Dutch
Location Amsterdam
commented
Status: Active » Postponed (maintainer needs more info)

Yeah this sounds like a JS error, but some logs/errors are needed here because this obviously doesn't happen for everybody.

Does this also occur on a clean Drupal 8 install for you? Or only an a specific site? And if on a specific site, are there any relevant contrib modules installed or any Views custom code active?

brisath’s picture

brisath commented

Upgraded to 8.8.0 and still getting the same problem. Nothing shows in Drupal watchdog but the browser says

Uncaught Error: Syntax error, unrecognized expression: #
at Function.se.error (jquery.min.js?v=3.4.1:2)
at se.tokenize (jquery.min.js?v=3.4.1:2)
at se.select (jquery.min.js?v=3.4.1:2)
at Function.se [as find] (jquery.min.js?v=3.4.1:2)
at k.fn.init.find (jquery.min.js?v=3.4.1:2)
at new k.fn.init (jquery.min.js?v=3.4.1:2)
at k (jquery.min.js?v=3.4.1:2)
at c (bootstrap.min.js?v=1.x:6)
at HTMLAnchorElement. (bootstrap.min.js?v=1.x:6)
at Function.each (jquery.min.js?v=3.4.1:2)

brisath’s picture

brisath commented
Version: 8.8.x-dev » 8.8.0
Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active
lendude’s picture

lendude
Primary language Dutch
Location Amsterdam
commented
Title: Cannot save views changes » Cannot save views changes due to a JavaScript error
Version: 8.8.0 » 8.8.x-dev
Status: Active » Postponed (maintainer needs more info)

Still needs more info, it's good to know that this occurs as a result of a javascript error, but we still have no idea as to the origin.

Per #5

Does this also occur on a clean Drupal 8 install for you? Or only an a specific site? And if on a specific site, are there any relevant contrib modules installed or any Views custom code active?

See #2647916: Views ajax modals stop working in certain scenarios: due to JS settings caching, AJAX responses may set wrong ajaxPageState.libraries, causing problems for subsequent AJAX requests/responses for the level of debugging that can be needed to fix weird javascript errors in Views UI.

brisath’s picture

brisath commented

Clearing caches isn't solving anything and we are not in a position to do a clean Drupal 8 install just to test this. Right now I am able to edit views by opening the edit component in another tab which doesn't use ajax and is a pain to do but at least we can work on things.

brisath’s picture

brisath commented
Status: Postponed (maintainer needs more info) » Active

Still same problem, cannot edit views on my site.

cilefen’s picture

cilefen commented

The browser tools network tab will show what the browser sends to Drupal and what Drupal returns in the Ajax call.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented

> at c (bootstrap.min.js?v=1.x:6)
> at HTMLAnchorElement. (bootstrap.min.js?v=1.x:6)

This could be Bootstrap or theme related, similar to #2903656: Updating to Drupal core 8.4.0-beta1 results in not working dropdown menu

lendude’s picture

lendude
Primary language Dutch
Location Amsterdam
commented
Status: Active » Postponed (maintainer needs more info)

@longwave well spotted. Without steps to reproduce, we can't do anything but guess.

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
quietone’s picture

quietone commented
Issue tags: +Bug Smash Initiative

@brisath, have you resolved this problem? If so, what did you that fixed it? If not, can you provide more details as asked for in #5 and what themes you are using, from #12.

I searched for duplicates and did not find any.

Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

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.

quietone’s picture

quietone commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

And three months has passed and no additional information has been provided as asked for #13 and again in #17.

Therefore, closing as outdated. If this is incorrect reopen the issue, by setting the status to 'Active', and add a comment explaining what still needs to be done.

Thanks!