I followed all the instructions for upgrading to D7 from D6. Once I run the update.php script, I get the following error "
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://peoriaparent5:8082/update.php?id=459&op=do StatusText: OK ResponseText: Fatal error: Call to undefined function _update_7000_field_read_fields() in C:\Users\Mahmoud\Sites\peoriaparent5to6\modules\forum\forum.install on line 354
The update process was aborted prematurely while running update #7003 in forum.module.
Has anyone seem something similar ?
THanks
Comment | File | Size | Author |
---|---|---|---|
#18 | forum_upgrade.patch | 747 bytes | catch |
#9 | forum_dependencies.patch | 747 bytes | catch |
#7 | forum_dependencies.patch | 599 bytes | catch |
#5 | forum_dependencies.patch | 602 bytes | catch |
#3 | forum_dependencies.patch | 577 bytes | catch |
Comments
Comment #1
Tor Arne Thune CreditAttribution: Tor Arne Thune commentedJust adding a new title to make it easier to find for others searching for issues detailing the same problem as they have. Also changing to the right component and adding a tag. As this renders a system unusable, the priority is critical.
Comment #2
matmasr CreditAttribution: matmasr commentedOk, I thought of giving out more details. I have site that I am upgrading from Drupal 5 to 7. I went through the upgrade from D5 to D6 sucessfully. I updated my core Drupal to the latest version of D5 and uploaded all the latest versions of contributed modules. Like I said the upgrade from D5 to D6 went relatively smooth.
For the D6 to D7 upgrade, I used the latest stable version of the contributed modules in D7, and the latest D7.4 core. I disabled all the non-core modules, made a backup of my D6 database and files. As I started the update.php script in D7, every works fine until I received that error above which seems to be related to the update path for the forum core module.
I am now reconsidering my upgrade to D7 and may just stick with D6 for a while.
Any thoughts on the cause of this bug ?
Thanks
Comment #3
catchUntested patch, but this might be the problem - it looks like the forum upgrade is running before field module is installed.
Also this might be a duplicate of #717834: The dependencies declared in core's hook_update_dependencies() implementations aren't actually correct (or at least, you might need the patch there as well).
Comment #5
catchComment #7
catchNo wonder it fails, wrong function name :(
Comment #9
catchOK that's the right kind of fail now. Let's try this.
Comment #10
catchComment #12
matmasr CreditAttribution: matmasr commentedIs there any chance this could be resolved. I am now left with either recreating my site from scratch from a fresh D7 installation, or just keep mt site running on D6.
Comment #13
catchHave you tried the patch linked from #3? that needs to go in first and that won't happen without more testing.
Comment #14
matmasr CreditAttribution: matmasr commentedSo should I tried patch # 3 although it failed testing already ?
Comment #15
catchI meant try the latest patch from #717834: The dependencies declared in core's hook_update_dependencies() implementations aren't actually correct, sorry was in a bit of a hurry when I typed that. Even if that patch doesn't work, please report back if you get the same error or a different one.
Comment #16
matmasr CreditAttribution: matmasr commentedI tested the patch above #717834: The dependencies declared in core's hook_update_dependencies() implementations aren't actually correct: The dependencies declared in core's hook_update_dependencies() implementations aren't actually correct.
Then attempted the update again. Got the same error
Comment #17
matmasr CreditAttribution: matmasr commentedHere is some additional error messages at the end of the aborted update
Comment #18
catchLooks like you have more issues with your db than just this. For that filter issue, please see #1211796: Drupal 6 -> 7 upgrade can fail due to unique indexes added in Drupal 6.
I'm uploading a new patch, I can't reproduce the failure you're getting, but this passes automated tests locally (but so does the current code in Drupal 7 so that's no guarantee this will fix your problem).
Comment #19
catchComment #20
matmasr CreditAttribution: matmasr commentedReverted back to the D6 installation. Applied the patch to D7 and reran the installation. This time I got this error.
So at least the fatal error is not occurring in the forum module, but now looks like it in the field module ?
Comment #21
catchtext module updates should not be running during D6-D7, unless you have a 'text' module installed in D6.
Comment #22
matmasr CreditAttribution: matmasr commentedThe text module in D6 is installed as part of the CCK module. Do I need to uninstall the CCK module from D6 before the upgrade ?
Comment #23
catchThat's a good question, opening a new issue for this.
Comment #24
catch#1228488: Drupal 7 text module update (added during beta) runs on sites that have D6 CCK text module installed
Comment #25
sunComment #27
matmasr CreditAttribution: matmasr commented@catch.
I wanted to let you know that I reran the update process all over again from D5 to D6 to D7. This time I has NO fatal errors at all. There were several errors that I can post here later if you are interested, but none were show stoppers.
I looked at my content, and as far as I can tell, the integrity of the data looks good. All stories, pages and custom content show fine ???? Very strange.
Anyway, the only problem is with a custom content that I had that had a custom DATE field is not showing in my calendar view. I am getting a SQL error when the view is displayed. I am not sure if this is realted to an improper update or something else.
I want to know what information you would like me to provide to help diagnose and close this current open issue?
Comment #28
xjmTagging issues not yet using summary template.
Comment #29
David_Rothstein CreditAttribution: David_Rothstein commentedSubscribing.
Comment #30
xjmSince the original poster's issues appear to be resolved, and the particular site appears to have multiple upgrade path issues, downgrading and postponing this for additional reports. If you encounter the error message in the title during an upgrade, please try the following steps and report here whether they resolve the issue and what results you get at each step:
Also, if you encounter the error, set the issue back to needs work if the problem persists, or needs review if any of the steps resolve your issue.
Comment #31
catchHmm I think the patch makes sense whether we get more reports or not, but fine with downgrading if this is the only one we get.
Comment #32
catch#18: forum_upgrade.patch queued for re-testing.
Comment #33
dan_aka_jack CreditAttribution: dan_aka_jack commentedI just attempted to upgrade from Drupal 5.23 to 6.22 to 7.8. The upgrade from 5.23 to 6.22 went fine but the upgrade from 6.22 to 7.8 resulted in the same "Fatal error: Call to undefined function _update_7000_field_read_fields()" mentioned by the original poster above.
I got the upgrade to work by going back to 6.22 and applying the patch in #18 to the 7.8 code and then upgrading to 7.8. All seems well now.
Comment #34
xjm@dan_aka_jack: Thank you for the clear report! Based on that, I think we can consider this RTBC if it still applies. I sent a request for a retest to check.
Edit: #18 still passes, so it is ready to go.
Comment #35
webchickCommitted and pushed to 7.x. Thanks!
Comment #37
thinkyhead CreditAttribution: thinkyhead commentedI had been encountering this with the "text" module instead of the "forum" module, so I got the latest 7.x-dev. Now it's crapping out on "image." --- Could this be another one of the cases, like "text" and "forum" that was not accounted for, and hasn't been included in the patch yet?
Sorry if changing the status here is unwarranted. But I think we need another look.
Comment #38
xjm#37: I'd suggest looking for an existing issue with your exact error message, or if one doesn't exist yet, you can open a new one. Thanks!
Comment #39
thinkyhead CreditAttribution: thinkyhead commentedIt's this issue. The modules that must state a dependency on 'system' update 7020 are: forum, text, and image. As far as I can tell that closes it.
Comment #40
mstrelan CreditAttribution: mstrelan commentedThe following code fixes the issue in #37.
and
Comment #41
xjmAgain, please search for an open issue or open a new one if you have this problem in 7.12 or later. Thanks!