Attempting to edit any Views parameters causes bad output without a clear error. I've read the Views bug submission guidelines and have done my best to comply.
When I:
- Go to Administration » Structure » Views
- edit or create a View (admin/structure/views/view/test2/edit)
- add or edit anything, e.g. admin/structure/views/nojs/display/test2/page/display_title
- receive an edit overlay
- click Save or Cancel in the edit overlay
- bad output
Resulting URL is:
admin/structure/views/ajax/add-item/test2/page/[somepagename]
Where "somepagename" is argument, title, path, etc.
Output looks like several pages of:
[{"command":"settings","settings":{"basePath":"\/","pathPrefix":"","ajaxPageState":{"theme":"adaptivetheme_admin","theme_token": and so on.
I see several bugs that seem related but not clear solution other than one guy who rebuilt his site from scratch.
http://drupal.org/node/1119138
Some other things I've noted include:
- The Advanced section of editing a Views always opens an overlay, even if the Overlay module is turned off.
- Clicking Save does save the changes.
- Click the X in the Advanced overlay closes the overlay correctly; but clicking Cancel causes the bad output.
- When editing the Contextual filters, there's nothing in the More section of the Advanced overlay.
- There's nothing reported in the Drupal log. The Developer block is obviously useless when the page doesn't render. Logging is set to All Messages.
- Nothing is reported in Firefox's Error Console.
- All the links that cause errors have nojs/ in the pathname, but ajax/ in the destination, does that seem correct?
My environment:
- All modules are up to date. Caches rebuilt. Update script ran.
- Testing in multiple admin themes, including Seven.
- Disabled JQuery update; bug still present.
- I do not have secure_pages module.
- Tested across multiple browsers — Safari, Chrome, Firefox.
- I have ssh access to my server but don't seem to have permission to view my Apache log.
Comments
Comment #1
luke xi commentedI have exactly the same problem with you,so i come to search.I just updated to views 7.x-3.7 .
On my localhost,it doesn't happen,I don't update views on my local host .
I find a difference between 3.7 and before ,When i click to edit something ,the configuration dialog box
is on the left while center on old ones,when click apply or cancel,the error thrown exactly the same with you.
Comment #2
luke xi commentedI've solved this issue configuring jquery_update module by downgrading from 1.8 to 1.7 version.
Is there a solution that permits to work with jquery_update configured with 1.8 version?
Comment #3
slamorte commentedBrilliant! I downgraded as well and now it works here too. At least I have a work-around and can move forward.
I had a similar issue with the box placement; it would appear in the upper-left, but jump to centered when the box content was scrolled to the end. I didn't mention it because it seemed trivial compared to the missing functionality.
Comment #4
pinamac commentedThank you. Awesome Suggestion, it works perfect ! The jump is now also gone. Downgrading to 1.7 version does it.
Comment #5
robriley78 commentedSame problem - downgrading JQuery to v1.7 from the JQuery update module fixed it for me. Thanks for the tip.
Comment #6
dshields commentedThis solution no longer seems to work.
Comment #7
jsiesquen commentedThanks for the tip... downgrading the JQuery to v1.7. it works fine!
Comment #8
janv commenteddowngrading Jquery doesn't work here.
any other solutions?
Comment #9
permaculturegeek commentedIn Google Chrome the output is source code as described by the bug creator. In Opera 12 (Presto engine) I get a file download dialog (Open/Save/Cancel) - this suggests that the response is being served with a MIME type other than text/html - something that the browser isn't configured to process. I can't analyse the response in my inspector tools, as the inspector doesn't let me mimic POST requests.
Comment #10
Benone_ commented#2 worked for me too.
Comment #11
webfix commentedThanks!!! Downgrading the JQuery to v1.7.
Comment #12
egarbeil commentedDowngrading jquery worked here on several sites. 1.7 appears to be the way to go with the latest versions of Firefox and Safari.
Comment #13
SteveMushynsky commentedSame problem; same apparant solution. Changed to jquery 1.7 from 1.8
Comment #14
zura_lanch commentedI did the same (turned to 1.7 jQuery update) and it worked :) tnx
Comment #15
zura_lanch commentedI've just noticed that when I'm trying to manage display of content type "Custom display settings" is not outputted as a link (also other drupal 7 things aren't outputted as a link in administrative overlay). After turning jQuery update to 1.8 it started working well.
So I've to play with jQuery update versions depending what I've to do - manage display of content type or edit views from views ui. Headache!
Comment #16
dadaisme commentedDowngrading to 1.7 did the trick for views and even for another module and script (MD Slider) not related to this...
Thx a lot!
Comment #17
dshields commentedWhile it works, it's tough to say "downgrading is the solution"
Comment #18
mrcodez commentedThis worked for me as well. Glad to come across this thread.
From admin screen,
Modules -> JQuery -> Configure -> Change dropdown value to 1.7 -> Click save
Comment #19
igormagic commentedDowngrading worked for me, subscribing
Comment #20
lu_smithcon commented@futureisdream
Thanks for posting. It worked for me too.
Comment #21
BartGysens commentedProblem stays when I change to 1.7
Damn! Loosing lot of time on this ...
When do they keep this module still alive???
Comment #22
lu_smithcon commentedThis problem still exists, but setting Jquery Update back to 1.7 and clearing the cache worked for me.
Comment #23
oppure commentedI think upgrading jquery has somehow caused the problem for me but downgrading doesn't fix it! tried 1.7 and 1.4 as well.
Subscribing.
Comment #24
oppure commentedSort of fix here: http://drupal.stackexchange.com/a/73189
just disable javascript in views settings.