After upgrades completed successfully I went thru and reset modules and themes to convert d6 site to d7. This all went OK.
I deleted the PM modules and storm module directories and then, using terminal I then did a "git clone --branch 7.x-1.x http://git.drupal.org/project/pm.git", and out of habit, a "git hard reset", and then a "git pul origin". These all completed OK.
I then went to rebuild permissions ... at which point it fails and throws this error message...
An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /re6/?q=batch&id=11&op=do StatusText: Internal Server Error ResponseText: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 're6.pminvoice_items' doesn't exist: SELECT pmini.* FROM {pminvoice_items} pmini WHERE (invoice_vid = :db_condition_placeholder_0) ORDER BY weight ASC; Array ( [:db_condition_placeholder_0] => 40 ) in pminvoice_load() (line 847 of /media/sf_sandbox/re6/sites/all/modules/pm/pminvoice/pminvoice.module).
Comment | File | Size | Author |
---|---|---|---|
#3 | stormmigrate-invoiceitems.patch | 1.06 KB | juliangb |
Comments
Comment #1
dbt102 CreditAttribution: dbt102 commentedSince the error msg specified the problem to be in pminvoice, I disabled that module (admin/modules) and THEN rebuilt permissions. This allowed for the content access permissions to be rebuilt successfully.
I then went back and enabled the pminvoice module again and rebuilt permissions again. This resulted in same error msg.
So I disabled the pminvoice module again and rebuilt permissions again (which completed OK).
Comment #2
dbt102 CreditAttribution: dbt102 commentedfyi...
I didn't mention in original post that the reason I tried the 'git clone' was because I noticed that in "note" nodes, the description field was missing. I thought this issue had been fixed several patches (weeks) ago so wanted to see if updating to most current git branch would work OK. On checking "note" now, after git pull and rebuilding permissions, the notes description field shows up just fine.
Comment #3
juliangb CreditAttribution: juliangb commentedThis is an issue in the migration path.
The attached patch is against the storm migrate module.
To test, you can either run the full upgrade again, or just reenable the storm migrate module and run update.php.