super-table: Craft 3.1 Migration Failure: m190120_000000_fix_supertablecontent_tables

Description

Got the following error when updating Super Table:

Exception: Unable to save a Super Table field’s settings without knowing its content table.

Migration: verbb\supertable\migrations\m190120_000000_fix_supertablecontent_tables

Output:

> update in {{%fields}} ... done (time: 0.002s)
Exception: Unable to save a Super Table field’s settings without knowing its content table. (/vagrant/vendor/verbb/super-table/src/services/SuperTableService.php:566)
#0 /vagrant/vendor/verbb/super-table/src/migrations/m190120_000000_fix_supertablecontent_tables.php(118): verbb\supertable\services\SuperTableService->saveSettings(Object(verbb\supertable\fields\SuperTableField))
#1 /vagrant/vendor/verbb/super-table/src/migrations/m190120_000000_fix_supertablecontent_tables.php(93): verbb\supertable\migrations\m190120_000000_fix_supertablecontent_tables->_updateMatrixOrSuperTableSettings(Object(verbb\supertable\fields\SuperTableField))
#2 /vagrant/vendor/craftcms/cms/src/db/Migration.php(56): verbb\supertable\migrations\m190120_000000_fix_supertablecontent_tables->safeUp()
#3 /vagrant/vendor/craftcms/cms/src/db/MigrationManager.php(243): craft\db\Migration->up(true)
#4 /vagrant/vendor/craftcms/cms/src/db/MigrationManager.php(163): craft\db\MigrationManager->migrateUp(Object(verbb\supertable\migrations\m190120_000000_fix_supertablecontent_tables))
#5 /vagrant/vendor/craftcms/cms/src/services/Updates.php(223): craft\db\MigrationManager->up()
#6 /vagrant/vendor/craftcms/cms/src/controllers/BaseUpdaterController.php(445): craft\services\Updates->runMigrations(Array)
#7 /vagrant/vendor/craftcms/cms/src/controllers/UpdaterController.php(208): craft\controllers\BaseUpdaterController->runMigrations(Array, 'restore-db')
#8 [internal function]: craft\controllers\UpdaterController->actionMigrate()
#9 /vagrant/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array)
#10 /vagrant/vendor/yiisoft/yii2/base/Controller.php(157): yii\base\InlineAction->runWithParams(Array)
#11 /vagrant/vendor/craftcms/cms/src/web/Controller.php(109): yii\base\Controller->runAction('migrate', Array)
#12 /vagrant/vendor/yiisoft/yii2/base/Module.php(528): craft\web\Controller->runAction('migrate', Array)
#13 /vagrant/vendor/craftcms/cms/src/web/Application.php(297): yii\base\Module->runAction('updater/migrate', Array)
#14 /vagrant/vendor/craftcms/cms/src/web/Application.php(683): craft\web\Application->runAction('updater/migrate')
#15 /vagrant/vendor/craftcms/cms/src/web/Application.php(243): craft\web\Application->_processUpdateLogic(Object(craft\web\Request))
#16 /vagrant/vendor/yiisoft/yii2/base/Application.php(386): craft\web\Application->handleRequest(Object(craft\web\Request))
#17 /vagrant/web/index.php(43): yii\base\Application->run()
#18 {main}

After navigating back to the updates page, was met with an un-finished updates message, proceeded through and confirmed the ‘someone else might be updating’ message, and got back to the CP successfully. No idea if the migrations successfully ran or if there’s now hidden gremlins lurking.

Steps to reproduce

1. Run Craft 3.1 update including all updates released as of 2018-01-21
2. Run Super Table 2.1.4.2 update

Additional info

• Plugin version: Updating to 2.1.4.2
• Craft version: 3.1.2.2