You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Exec] Running ./vendor/bin/drush updatedb -y
------------------- ----------- ------------- ------------------------------
Module Update ID Type Description
------------------- ----------- ------------- ------------------------------
oe_media_webtools 00002 post-update Install OP Publication List
media type.
oe_theme_helper 20015 post-update Create oe_theme_main_content
view mode for Iframe media.
------------------- ----------- ------------- ------------------------------
// Do you wish to run the specified pending updates?: yes.
> [notice] Update started: oe_media_webtools_post_update_00002
> [error] Attempt to create a field oe_media_webtools that does not exist on entity type media.
> [error] Update failed: oe_media_webtools_post_update_00002
[error] Update aborted by: oe_media_webtools_post_update_00002
[error] Finished performing updates.
[Exec] Exit code 1 Time 11.517s
[Exec] Exit code 1 Time 15.164s
The text was updated successfully, but these errors were encountered:
I don't think this should be closed.
The post update hook should consider cases where developers have removed field storage definitions after initial install, and either provide more relevant error reporting or ignore?
Not sure what this is really trying to accomplish.
I found a similar problem with oe_media_iframe_post_update_00005(), on a site where the oe_media_iframe_thumbnail field did no longer exist - possibly removed by a developer who did not think it necessary to have. (our project git history does not tell, unfortunately).
The text was updated successfully, but these errors were encountered: