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.

CommentFileSizeAuthor
#1 ajaxInstallError.png9.51 KBaspilicious
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

aspilicious’s picture

Component: overlay.module » update.module
FileSize
9.51 KB

Maybe this componenent is better...

+ added a screenshot I could make by being fast :)

Bence’s picture

I 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.

aspilicious’s picture

This 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..

Bence’s picture

Ah, sorry, then ignore my post. I copied it to the proper issue :)

mccask’s picture

Getting 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.

Michsk’s picture

I also get this error.

jodeygrist’s picture

I 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.

glenshewchuck’s picture

subscribing

David_Rothstein’s picture

Status: Active » Closed (duplicate)

Should be fixed by the current patch at #936686: "Installation failed" errors when installing modules from Update Manager w/ Overlay. Please help test that - thanks!

Kiorrik’s picture

Downloaded & 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.

Honza Pobořil’s picture

Same error on different servers.

spessex’s picture

I also get this error.

vikingv’s picture

Terrible. Drupal was supposed to be better and more stable than this. It is getting worse than its big cousin Joomla.

KingSalibah’s picture

We should have a "thumbs down" feature for random unhelpful comments such as #13's.

stackpr’s picture

For 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...

sachbearbeiter’s picture

$base_url has to be checked - had the same problem ...

zinkzinkzink’s picture

Thanks 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.