Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When clicking on "Check Manually" when viewing the available updates screen or in the status report I receive the following error shortly after the progress bar appears:
An AJAX HTTP error occurred.HTTP Result Code: 200Debugging information follows.
Path: /batch?render=overlay&id=22&op=doStatusText: OK
ResponseText: {"status":true,"percentage":"42","message":"Trying to check available update data ...\u003cbr \/\u003eChecked available update data for \u003cem class=\"placeholder\"\u003eExternal Links\u003c\/em\u003e."}Drupal for Firebug General MessagesThere were no messages sent to the general log. Please use "firep($item, $optional_title)" to output messages to this console.Devel Module is Not InstalledPlease install and enable the Devel Module to display the SQL queries.There was no form altering.There was no user processing.There was no node processing.There was no views processing.There was no page processing.
Initializing.
..Drupal for Firebug General MessagesThere were no messages sent to the general log. Please use "firep($item, $optional_title)" to output messages to this console.
Devel Module is Not InstalledPlease install and enable the Devel Module to display the SQL queries.
There was no form altering.
There was no user processing.
There was no node processing.
There was no views processing.
Page Alter Support is Not Yet Implemented
Comment | File | Size | Author |
---|---|---|---|
#17 | panels_error.zip | 2.33 KB | Max_Headroom |
#6 | updating_detection_of_headers_for_d7.patch | 1.19 KB | OnkelTem |
#1 | bloqueio.JPG | 45.08 KB | roseiro |
Comments
Comment #1
roseiro CreditAttribution: roseiro commentedMe too me it's the same with the discharge of language.
So this one trnho installed nothing else besides Drupal 7.0, Locale updater7.x-1.0-alpha1 and locale-1.0-dev updater7.x
Attached image transmission.
Comment #2
boftx CreditAttribution: boftx commentedDisabling Drupal for Firebug eliminates the problem.
Comment #3
rfayI'm going to call this a Drupal for Firebug problem then....
Comment #4
jordanaWith drupal for firebug & preprocessor enabled, I also get a similar error (result code 200) when I try to edit configuration options for my content fields (i.e. when I press the gears icon when I add an image field to a content type)
Also got errors when I tried uploading files.
I also got a different ajax error "NPMethod called on non- NPObject", which I haven't been getting after I disabled the module, so I'm assuming it also had to do with an issue with the firebug module.
All errors stopped after I disabled the modules.
Hope this may help in debugging the problem.
Thanks for all the hard work
Comment #5
OnkelTem CreditAttribution: OnkelTem commentedThis is very bad thing
Comment #6
OnkelTem CreditAttribution: OnkelTem commentedOh, now we go with drupal_get_HTTP_headers(), not drupal_get_headers()...
Patch is attached
Comment #7
OnkelTem CreditAttribution: OnkelTem commentedComment #8
sammyframson CreditAttribution: sammyframson commentedI was running into the same issue when trying to manage display of fields within my content types. It doesn't seem to be content type specific. Any attempt to change the display of fields within a content type initiated this error and when I tried to save changes, nothing was changed. My site was at a standstill and then I tried disabling Firebug for Drupal and I was able to proceed.
Found similar info with a devel bug but I did not have that module installed: http://drupal.org/node/699668
Comment #9
OnkelTem CreditAttribution: OnkelTem commented@sammyframson
Have you tried the patch?
Comment #10
vbplusme CreditAttribution: vbplusme commentedI have manually installed the patch and no longer get the AJAX error, thanks for the help.
Comment #11
bombo CreditAttribution: bombo commentedI had the same ajax issue when trying to fill autocomplete fields or in views with drupalforfirebug activated. patch in #6 worked. thx.
Comment #12
geek-merlinas of #10 and the dup: #1040392: [THIS ISSUE IS CLOSED - DO NOT COMMENT]An AJAX HTTP error occurred. HTTP Result Code: 200 FIXED
setting to tested and praying to maintainers
Comment #13
geek-merlinComment #14
populist CreditAttribution: populist commentedThanks for checking into this and this has been now been committed to the repository.
Comment #15
populist CreditAttribution: populist commentedComment #17
Max_Headroom CreditAttribution: Max_Headroom commentedSeems the bug is back. I've tested it with the latest dev versions of this module and Panels on my local host. Tested in a vanilla setup.
I get the error when trying to add any of the Selection rules in a Variant:
Turning this module off and Panels work.
Attached is a txt with all the gooblygook in the ResponseText if anybody is interested.
Comment #18
dingdongdong123 CreditAttribution: dingdongdong123 commentedI don't know how to apply or set up the patch.Can you tell me the details?
Comment #19
sammyframson CreditAttribution: sammyframson commentedHere is a pretty good, easy to follow article on applying patches... http://bri-space.com/content/how-patch-drupal-module-windows
Comment #20
srkamineni CreditAttribution: srkamineni commentedI had echo statements, print statements from a code I imported into a module..
Removing them fixed it.
Comment #21
frobI am marking this as a duplicate because the issue as it was is fixed. The panels specific fix is being discussed in a different thread.
Drupal For Firebug Breaks Panels
Comment #23
isholgueras CreditAttribution: isholgueras commentedI have the same problem for this 2 days. I haven't got any drupal for firebug, any devel module, no errors with the MySQL max_allowed_packet and no errors even with max_execution_time of php.ini. The problem was a damn character before a "<?php" in one custom module. I think it's because the text editor... I delete the '^R' character and all works fine.
I found it by disabling modules one by one and executing the "check for updates" script in /admin/reports/updates/check. When I disabled this wrong module and the script runs... THE ERROR WAS HERE!!!
I'll show you my code and the damn hidden character. I hope it helps...
Comment #24
deanflory CreditAttribution: deanflory commentedAnyone 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.
Comment #25
frobdeanflory, if you are having an issue with compatibility with jquery_update and drupalforfirebug then please let us know what version of drupal, drupalforfirebug, and jquery_update that you are using.
If the problem persists please open a new issue.
And thanks for the info. :)
Comment #26
kubilayrd CreditAttribution: kubilayrd commented#24, Thanks @deanflory, this worked me, too.
However, since I need this module, I didn't disable completely but downgraded the jQuery Version from 1.8 to 1.7. I think there's something wrong with jQuery 1.8 when it comes to work with Drupal.
Comment #27
frobYes, There is an issue for this in the jquery_update module. it seems not so much to be with Drupal and jQuery1.8 as much as jQuery 1.8 and jQuery UI.
Comment #28
trevorforrest CreditAttribution: trevorforrest commentedI concur with #26 this solution does work....there seems to be an issue with version 1.8
Comment #29
tbw17 CreditAttribution: tbw17 commentedI've run out of ideas where to look for this solution. I've searched endlessly all ajax errors I can find, none are specific to this form that I've located and none are specific to the modules involved.
It first started using Location with GMap. I contacted the maintainer and posted there about how the ajax autocomplete would never complete, so the form would always be submitted prior to ajax finishing and return a fatal error. After weeks of searching and reporting back for help, no luck. After uninstalling those modules, I installed Leaflet 7.x-1.0 beta2, its library (Leaflet v0.5.1-0), GeoCoder 7.x-1.2, Geofield 7.x-1.1, Geophp 7.x-1.7 and now when I add the geofield field to the content type via manage fields and click on format settings for Leaflet and save it (with or without making any changes to the settings) I receive the error message below and cannot proceed.
I sincerely apologize if this is NOT where to place this, but I can't tell where it should go...a new issue somewhere? If so, please advise and I'll post there. Too new to Drupal to know all the ins and outs, and appreciate any help in resolving this persistent "ajax error" issue. Thank you.
I am NOT using drupalforfirebug or jquery_update - the two modules everyone is saying need to be disabled...
I am using Drupal 7.4
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /system/ajax
StatusText: OK
ResponseText:
Fatal error: Call to undefined function element_validate_integer_positive() in /home/(my domain)/includes/form.inc on line 1356
This is the code from lines 1352-1357 in includes/form.inc:
// Call any element-specific validators. These must act on the element
// #value data.
elseif (isset($elements['#element_validate'])) {
foreach ($elements['#element_validate'] as $function) {
$function($elements, $form_state, $form_state['complete form']);
}
Comment #30
frobWhat is very interesting to me about that error is that the function that is supposed to be called is in the same file, line 4188.
http://api.drupal.org/api/drupal/includes!form.inc/function/element_vali...
Sorry I cannot be of more help and you're right. This isn't really the place to be asking about this. You should checkout the support forums. You could also checkout one of the #drupal channels on IRC.
Just as a precaution, you said you where new to Drupal, make sure you clear your caches, try in other browsers, use firebug to see if there are other js errors that could be causing this, uninstall all modules that are disabled, try a fresh installation and build the same thing in a vanilla drupal install, do a registry rebuild with the drush rebuild registry module, and before you do anything backup your database.
Welcome to Drupal.
Comment #31
maximiano CreditAttribution: maximiano commentedComment #32
MandySingh CreditAttribution: MandySingh commentedHey,I resolved that error...you just need to downgrade the jquery version from 1.8 to 1.7 in jQuery Update module
Comment #33
RamezAshraf CreditAttribution: RamezAshraf commentedDowngrade jQuery to 1.7
worked for me after loong time of (right click-open in new tab) just to get around it.
Thanks for the thread
Comment #34
kopeboy CreditAttribution: kopeboy commentedGuys, I tried everything, it has been 3 DAYS. I got sick. I argued with my hosting because I thought (or maybe I still think) it was their problem. PLEASE HELP ME.
I'm having this problem: AJAX not working in Manage Display of any content type. I cannot move row or edit configurations on any field, cause ajax won't load the form or move the rows. Still, everything works in Views.
I tried different versions of core, of jquery, patches to jquery, disabling all the modules (also clean urls), disabling features, base_url, rewrite base.. but the possibilities are too many to isolate a single potential problem.
I can't figure out what this is. I was thinking is the hosting provider because it happened when (but I'm not sure) I asked them to change my main domain from one to the second I bought.
I'm getting "Invalid form POST data" at system/ajax.
Drupal core 7.26
Omega 4.1
Shared hosting at public_html, single site
Comment #35
kopeboy CreditAttribution: kopeboy commentedComment #36
deanflory CreditAttribution: deanflory commentedkopeboy, I've had similar/same problems with Display Suite Manage Fields forms not performing correctly. In my case, I was able to move a field from the disabled region to another region and then what I'm guessing is the form's AJAX kicked-in, seemed to perform the operation (could see loading in browser), then the browser would finish loading whatever was being downloaded during the operation but wouldn't then tell the loading animation that it was complete, thus hanging all functionality.
I took two days disabling > testing > disabling > testing modules and found the following were all individually causing errors that prevented the DS Manage Fields forms from working:
I created bug reports in each of these modules (I think), notifying them of the issue as I think it's a pretty big bug/incompatibility when necessary functionality like this is rendered inoperable. I'm in the process of going through issues so we'll see if anything has been resolved or at least acknowledged.
Hopefully this list above will keep others from going crazy (too late).
Comment #37
frob@kopeboy please don't change the issue status to Needs Review unless you have a patch that needs review. The issue status all mean something.
Active: the problem is Actively being worked on.
Needs Work: The patch that was submitted doesn't work and needs work before being testing again.
Needs Review: A new patch has been submitted and needs to be reviewed
More information have be found here: https://drupal.org/node/156119
If you are having trouble with the Drupal for Firebug module then please open a new issue.
Comment #38
Amol.anant CreditAttribution: Amol.anant commentedI had the same issue. its issue with JQuery version 1.8 due to some charachter, it works well with version 1.7.
Amol Yeram
Comment #39
ezsolution CreditAttribution: ezsolution commentedMake sure that you are not using jQuery 1.8
You can see your settings at: /admin/config/development/jquery_update
jQuery 1.5 and 1.7 seem to play well with views. jQuery 1.8 currently does not.
Reference site: http://ezsolution.in/?q=ajax-http-error-200-when-try-manage-field-displa...
Comment #40
W.M. CreditAttribution: W.M. commented#23 at this post solved the issue for me.
Here at:
https://www.drupal.org/node/1022516#comment-6183024
I had a module file that included non-latin characters. It was encoded using UTF-8 with BOM, I had to change it to UTF-8 without BOM and problem disappeared.
Thanks Ignacio.
Comment #41
xiaomo CreditAttribution: xiaomo commentedNot sure which of the following solved the problem but it works
Disabled og context
Disabled Ajax comment
Changed Jquery to 1.7 in both selection
Comment #42
Georgii CreditAttribution: Georgii commentedIn fact the #23 above was the most correct. The issue happens not because of something in jQuery Update module and not because of 1.9, 1.10 etc. versions of that lib.
The issue comes from an incorrect encoding of some file in a contrib module.
Solution
You should really search for that module by disabling them one by one and once you find that module convert it to UTF-8 without BOM. Pretty simple huh.
BTW one might ask "why downgrade to 1.7 jQuery helps?"
I don't know. But 1.7 tolerates AJAX responses with an incorrect 1st symbol. 1.8 and beyond - does not.
Comment #43
frobEveryone should stop posting in this very old issue. This issue was opened 4 years ago in 2011, and closed initially 4 years ago and again 3 years ago.
Please stop posting in this issue.