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.
Always get following error for a milisecond, after this it says succesfully installed.
an ajax http request terminated abnormally. Debugging information follow. Path: drupal/authorize.php?batch=1&render=overlay&id=1&op=do ReadyState: 4
I'm not sure this bug qualifies as major, as everything works. But from a UX perspective this a serious WTF and maybe there is a hidden major bug somewhere causing this.
Comment | File | Size | Author |
---|---|---|---|
#1 | ajaxInstallError.png | 9.51 KB | aspilicious |
Comments
Comment #1
aspilicious CreditAttribution: aspilicious commentedMaybe this componenent is better...
+ added a screenshot I could make by being fast :)
Comment #2
Bence CreditAttribution: Bence commentedI only get this error if I press the back button in my browser, after installing a module with the built-in installer. Because then the installer tries to install the module once again, and throws this error.
Comment #3
aspilicious CreditAttribution: aspilicious commentedThis error is only visible for a moment between starting the installation and getting the "all is green screen". If your server is fast you probably wont notice it.
When I push back I get this error: #1009716: Display readable ajax error when pressing "previous page" in browser after any batch operation..
Comment #4
Bence CreditAttribution: Bence commentedAh, sorry, then ignore my post. I copied it to the proper issue :)
Comment #5
mccask CreditAttribution: mccask commentedGetting the same error message with 7.0 Release. Message flashes by very quickly every time I upload a new module - have to use a screen recorder to catch and play back slowly.
Get the following when installing a new module using Safari:
An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.MYHOST.ca/drupal/authorize.php?batch=1&render=overlay&id=9&op=do StatusText: ResponseText: ReadyState: 4
Slightly different message when installing a new module using Firefox:
An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.MYHOST.ca/drupal/authorize.php?batch=1&render=overlay&id=10&o... ResponseText: ReadyState: 4
Everything seems to work fine - error display just not a confidence builder. Advice appreciated.
Comment #6
Michsk CreditAttribution: Michsk commentedI also get this error.
Comment #7
jodeygrist CreditAttribution: jodeygrist commentedI also have noticed this error using 7.0 release. Again it doesn't fill me with confidence that everything is working correctly. I don't think I noticed it though before I installed the views module, this might be nothing though, as it may have simply been unnoticed rather than anything specifically related.
Comment #8
glenshewchuck CreditAttribution: glenshewchuck commentedsubscribing
Comment #9
David_Rothstein CreditAttribution: David_Rothstein commentedShould be fixed by the current patch at #936686: "Installation failed" errors when installing modules from Update Manager w/ Overlay. Please help test that - thanks!
Comment #10
Kiorrik CreditAttribution: Kiorrik commentedDownloaded & installed Drupal 7 today and had the same error.
An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.example.com/authorize.php?bath=1&render=overlay&id=4&op=do ResponseText: ReadyState 4
Subscribing.
Comment #11
Honza Pobořil CreditAttribution: Honza Pobořil commentedSame error on different servers.
Comment #12
spessex CreditAttribution: spessex commentedI also get this error.
Comment #13
vikingv CreditAttribution: vikingv commentedTerrible. Drupal was supposed to be better and more stable than this. It is getting worse than its big cousin Joomla.
Comment #14
KingSalibah CreditAttribution: KingSalibah commentedWe should have a "thumbs down" feature for random unhelpful comments such as #13's.
Comment #15
stackpr CreditAttribution: stackpr commentedFor what it's worth, this error can be the result of misconfiguration. I encountered it when I accessed a site on a different domain than that specified by $base_url in settings.php. Although both domains worked fine in most cases, the base_url resulted in a cross-site scripting error in the browser. Updating the base_url to match the domain actually used for administration (and ajax calls) resolved the issue for me. Based on some of the comments (especially #10), this might be what some others are running into as well... Of course, this is a long-closed issue, so I won't worry too much about it...
Comment #16
sachbearbeiter CreditAttribution: sachbearbeiter commented$base_url has to be checked - had the same problem ...
Comment #17
zinkzinkzink CreditAttribution: zinkzinkzink commentedThanks witti (#15), saved me lots of time!! I had $base_url example.com, and a htaccess rewrite to www.example.com. Changing $base_url solved the problem.