- Issue created by @dianacastillo
- π·π΄Romania claudiu.cristea Arad π·π΄
We need more info:
- Which was the value of "value" column from the "key_value" table for "collection" = "system.schema" and "name" = "private_message" before you've started the update?
- Which was the initial module version before you've started the update to 3.0.4?
- πΊπΈUnited States dianacastillo Miami
answer to value from key_value table for collection system.schema name private message -- value is i:8014;
- πΊπΈUnited States dianacastillo Miami
i did a cim before the updb and now i dont get the error. thanks
- πΊπΈUnited States firstlut
Why is this issue marked as fixed? I'm having the same problem.
My prior version is: 8.x-2.0-beta18
Prior system schema version: 8006.Same exact error message.
Thanks!
- πΊπΈUnited States dianacastillo Miami
firstlut because if you run a cim first before the updb the issue is fixed.
- πΊπΈUnited States firstlut
OK, I figured this one out. The entities were deleted, but a couple of View Modes are still hanging around:
core.entity_view_mode.pm_thread_access_time.token
core.entity_view_mode.pm_thread_delete_time.tokenYou have to delete these orphaned config entities with Drush:
drush cdel core.entity_view_mode.pm_thread_access_time.token, core.entity_view_mode.pm_thread_delete_time.token
For reference, here's the Drush manual page.
Changing status back to "Fixed." Automatically closed - issue fixed for 2 weeks with no activity.