Theme developer... js problems, white screen, views

Clear the cache twice and take sure to reload your browser cache. This should probably fix your issue.

We got the same problem in a form using two selection (dropdown) menu. When the first tries to change the second using an ajax callbacks a similar error message is showed.
The problem exits on IE 8, Crome but surprisingly not on Firefox 4.0.

I have had the exact same error ("An AJAX HTTP error occurred") when trying to change anything at all inside a views item. Updated to latest views (beta3) and ctools (alpha4) and made all the prescribed cache actions, but it all made no difference.

I solved the issue by disabling the Theme Developer and Devel modules. Hope this helps others in this situation.

Obviously it would be nice being able to use devel and views at the same time, so I think this remains a bug.

Tino

Can you try out whether "theme developer" is the reason for this issue? If yes this issue should be moved to this module.

Sure! How?

Not sure how to test for causality beyond my it's-switched-off-and-now-it-works approach. I can see the Devel people say the same thing, that's it's a Views issue :S

Also, would be great if the OP and others with this issue could confirm if Theme Developer was enabled in their case.

Hi. I already have the Devel module switched off and I don't have Theme developer and I'm getting the same thing. It happens when I try to change fields or filter settings. I then hit the browser back button, go to the views main page, choose my view again and when I come back in the change is made and it's ready to be saved.Seems to work OK when I save it but the extra step to go out and come back it is frustrating. I would be happy to provide any information I can to help solve the issue. Thank you. (I just installed the latest dev version of Views yesterday)

What browser are you using? I have been using Chrome and recently I noticed some of the links to change settings in Drupal don't work in Chrome so I then switch to Firefox. I was getting the above error in Chrome. When I hit a dead link and went to FF, I tired the Views editing again and all works fine...so, it might be a browser issue.

Okay, to summarize, here are the steps that should get it temporarily fixed:

1. Disable all "Devel" modules including Theme Developer
2. Clear the cache twice from Admin > Performance > Clear All Caches
3. Clear your browser cache
4. Preferably use firefox when administering the views.
5. Thats it. Should work now.

So update status?

Remove useless tag.

I have the same problem trying to change ANY setting within the Views admin for a calendar I am trying to set up from scratch.

I'm using:

calendar 7.x-2.x-dev (2011-May-28)
ctools 7.x-1.x-dev (2011-Jun-08)
date 7.x-2.x-dev (2011-May-27)
views 7.x-3.x-dev (2011-Jun-09)

So ... if it was fixed, is there a chance someone's change accidentally got rolled back?

I got a fresh install, views 7.x-3.0-beta3 and ctools 7.x-1.0-beta1, I still have this error

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /admin/structure/views/ajax/add-item/archive/page/header
StatusText: OK
ResponseText: [{"command":"settings","settings":{"basePath":"\/","ajaxPageState":{"theme":"bartik","theme_token":"fivzDPq4qH9Jaf5CvvEcCK693hIbKerB0M59arZVeA0","css":[]},"admin_menu":{"destination":"destination=admin\/structure\/views\/ajax\/add-item\/archive\/page\/header","hash":"3a38763e01c5d265807338530b4771be","basePath":"\/admin_menu","replacements":{".admin-menu-users a":"0 \/ 2"},"margin_top":1}},"merge":true},...

I am using firefox running on linux

I disabled drupalforfirebug.... Finally got it working :)

This is NOT fixed!

No development modules on my end, it used to work mostly fine. Now it does not work at all. I get the error upon clicking on pretty much any setting within the Views UI, and by that I mean every setting.

I cleared each and every cache multiple times to no avail. If such an error should occur for whatever reason, it would be helpful for users and especially for developers to provide a bit more meaningful message. The response text in its current form is pretty useless.

Also, I get a similar error when checking for updates manually:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?render=overlay&id=328&op=do StatusText: OK ResponseText: n{"status":true,"percentage":"4","message":"Trying to check available update data ...\u003cbr \/\u003eChecked available update data for \u003cem class=\"placeholder\"\u003eFeeds XPath Parser\u003c\/em\u003e."}

On a side note: Just whose genius idea is it to mark issues as automatically fixed after 2 weeks of inactivity anyway? If an issue is not active for two weeks, then the issue is, well.. INACTIVE! But by no means can it ever be considered FIXED if there is no official resolution!

On a side note: Just whose genius idea is it to mark issues as automatically fixed after 2 weeks of inactivity anyway? If an issue is not active for two weeks, then the issue is, well.. INACTIVE! But by no means can it ever be considered FIXED if there is no official resolution!

Please calm down, disable javascript and everything is fine.
As long noone is able to provide a way to reproduce the issue it still can't be considered as total bug, or more important it's not possible to fix as most of the users don't want to fix it for themself.

If you search for the error message you will see that this error message doesn't come from views, but from drupal itself.
In general i would look at it with firebug and look at the full output etc.

Apologies for the tone, but stuff like this is really frustrating, and there seems to be plenty of it too.

Yes, after fiddling around for quite a while I also figured out that disabling JavaScript ultimately fixes the issue, which kept popping up in various spots. So I came to the same conclusion that it is not really Views specific, as parts of display suite and other modules seem to be affected as well.

I'll see if I can provide more information regarding this, hopefully at the right place too, as there appear to be many reports on many modules related to this.

