Ajax error updating search_api_autocomplete_post_update_sort_dependencies_order.module

Created on 2 August 2025, about 2 months ago

Problem/Motivation

Drupal 10.5.1php 8.3.15 running database update for searchapi autocomplete.
/web/update.php produces errors:

An AJAX HTTP request terminated abnormally.
Debugging information follows.
Path: //web/update.php/start?id=11&op=do_nojs&op=do
StatusText: error
ReadyState: 0

The update process was aborted prematurely while running update # in search_api_autocomplete_post_update_sort_dependencies_order.module

Any advice anyone?

Thx

Steps to reproduce

Proposed resolution

๐Ÿ’ฌ Support request
Status

Active

Version

1.1

Component

Miscellaneous

Created by

๐Ÿ‡ฆ๐Ÿ‡บAustralia CBEEM

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @CBEEM
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia CBEEM

    Update - I can update OK with drush, apparently this has something to do with my local hosting environment, not Drupal and probably not the module.

    Thanks

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia CBEEM

    Ah no,

    The update also failed on the production server. I am not able to run drush on the production server.

    So the same error persists:

    An AJAX HTTP request terminated abnormally.
    Debugging information follows.
    Path: //web/update.php/start?id=11&op=do_nojs&op=do
    StatusText: error
    ReadyState: 0

    The update process was aborted prematurely while running update # in search_api_autocomplete_post_update_sort_dependencies_order.module

    Thx

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia CBEEM

    Update:

    On the third attempt running update.php on the production server the database update succeeded. So I'm all up to date on this server.

    I have no idea why it would fail twice then succeed.

    Cheers

  • ๐Ÿ‡ฆ๐Ÿ‡นAustria drunken monkey Vienna, Austria

    Hi, @cbeem,
    Thanks for reporting this issue and sorry it took me a while to respond.
    Unfortunately, Iโ€™m not sure how to help you here. The update works for me and, apparently, almost everyone else as it has been there without problems for over a year. So, there has to be something very specific about your site that interferes.
    Unless you are able to provide further information by maybe adding debugging statements or using XDebug I donโ€™t think weโ€™ll be able to find out any more here. And since it finally worked, you are probably not really invested anymore, either?

    I see you selected version 1.1 โ€“ was that the version you updated from? In that case, maybe the large step from 1.1 to 1.10 is the problem and it would work (reliably) if youโ€™d first update to some intermediate version, run the updates, maybe re-save the affected entities and only then update to 1.10?

Production build 0.71.5 2024