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.
AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://domain.com/update.php?op=selection&token=ZAIU0XaQOZmKWryS07qxMSi2... StatusText: parsererror ResponseText: Fatal error: Call to undefined function apachesolr_load_all_environments() in /var/aegir/platforms/D7/sites/all/modules/apachesolr/apachesolr_search.install on line 379
Comment | File | Size | Author |
---|---|---|---|
#8 | apachesolr-1835208-fatal_undefined_apachesolr_load_all_environments.patch | 624 bytes | xurizaemon |
Comments
Comment #1
webmaster-eddie CreditAttribution: webmaster-eddie commentedDB update failing is 7006
Comment #2
webmaster-eddie CreditAttribution: webmaster-eddie commentedUpdating to dev version does not help, but produces another update 7016 which also fails, so because of apachesolr, i now have 4 db updates failing:
7006 - apachesolr search module
7016 - apachesolr module
7077 - system module
7003 - aggregrator module
Any tips on how to get these other db schema updates to work without uninstalling apachesolr from the platform / site?
Comment #3
webmaster-eddie CreditAttribution: webmaster-eddie commentedsame problem with dev version
Comment #4
Nick_vhapachesolr_load_all_environments is a normal function in apachesolr.module. I wonder if something broke in latest drupal?
Can you, to test add an module_load_include() function in the update function?
Thanks
Comment #5
webmaster-eddie CreditAttribution: webmaster-eddie commentedUPDATE
I had the apachesolr modules installed but not activated. Activating them allowed the dB schema updates to work. Sorry about this, but it shouldn't really matter whether or not a module is enabled as to whether or not it prevents other core modules from updating db schema properly?
Comment #6
Nick_vhapachesolr_search depends on apachesolr. If you somehow broke your system table, that is not the responsibility of this module. It seems something broke in your install and I don't think these modules can do anything about that.
I am going to close this issue unless you think you can provide a fix. I hope that is ok?
Comment #7
xurizaemonThis error occurs if a site is upgraded from D6 to D7 with ApacheSolr disabled as per Drupal 7 Upgrade process.
I suspect Eddie didn't break his system table, he was just following the upgrade docs.
To repro:
1. put system in state where apachesolr_update_7006 is going to run (eg upgrade to D7)
2. disable apachesolr
3. run drush updb
Updates for disabled modules are run during update-db. This confused me at first but it does make sense.
Comment #8
xurizaemonpatch
Comment #9
travelerttWorked for me! Thanks
Comment #10
Nick_vhThanks! Committed