Twill install failes to complete migrations #855
Replies: 6 comments
-
Check your migration file, you have deleted or comment out the table name. |
Beta Was this translation helpful? Give feedback.
-
I have not touched any of twill files. This results from a fresh composer install followed by twill:install. |
Beta Was this translation helpful? Give feedback.
-
The migrator get the table name from config:
So I believe if you do |
Beta Was this translation helpful? Give feedback.
-
I am sorry but if there is additional steps required after a fresh install of laravel and then a fresh install of latest twill then the documentation is lacking. |
Beta Was this translation helpful? Give feedback.
-
I just encountered this issue. In order to get it working I had to A: Publish spatie/activity_log's service provider, B:Clear my config cache and C: Enter the vendor directory, comment out Twill's version of the activity_log migration and then run php artisan migrate. After that, I uncommented Twill's activity log migration, as it already had a check to see that the table wasn't populated. After that, the install ran. What puzzles me is why Twill is duplicating the migration of a dependency package? |
Beta Was this translation helpful? Give feedback.
-
Hi @radovanobal, could you provide steps to reproduce the issue? Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Running the command
php artisan twill:install
results in an error:Migrating: 2020_02_09_000007_create_twill_default_activity_log_table
Illuminate\Database\QueryException
SQLSTATE[42000]: Syntax error or access violation: 1103 Incorrect table name '' (SQL: create table `` (
id
int unsigned not null auto_increment primary key, `log_name` varchar(255) null, `description` text not null, `subject_id` int null, `subject_type` varchar(255) null, `causer_id` int null, `causer_type` varchar(255) null, `properties` text null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')at vendor/laravel/framework/src/Illuminate/Database/Connection.php:671
667| // If an exception occurs when attempting to run a query, we'll format the error
668| // message to include the bindings with SQL, which will make this exception a
669| // lot more helpful to the developer instead of just the database's errors.
670| catch (Exception $e) {
47 artisan:37
Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
Running in docker environment:
mysql: 5.7
php: 7.4.9
Laravel: 7.27.0
Beta Was this translation helpful? Give feedback.
All reactions