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.
currently a workaround is needed to go from entityqueue 1.0-beta5 to version 1.0
There is not a super friendly upgrade path currently but one that requires attention to details and caution, a patch and a manual step or two.
Not super difficult be not super easy either.
For background info:
#3130960: entityqueue dependency 1.0 or 1.0-rc1 fails updb
Comments
Comment #2
joseph.olstadHaven't fully tested this upgrade path yet.
Affects those that come from installs of wxt 3.0.8 or previous versions when entityqueue 1.0-beta5 was current (installations done prior to April 15th 2020)
Comment #3
sylus CreditAttribution: sylus commentedI applied the patch and made note of the manual notes in our changelog.
Hoping this should provide a viable path for anyone hitting these issues! :)
https://github.com/drupalwxt/wxt/commit/4d2d909b5732f1746773f2850651391b...
Comment #4
sylus CreditAttribution: sylus commentedComment #5
joseph.olstad*edit*, off topic, my mistake
Comment #6
joseph.olstadupdb still does this
Comment #7
joseph.olstadOk this fix is good but with an asterisk.
there is a trick to this.
The patch works however ONLY if you pin entityqueue on 1.0-beta5 , with entityqueue pinned on 1.0-beta5 the lightning_workflow patch does it's thing the hook update corrects the data in the schema.
Once you do this, then go to the workflow and save the 'editorial' workflow, this rids us of the reports status warning , fixes that glitch too.
however if you try to upgrade entityqueue with the fix for lightning_workflow entityqueue will crash because it runs first , entityqueue has a lighter weight and runs first.
so the trick to this is to upgrade everything EXCEPT entityqueue (pinning it to 1.0-beta5) and once the update.php / drush updb has run for lightning_workflow THEN you can upgrade entityqueue to 1.0
again, it's a module weight thing.
entityqueue has a lighter weight ('e' is before 'l' in the alphabet)
Comment #8
sylus CreditAttribution: sylus commentedAh I gotcha now ok will try to get this properly fixed in next release. :)
Comment #9
joseph.olstadstill having issues with this
Comment #10
joseph.olstadissues resolved, last one was a restore to a previous sql dump file that missed a few steps.
For those that see warnings, edit the editorial workflow and press save, no need to change anything except press save.
Should be good now
Thanks for assistance and quick response for this, we're fully up-to-date with wxt and entityqueue.
Comment #11
joseph.olstadComment #12
joseph.olstad