I keep being amazed how easy it is to make a fool of oneself, and I have to admit I certainly managed quite well to do so in this case.

I am marking this as fixed now, at least in my case, as I reopened it in the first place.

The problem in my case turned out to be of most peculiar nature. There was a single runaway character before the start of a PHP file from the Search API module - the cursor in the editor must have slipped for a single character without me noticing. This in turn resulted in all kinds of bizarre issues - Autocomplete Deluxe was broken, Views was broken, Update was broken, Display Suite was broken, who knows what else was broken - everything BUT Search API was probably broken.

Now, it is a mystery to me how such a minor issue in one module has a major impact on various other modules, except the one the issue is actually in, without providing the slightest clue where to look for it (not even dev-tools would help, hooray fancy web technologies!).

But there you have it, in case such bizarre behavior does occur, it may be worth checking for runaway characters in third party modules just installed / updated. It certainly was in my case. although it turned out to be the last place I looked for it. Maybe my case was rather unusual, maybe this could be of assistance to someone else facing a similar problem.

To solve the mystery:

anything outside of the <?php tag in a file is considered HTML. When the file is loaded, that output goes directly to the browser. It was probably there on all pages, but not something you really noticed.

During AJAX operations, however, it's sending packets of data. That extraneous character corrupted the packet, making it unreadable, causing almost every AJAX operation to break.

/admin/structure/pages/nojs/operation/node_view/actions/configure

triggered this when drupalforfirebug was enabled.

I figured it out looking at the AJAX content in Firebug :-).

I have this issue, no devel module, no drupalforfurebug, nothing!

cleared cache 100times and no change. totally up to date install.

And no word about what you did/the actual error etc.

Daniel, thanks! Disabling "Drupal for firebug" saves me too.

solution for Theme developer > "themer info" users:
- disable Krumo display in devel modul settings
- clear all cache

it's accoured when you use "themer info" variable viewer and devel krumo together.

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.

#31 worked for me ! Thank you deanflory!

#31 worked also for me! Thanks a lot

Thanks a lot, for the "runaway character before opening php tags" tip. It works for me

I just changed jquery update from 1.8 to 1.7 and it is fixed.

I've tried...

1. Clearing Cache
2. Disabling jqueryUpdate
3. Disabling Devel
4. Clearing Cache some more

Still no luck.

In particular I have the issue on...
HTTP: 500
/admin/structure/ds/ajax/add_field/custom_field

Is this the same issue? Any other suggestions I should try.
Thanks

EDIT: I downgraded Display Suite to 7.x-1.7 and it appears to have fixed it.

#31 fixed for me also, downgrade to 1.7 jquery update

thanks

#31 worked for me as well ! Thank you deanflory!

You may already have a fix on this one, but I thought I'd add how I fixed it in case it helps:
a) I didn't have the problem on a site that used Devel & Theme developer (wasn't using views 3.6)
b) Installed Views - 3.6
c) Couldn't use the views UI at all -- clicking any link in it Gave me "An AJAX HTTP Error occurred. HTTP result code: 200" + debug info...
d) Disabled Theme developer -- Views works fine.

Was using Windows 7/Chrome/XAMPP localhost.

Disabling Theme developer has solved several other (seemingly unrelated) problems.

Thanks for all your efforts here.

The "Theme developer" module is known for it's various problems, because it manipulates the html of your output.
Maybe that module could have a list of paths on which it shouldn't be active.

#31 worked
thank a lot

I don't think views can do anything against it. Maybe the theme developer module could have a hardcoded setting to not be included on views admin pages.

Bump on #31. Worked for me as well.

#31 recommends disabling jquery_update but that will raise problems with features depending on jquery. #35 solved the problem for me.

One could always use jqmulti to allow multiple versions of jquery to run simultaneously.

http://drupal.org/project/jqmulti

#35 solved!

I had a similar problem, i was unable to edit Views (after clicking rearrange or edit the loader would rotate whilst nothing else happened) and the ajax error finally appeared only after i enabled and disabled installed and uninstalled jquery_update and toggled developer modules on an off.

Switching with jquery_update to 1.7 version had little effect although I was able to finally see some editing options, however when attempting to save changes a white screen full of text appeared, I had to return and see the changes not being saves.

I finally decided to search the localhost directory for all that could have influenced and interfere by searching for "*.js" files and sure enough inside one of the template directories there were some .js files that got in the way.

Namely "jquery.ui.core.js" had a line at the top

$.extend( $.ui, {
	version: "1.8.7",

I changed it to

$.extend( $.ui, {
	version: "1.7.0",

and the problem went away.

For all of those whom have bought template solutions this could be handy, template folders will often have UI subfolders with .js files, I've spent a good few hours getting to the solution. Views seems unable to handle later releases of jquery.

D.

I had this same issue with form that I was building in Drupal 7 and the "autocomplete" function for privatemsg module was giving me this same issue; after trying everything to no avail; once I disable the "Theme Developer" module this AJAX Error went away

Thanks!!!

Same thing here. Breaking output in views. Disabled Devel modules + simpledomhtml and everything seems to be fine.

I got the same problem when I was working with the theme developer. At that moment, I was using Chrome for my development. Then, I switched to the Firefox browser and then the issue was gone.