Running jQuery 1.8 or higher will crash the AJAX request when I was trying to add a new filter. Here is one of the error you can get while trying to use Views 3 with a jQuery 1.8 or higher.

AJAX An HTTP error occurred.
HTTP Result Code: 200
Debugging information FOLLOWS.
Path: /views/ajax?render=overlay
StatusText: OK

In addition, you can also get a white screen with json in the background.

#21 views-overlay-mess-1376686-21.patch689 bytesnod_
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch views-overlay-mess-1376686-21.patch. Unable to apply patch. See the log in the details link for more information. View
Members fund testing for the Drupal project. Drupal Association Learn more


dolu’s picture

I have the same issue.

Each AJAX action (sort, filter, pagination) throws an AJAX HTTP error.

I updated Views from 3.0-rc3 to 3.0 and ran database updates (there were no database update).

dolu’s picture

Category: support » bug

I think this a bug, so marking it as is.

Babymaggie’s picture

Hi guys, Im getting a similar issue - I'm running drupal 7.8 and I updated to views 7.x-3.0 Everytime I create a view (or update an old working view) with a sortable ajax I'm getting this when I click sort:

An AJAX HTTP error occurred.
HTTP Result Code: 404
Debugging information follows.
Path: /folder/?q=views/ajax?q=users/admin
StatusText: Not Found
Page not found | mysite
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
@import url("");
Skip to main content
Options for the administrative overlayIf you have problems accessing administrative pages on this site, disable the overlay on your profile page. Dismiss this message.

I get that 404 are missing pages, but in the preview the views with ajax work great!
Also if I remove the ajax setting everything behaves as you would expect.

I'm thinking of reverting back to my previous version of views to see if it fixes this or maybe I need to try to update Drupal? Could that be the problem? What do you think?

Many thanks for your advice guys, I think these are related issues, if not could someone please move my post.

Best wishes to all!

nod_’s picture

This is a different bug, see #1359798: Clean urls off break all Ajax views it's because clean urls are off.

Babymaggie’s picture

Thank you nod_ I must have disabled clean urls by mistake.

Anyway re-enabled clean urls, cleared the cache and logged out and back in and that fixed it for me.

I hope they can fix that nasty little bug though!

Thanks again nod_ for your fast and helpful response.

dolu’s picture

In my Drupal installation, Clean URLs are enabled, but I still get this bug.

longwave’s picture

Also seeing this when trying to use Ajax enabled views in the overlay.

sreynen’s picture

I'm seeing this error in @font-your-face, which uses AJAX views with /admin/ paths. Report here:

longwave’s picture

Title: AJAX error in views are in admin path after upgrading 3.0 version » AJAX HTTP 200 error in Ajax enabled views in the admin overlay after upgrading to 7.x-3.0

Improving issue title.

The Pixelworx’s picture

I'm having the same issue as mentioned in #6

I've tried rolling back as far as rc1 but the ajax pagination is broken

afsolano’s picture

Thanks for the improvement in the title

herve’s picture


Same issue here, with one of my own view. If i use ajax pager or filter in overlay, i get an AJAX error.



thinkdrupal’s picture

The issue appears to be on line 39 in ajax_view.js.

