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.
I strumbled on this bug lately:
If a reference field with the autocomplete widget enabled is set as required, it gives a "ReadyState: 0" error in a dialog window. If it's set unrequired, the error does not appear.
I have no knowledge at all about Ajax, but I suppose this should not happen normally.
Comments
Comment #1
Alex Andrascu CreditAttribution: Alex Andrascu commentedI can't replicate this under Ubuntu 12.10 with Chrome and latest dev. Please provide more details (e.g. browser/OS versions)
Thanks.
Comment #2
Tran CreditAttribution: Tran commentedI am getting the same error
An AJAX HTTP request terminated abnormally.
Debugging information follows.
Path: http://mysite.com/taxonomy/autocomplete/field_tag
ResponseText:
ReadyState: 4
Works fine in Firefox.
Not working in Chrome.
Also, it doesn't work when creating the document. It works fine when editing a document.
Comment #3
Tran CreditAttribution: Tran commentedI am getting the same error
An AJAX HTTP request terminated abnormally.
Debugging information follows.
Path: http://mysite.com/taxonomy/autocomplete/field_tag
ResponseText:
ReadyState: 4
Works fine in Firefox.
Not working in Chrome.
Also, it doesn't work when creating the document. It works fine when editing a document.
Also, this began after I updated Drupal Core last week.
Comment #4
jenlamptonI'm also seeing the same problem on our Acquia hosting environment - live site, but not on test, dev, or my local.
I get the following error both when creating a node, and when editing a node.
I also get a similar error in the "Authored by" field on the node so this may not be related to references module:
Comment #5
jenlamptonMy solution: The AJAX urls (see errors above) always started with https instead of http, but the pages I was on were http pages. This presented the problem. I checked settings.php and sure enough, the base_url started with https. Removing the S from base_url meant that AJAX did not try to prefix all its urls with https anymore, and so the error went away.
Not sure if this is the same problem others were having, but hopefully someone finds this hint useful.
Comment #6
zincdesign CreditAttribution: zincdesign commentedI am using secure pages and removing node/add* and node/*/edit from the secure pages solved the issue
Comment #7
manoloka CreditAttribution: manoloka commented#5 sorted it for me
Curiously the error was happening with all users except user 1