Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compatibility with twill CMS error SQLSTATE[42S01] #4

Open
c-nv-s opened this issue May 12, 2020 · 0 comments
Open

compatibility with twill CMS error SQLSTATE[42S01] #4

c-nv-s opened this issue May 12, 2020 · 0 comments

Comments

@c-nv-s
Copy link

c-nv-s commented May 12, 2020

Hello Vicktor,

I've been trying to get admin-one to install alongside twill cms but it seems there is a mysql error or table conflict regardless of which is installed first.

system
AMD64 - ubuntu 18.04
laravel 7
PHP 7.2.24-0ubuntu0.18.04.4
mysql Ver 15.1 Distrib 10.4.12-MariaDB

Steps to reproduce
If installing twill cms first:

composer create-project laravel/laravel myproject
cd myproject
composer require area17/twill:"^2.0"
php artisan twill:install
php artisan serve
--- login to working CMS ---
--- ctrl ^c - stop dev server ---
composer require vikdiesel/admin-one-laravel-dashboard --dev
composer require laravel/ui
php artisan ui:controllers
php artisan jb:admin-one-preset
php artisan migrate

Migrating: 2019_06_19_104931_create_files_table                    
                                                                                  
   Illuminate\Database\QueryException                            
                                                                                
  SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'files' already exists (SQL: create table `files` (`id` bigint unsigned not null auto_increment primary key, `file`
 varchar(255) not null, `name` varchar(255) null, `mime` varchar(255) null, `size` bigint unsigned 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) {
  > 671|             throw new QueryException(
    672|                 $query, $this->prepareBindings($bindings), $e
    673|             );
    674|         }
    675| 

      +11 vendor frames 
  12  database/migrations/2019_06_19_104931_create_files_table.php:23
      Illuminate\Support\Facades\Facade::__callStatic("create")

      +22 vendor frames 
  35  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))



conversely if admin-one is installed first and is in working order, the subsequent installation of twill CMS displays the following mysql error in the CMS after logging in:

Facade\Ignition\Exceptions\ViewException
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'files.deleted_at' in 'where clause' (SQL: select count(*) as aggregate from `files` where `files`.`deleted_at` is null) (View: /home/ubuntu/bulma/vendor/area17/twill/views/layouts/main.blade.php) 


happy offer my time and resources to make this work if you can help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant