There is uncaught error with empty responsetext in modal popup window with response 200

ajax.js?v=8.6.15:500 Uncaught Drupal.AjaxError {message: "↵An AJAX HTTP error occurred.↵HTTP Result Code: 20…form/↵StatusText: OK↵ResponseText: ", name: "AjaxError"}

Comments

meshweta created an issue. See original summary.

meshweta’s picture

meshweta’s picture

meshweta’s picture

Category: Feature request » Bug report
meshweta’s picture

Issue summary: View changes
StatusFileSize
new728 bytes
cilefen’s picture

Status: Active » Needs review
Issue tags: +JavaScript
meshweta’s picture

StatusFileSize
new733 bytes
meshweta’s picture

StatusFileSize
new738 bytes
akalata’s picture

Version: 8.6.x-dev » 8.8.x-dev

I'm also encountering a case where my AJAX request is returning an `AjaxError` message, even through my custom functionality completes successfully and the `XHR` response = 200.

However, I'm more willing to bet that there's something wrong with how I'm implementing the Ajax call, since the exact same code triggered slightly differently does not produce an error:

  1. What is working: Clicking a control to trigger the AJAX callback while remaining on the same page.
  2. What is working but gives me an `AjaxError`: Clicking a link, which triggers the AJAX callback as an `onClick()` reaction, and then proceeding to the original link's href.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

deepika dhiman’s picture

Issue tags: -JavaScript +JavaScript
StatusFileSize
new738 bytes

Hi,

Here is the patch for Drupal 9.2.2.

Thanks

gauravvvv’s picture

StatusFileSize
new1.23 KB

Re-rolled patch #14, Please review.

gauravvvv’s picture

StatusFileSize
new1.23 KB

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

needs-review-queue-bot’s picture

Status: Needs review » Needs work
StatusFileSize
new144 bytes

The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

gauravvvv’s picture

StatusFileSize
new577 bytes

Re-rolled patch for 10.1.x. Please review

gauravvvv’s picture

Status: Needs work » Needs review
smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs tests, +Needs issue summary update

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

As a bug this will need a test case.
Also the issue summary needs to be updated with steps to reproduce, proposed solution, etc. Please use default template.

jimconte’s picture

The patch for 10.1.x applies to 9.5.7

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.