PLATFORM
  • Tails

    Create websites with TailwindCSS

  • Blocks

    Design blocks for your website

  • Wave

    Start building the next great SAAS

  • Pines

    Alpine & Tailwind UI Library

  • Auth

    Plug'n Play Authentication for Laravel

  • Designer comingsoon

    Create website designs with AI

  • DevBlog comingsoon

    Blog platform for developers

  • Static

    Build a simple static website

  • SaaS Adventure

    21-day program to build a SAAS

Question By
Unsolved

WAVE 1.0.2 install/migration error

subclass

Aug 3rd, 2020 08:05 PM

I get the following error while installing and migration of WAVE:

In Connection.php line 671:

SQLSTATE[HY000]: General error: 1553 Cannot drop index 'voyager_theme_options_voyager_theme_id_index': needed in a foreign key constraint (SQL: ALTER TABLE theme_options CHANGE voyager_theme_id theme_id INT UNSIGNED NOT NULL)

In PDOStatement.php line 129:

SQLSTATE[HY000]: General error: 1553 Cannot drop index 'voyager_theme_options_voyager_theme_id_index': needed in a foreign key constraint

In PDOStatement.php line 127:

SQLSTATE[HY000]: General error: 1553 Cannot drop index 'voyager_theme_options_voyager_theme_id_index': needed in a foreign key constraint

Any help?

bobbyiliev

Aug 4th, 2020 07:46 AM

Hi there,

I tried to recreate this problem at my end but it seems to be working as expected.

Are you using an existing database? If this is a new installation, I would recommend using a plain new database and as stated in the documentation just running:

composer install
php artisan migrate
php artisan db:seed

Also what is the exact command that you are running?

mrawesomestaco

Aug 8th, 2020 01:26 AM

I've had the same issue. Using Mariadb. The solution is simply to remove the index manually (unless you want to edit the migration files).

mysql -u root -p
use [database];
ALTER TABLE theme_options DROP FOREIGN KEY voyager_theme_options_voyager_theme_id_foreign;
exit

and then run the migrations again and then the seeds.

Report
1
tnylea

Aug 13th, 2020 06:25 PM

This has been updated and fixed in the latest version ;)

Report
1