creativetimofficial / ct-material-dashboard-pro-laravel

Material Pro Dashboard For Laravel Framework 11.x and Up
https://www.creative-tim.com/live/material-dashboard-pro-laravel
19 stars 6 forks source link

Installation Error #43

Closed cyberautomate closed 1 year ago

cyberautomate commented 1 year ago

Current Behavior

I get the attached database error when running the migrations via php artisan migrate --seed image

Failure Information (for bugs)

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

  1. step 1
  2. step 2
  3. you get it...

Context

I tried resetting the migrations and got the same result. I also deleted and re-created the database and get the same error.

Failure Logs

Please include any relevant log snippets or files here.

teamupdivision commented 1 year ago

Hello,

Thank you for using Creative TIM products!

You could try the "php artisan migrate:fresh --seed" command, but please keep in mind that it will reset your data base and it will add the data from seeding.

If this does not work, could you please give us more details? Did you make sure to follow all the steps or did you make any changes to the project?

Thank you.

cyberautomate commented 1 year ago

I followed the install instructions listed here: https://github.com/creativetimofficial/ct-material-dashboard-pro-laravel#installation

I re-created a new database, I'm using a brand new installation of Laravel (Laravel new site), nothing else has been add other than the template files.

Run php artisan migrate: fresh --seed and get the following error image

These tables are created when the migration runs. Just have no users, all the tables are empty. image

teamupdivision commented 1 year ago

Hello,

From what we can see you have Laravel breeze and not Laravel, could you install Laravel and let us if the issue still persists?

Thank you.

cyberautomate commented 1 year ago

You're correct, that was my fault. I was copying the contents of the template into a baseline Laravel project. Worked fine when I did it correctly. Sorry for the confusion and thank you for the support