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.
Banging my head . . .
I have the user profile displaying in a colorbox.
In Chrome, I always receive the error
AJAX HTML request terminated abnormally. Debugging information follows.
Path: colorbox/user/no?width=800&height=500
Status text:
Response text:
Ready state: 4
It happens intermittently in Firefox, IE 10, and Safari.
How do I diagnose an Ajax error?
Comments
Comment #1
iLLin CreditAttribution: iLLin commentedChange themes to a basic theme like garland and see if the problem persists. Then go from there. Start turning stuff off until you find out the problem.
Comment #2
mastoll CreditAttribution: mastoll commentedThis AJAX termination problem does not happen in the latest production release, 7.x-3.2.
I had switched to the dev version because I wanted to remove the arrows and page-count in the bottom left corner of the modal. If I have to choose between page count and AJAX error, I suppose I prefer the page count. But if you could point me to the lines of code in the dev version that relate to the arrows, I will patch my production version and have the best of both! :)
Thanks!
Comment #3
mastoll CreditAttribution: mastoll commentedYou're fast, iLLin, thanks for #1 which came in while I was typing #3! Regarding the suggestion to change to basic theme etc., do you mean to start turning modules off to look for inter-module conflict? Should I be looking for stuff that uses AJAX specifically?
By the way, the user profiles display without errors outside the colorbox.
Comment #4
iLLin CreditAttribution: iLLin commentedHmm, ill try to figure that out. There is a newer patch here #2120319: rel='nofollow' build up a gallery. Try that one out and let me know.
Comment #5
iLLin CreditAttribution: iLLin commentedNo, just change your theme to garland. that will take out any custom js, html... etc.
Comment #6
mastoll CreditAttribution: mastoll commentedHave changed my theme to Garland but the problem persists. And, it does happen in the production release after all.
It is most prevalent in Chrome. In fact, I cannot make it happen in Firefox, although others have seen it there.
Remember, I am trying to display user profiles in the CB modal.
In Chrome, I am able to detect the error
XMLHttpRequest cannot load. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://arizonawet.arizona.edu' is therefore not allowed access.
This would point to a cross-site request, and yet I cannot see where two different sites are involved, or even two variations on the current domain name.
What should I do next?
Comment #7
iLLin CreditAttribution: iLLin commentedYou have a link?
Comment #8
iLLin CreditAttribution: iLLin commented