this.element_settings = {
url: ajax_path +,
submit: settings,

change to ...
this.element_settings = {
url: ajax_path,
submit: settings,

The previous version(7.x-3.0-rc3) of views did not append ''. Once I removed this, I no longer got the error. Hopefully someone will report why this was added in version 7.x-3.0.

longwave’s picture

sreynen’s picture

I've traced the error on both the JS and the PHP end to the point where I'm not sure where to look next. On the JS end, the AJAX request with the query string is coming back with status of 'parsererror'. On the PHP side, I've confirmed that both views_ajax() and ajax_base_page_theme() return successfully both with or without the query string, but ajax_deliver() is only called when the query string is removed. I'm not familiar enough with the AJAX system to know what happens between ajax_base_page_theme() and ajax_deliver(), but that seems to be where the error is happening.

catmurray’s picture


spuky’s picture

Title: AJAX HTTP 200 error in Ajax enabled views in the admin overlay after upgrading to 7.x-3.0 » AJAX HTTP 200 error in Ajax enabled views in the admin overlay after upgrading to 7.x-3.1
Version: 7.x-3.0 » 7.x-3.1

Error persists in 3.1 the fix from #13 changed a little...

changeing line 36

var queryString = || '';

var queryString = '';

makes the error go away...
this helps my user using the pagers of admin_menus admin views in the overlay...

nod_’s picture

Title: AJAX HTTP 200 error in Ajax enabled views in the admin overlay after upgrading to 7.x-3.1 » Error with Ajax enabled views in the admin overlay
Version: 7.x-3.1 » 7.x-3.x-dev
Component: Miscellaneous » Code

This just hides the issue, you'd have to add console.log(queryString); after the function to see what's getting messed up. I might have time to look at this tonight.

I'm changing the title, a HTTP 200 response is not an error, it's just the debugging alert that's pretty useless here.

nod_’s picture

I'm sorry but I can't reproduce the error, it just work, admin_menu, vbo and all.

Someone has an export of a broken view ? Could you tell me if clean urls are on or off when testing ?

(edit) looks like i finally found how to reproduce, good.

nod_’s picture

Ok got the issue.

The only problem is that the thing works too well. It keeps the render=overlay parameter from the overlay module and it just fail after that.

nod_’s picture

Status: Active » Needs review
689 bytes
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch views-overlay-mess-1376686-21.patch. Unable to apply patch. See the log in the details link for more information. View

try this. Looks like render would always be last so i'm just checking the "&" before and not after.

sreynen’s picture

Status: Needs review » Reviewed & tested by the community

The patch in #21 fixes the problem for me.

spuky’s picture

#21 fixes the issue for me too and makes sense I knew my leaving out the solution was just a hack to get the site working again..

dolu’s picture

Patch in #21 is fine, there is no more ajax error (I tried in 3.1).

rachelnicolewhite’s picture

Patch #21 solved all the problems for me as well, thanks so much.

DaraghOB’s picture

Version: 7.x-3.x-dev » 7.x-3.1


I'm experiencing this issue since upgrading to latest version of Views (7.3.1). Ajax http 500 errors are triggered in Admin view when making any changes to a view. When accessing page views, trying to move to the next page triggers the same error message. I edited the view (a very simple one) to see if there was anything in config that would be causing the error. Views page is now not visible (returns a 500 error as well).

This also happens on a filtered view of the same content type that was created as a totally seperate view and has not been edited (but was working prior to 7.3.1 upgrade). View filters block loads OK but once options are selected filtered view returns a 500 error and page doesn't load.

As this is a core element of the site I'm building out (internal company project but with a very tight deadline) it is a bit of a pain.

Any suggestions?

nod_’s picture

Version: 7.x-3.1 » 7.x-3.x-dev

Have you tried the dev version of views ? lots of patches got committed lately, you might get lucky.

I don't think it's the same issue you're experiencing, in this case there was no error 500.

DaraghOB’s picture

I've gone to the dev version and the 500 errors are not as frequent (at least the pages are working). I am getting an AJAX timeout error when trying to save views though... i've upped timeout and memory in .htaccess.

nod_’s picture

That's not the same thing. You should open a different issue with steps to reproduce your error.

As far as this issue is concerned #21 will fix it. It's not perfect but good enough.

dawehner’s picture

Status: Reviewed & tested by the community » Fixed

I could reproduce the problem and in fact this fixed the problem for me. Thanks!

Committed to 7.x-3.x

jkaine’s picture

Patch in #21 worked great. Thanks for the fix.

afsolano’s picture

The patch #21 worked fantastic. Thanks !!!

sammyframson’s picture

Patch in #21 worked for me as well running views 7x - 3.1. Thanks

nicodv’s picture

Hi, it will be the first time I apply a patch. Can anyone guide me? I'm having the same problem as described (when browsing fonts in @font-your-face)

I tried to follow but didnt help: no diff -u -r1.51 example.module or other clue that pointed me in the right module (?)

Thanks in advance.


Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

davidseth’s picture

Status: Closed (fixed) » Reviewed & tested by the community

The patch #21 is perfect. I was tearing my hair out on this one :)

Please commit this. 9 people (including me) reported that this fixed their problems.


Status: Reviewed & tested by the community » Needs work

The last submitted patch, views-overlay-mess-1376686-21.patch, failed testing.

davidseth’s picture

Status: Needs work » Closed (fixed)

Sorry for the last message about committing. I can see that the latest version of views has already got this in place. Non of the messages above mentioned that this was committed (next time I will just view the newest code!).

deanflory’s picture

Anyone having lots of AJAX issues might want to try disabling the jquery_update module, worked for me. Just spreading the info, unsure if it's related to this issue.

Watergate’s picture

I had/have the same problem, however, changing jQuery version to 1.7 (or lower) in the jquery_update module configuration form did the trick.

luckyape’s picture

MrWatergate solution worked for me also, it's possible that < JQuery 1.8 should be added to the requirements for d7 Views module.

tomhung’s picture

solution #40 worked for us

albertguedes’s picture

I have the same problem with ajax, and so, change jquery to 1.7 version fix.

r_wel’s picture

Same with me although I never got an ajax error code, just a bunch of garbage on the screen - I've got some tech background so I guessed it was an ajax error. Those that don't probably would not have a clue on how to search for help.

I changed to 1.7 and problem went away.

veleiro’s picture

Status: Closed (fixed) » Needs work

I am still having this problem even though I switched to Jquery 1.7 or 1.5

darol100’s picture

Title: Error with Ajax enabled views in the admin overlay » jQuery 1.8 Higher support for Views 3.
Issue summary: View changes
Issue tags: +JavaScript, +Ajax, +jQuery


Did you clear the caches ? Maybe that will work. This is the second time that have happen to me and it always works. I can confirm #40 works. I set up to jQuery 1.7 and it works.

Since, this incompatibility issue with the jQuery version, I will change this issue to make jQuery compatible with jQuery 1.8 or higher.

ugintl’s picture

I am using views 3.14 and it already has the patch from #21. Jquery 1.8 works, but above it, does not work.