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.
I've upgraded Workflow from 7.x-2.0-beta12 to 7.x-2.3 and I've the following error after running update.php
PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.name' in 'field list': SELECT base.tid AS tid, base.name AS name, base.label AS label, base.sid AS sid, base.target_sid AS target_sid, base.roles AS roles FROM {workflow_transitions} base; Array ( ) in EntityAPIController->query() (regel 187 van /Applications/MAMP/htdocs/www.tdms.be/sites/all/modules/contrib/entity/includes/entity.controller.inc).
When i set the foreach as last in workflow_update_7011() it works.
Comments
Comment #2
johnvThanks, this should be fixed in next version.
The upgrade does a re-save of your workflows. You can do this by hand, too.
Comment #4
yan CreditAttribution: yan commentedSimilar error when I enable the module during the upgrade process from D6 to D7 and before I run the upgrade script (which produces no errors in my case):
The upgrade seems to work, though. (Just that views with workflow options are extremely (!) slow.)
Comment #5
johnv@yan, which version of the entity module are/were you using?
Comment #6
yan CreditAttribution: yan as a volunteer commentedI'm using Entity API 7.x-1.6.
But iirc the error just appears when I enable the module before running update.php.
Comment #7
johnvOK, that's normal behaviour.
Between uploading a newversion of a module and running update.php, the system is in an undetermined state.
Even during running update.php, Drupal puts the site on 'maintenence mode'.
Let's call this 'works as designed', OK?
Comment #8
yan CreditAttribution: yan as a volunteer commentedOk. What's confusing to me is that it seems that some modules need to be enabled before running update.php and others afterwards.