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

joseph.olstad created an issue. See original summary.

joseph.olstad’s picture

Haven'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)

sylus’s picture

Category: Plan » Bug report
Status: Active » Reviewed & tested by the community

I 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...

sylus’s picture

Status: Reviewed & tested by the community » Fixed
joseph.olstad’s picture

*edit*, off topic, my mistake

joseph.olstad’s picture

Status: Fixed » Active
>  [notice] Update started: entityqueue_update_8004
>  [notice] The publishing status field has been added to Entity Subqueues.
>  [notice] Update completed: entityqueue_update_8004
>  [notice] Update started: lightning_layout_update_8012
>  [notice] Update completed: lightning_layout_update_8012
>  [notice] Update started: entityqueue_update_8005
>  [notice] The revision metadata fields have been added to Entity Subqueues.
>  [notice] Update completed: entityqueue_update_8005
>  [notice] Update started: lightning_layout_update_8013
>  [notice] Update completed: lightning_layout_update_8013
>  [notice] Update started: entityqueue_post_update_make_entity_subqueue_revisionable_and_translatable
>  [error]  Exception thrown while performing a schema update. SQLSTATE[42S02]: Base table or view not found: 1146 Table 'c1agqa.entity_subqueue__scheduled_transition_date' doesn't exist: SELECT t.*
> FROM
> {entity_subqueue__scheduled_transition_date} t
> WHERE (entity_id IN (:db_condition_placeholder_0)) AND (deleted = :db_condition_placeholder_1) AND (langcode IN (:db_condition_placeholder_2, :db_condition_placeholder_3, :db_condition_placeholder_4, :db_condition_placeholder_5))
> ORDER BY delta ASC; Array
> (
>     [:db_condition_placeholder_0] => front_page
>     [:db_condition_placeholder_1] => 0
>     [:db_condition_placeholder_2] => en
>     [:db_condition_placeholder_3] => fr
>     [:db_condition_placeholder_4] => und
>     [:db_condition_placeholder_5] => zxx
> )
>  
>  [error]  Update failed: entityqueue_post_update_make_entity_subqueue_revisionable_and_translatable 
 [error]  Update aborted by: entityqueue_post_update_make_entity_subqueue_revisionable_and_translatable 

updb still does this

joseph.olstad’s picture

Ok 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)

sylus’s picture

Ah I gotcha now ok will try to get this properly fixed in next release. :)

joseph.olstad’s picture

still having issues with this

Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'media__scheduled_transition_date' doesn't exist: SELECT t.* FROM {media__scheduled_transition_date} t WHERE (entity_id IN (:db_condition_placeholder_0)) AND (deleted = :db_condition_placeholder_1) AND (langcode IN (:db_condition_placeholder_2, :db_condition_placeholder_3, :db_condition_placeholder_4, :db_condition_placeholder_5)) ORDER BY delta ASC; Array ( [:db_condition_placeholder_0] => 7 [:db_condition_placeholder_1] => 0 [:db_condition_placeholder_2] => en [:db_condition_placeholder_3] => fr [:db_condition_placeholder_4] => und [:db_condition_placeholder_5] => zxx ) in Drupal\Core\Entity\Sql\SqlContentEntityStorage->loadFromDedicatedTables() (line 1261 of 
/docroot/html/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).
joseph.olstad’s picture

issues 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.

joseph.olstad’s picture

Status: Active » Fixed
joseph.olstad’s picture

Assigned: joseph.olstad » Unassigned

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.