Originally reported here:
https://groups.drupal.org/node/398383#comment-1004753
I did what you said David, but as I had already upgraded drupal core to 7.26, I only copied the profiles folder and crossed my fingers. Initial findings are that it seems to have worked. The only thing though is that when I ran the update script I got the following error:
1 PENDING UPDATE (0 TO BE APPLIED, 1 SKIPPED)
panopoly_users module7001 - Enable user_picture_field and copy from field_user_picture to users.picture.
This update will been skipped due to the following missing dependencies: fieldable_panel_panes_update_7107I think I tracked this down to panopoly_users.install and line 17
'fieldable_panel_panes' => 7107,
an 's' seems to have been missed out:
'fieldable_panels_panes' => 7107,
That seems to sort it.
I'm pretty sure this is my fault, from one of the upgrade test issues:
#2164193: Upgrade from 1.0-rc5 fails: Table 'pathauto_state' doesn't exist
#2172093: Upgrade from 1.0-rc3 or 1.0-rc2 fails: Table 'cache_entity_fieldable_panels_pane' doesn't exist
#2164187: Upgrade from 1.0-rc4 fails: Table 'cache_search_api_solr' doesn't exist
I'll try the fix described and hope the upgrade tests still work!
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | panopoly_users-update-2175729-1.patch | 628 bytes | dsnopek |
Comments
Comment #1
dsnopekPatch is attached!
Comment #2
dsnopekSent to Travis-CI for testing, because that's the easiest way I know to run the upgrade tests:
https://travis-ci.org/lsolesen/panopoly/builds/17127879
If they pass, I'll commit it!
Comment #3
PedroKTFC commentedJust noticed that the drupal formatter has changed what I wrote a little! In case you did literally what was posted, what it should have said was (with minimal formatting, asterixes just so you see where easily):
Instead of
fieldable_panel_panes' => 7107,
it should be
fieldable_panel**s**_panes' => 7107,
Comment #4
dsnopekHrm. It looks like applying the patch the way I tried didn't work - build-panopoly-dev.make isn't affected by it. :-/ I'll either need to change the way the tests are run on Travis-CI, or just commit the patch and open a new issue if it fails.
Comment #5
dsnopek@PedroKTFC: I've updated the issue body to be correct! But I knew what you meant anyway. :-)
Comment #6
dsnopekMarking as critical and sprint because I really think this has to go in before we do a 1.1 release.
Comment #7
dsnopekAfter #2182927: Travis-CI should use drupal-org-core.make / drupal-org.make directly, the patch should actually get tested on Travis-CI. The build has started here:
https://travis-ci.org/lsolesen/panopoly/builds/17721863
Assuming this time it actually patches it AND all the update tests pass, then I'll commit it.
Comment #8
dsnopekAll the update tests have passed, so I've (finally) committed this.