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.
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.Top Drupal contributor Acquia would like to thank their partners for their contributions to Drupal.
Drupal is a registered trademark of Dries Buytaert.
Comments
Comment #1
drunken monkeyShould be fixed.
The API of this module should not have changed, but note that you'll have to run update.php immediately after updating to circumvent a fatal error when clearing the cache (in the Facets module).
Note also that now the current dev version will only work with Entity API's latest dev version.
Comment #2
Shadlington CreditAttribution: Shadlington commentedError after attempting to run update.php:
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /update.php?id=4&op=do StatusText: OK ResponseText: 4{"status":true,"percentage":"100","message":"Completed 1 of 1.\u003cbr \/\u003eUpdating search_api module"}
Comment #3
drunken monkey1) Damn!
2) If I'm reading the message correctly, the error consists of everything going perfectly well? Seems a little eccentric to me …
Are there other problems after this, or does everything work afterwards?
Comment #4
drunken monkeyComment #5
Shadlington CreditAttribution: Shadlington commentedI was having other problems but I didn't trust my install (it had become a bit cluttered).
Tried it just now with a clean install and I still get that error during the update, but I don't appear to hit any further problems.
Comment #6
drunken monkeyIf there really is a "4" in front of the response text, that could of course be the problem, since it would make the JSON invalid.
Of course, I'd still have no idea why there's suddenly a "4" output. As anyone can see, my update function has just a single line, and I just checked that the .install file also has no leading 4 for some reason, either.
Anyone else with this problem?
Otherwise, maybe you have some other module installed whose .install file has a leading "4"? Did other update scripts run successfully?
Comment #7
Shadlington CreditAttribution: Shadlington commented...Huh.
There's a random 4 in my update.php.
I am an idiot - I had edited update.php to prevent a nasty bug that has been corrected in the current 7.3-dev of core but I must have screwed it up. Also, I must have screwed it up a while ago on my backup of a clean install that I have been restoring when I need to test something.
Really sorry about wasting your time like this - it does work!