DarkGhostHunter / Laraconfig

Per-user settings repository system for Laravel
MIT License
173 stars 49 forks source link

php artisan settings:migrate command not working #21

Open lukas-pierce opened 3 years ago

lukas-pierce commented 3 years ago

php artisan settings:migrate command not working

Cannot declare class App\Models\AnyModel, because the name is already in use

I tried remove this model, and this issue occurs again on next model in alphabetical order looks like it swears at any model

DarkGhostHunter commented 3 years ago

Did you dump your autoload?

Laraguard doesn't uses require to pick up the models, it just infers them using PSR-4. The only require used is from the settings.php.

The stack trace should give you all the details.

lukas-pierce commented 3 years ago

Yes, I regenerated autoload file

composer dump-autoload

Sorry cannot show stack trace because removed your package from project, but I discovered sources and take the your models, chic architecture.

lukebouch commented 3 years ago

I'm having the same problem.

php artisan settings:migrate

   Symfony\Component\ErrorHandler\Error\FatalError

  Cannot declare class App\Models\User, because the name is already in use

  at app/Models/User.php:15
     11▕ use Silber\Bouncer\BouncerFacade;
     12▕ use Silber\Bouncer\Database\HasRolesAndAbilities;
     13▕ use Silber\Bouncer\Database\Role;
     14▕
  ➜  15▕ class User extends Authenticatable
     16▕ {
     17▕     use HasFactory, Notifiable, HasRolesAndAbilities;
     18▕
     19▕     /**

   Whoops\Exception\ErrorException

  Cannot declare class App\Models\User, because the name is already in use

  at app/Models/User.php:15
     11▕ use Silber\Bouncer\BouncerFacade;
     12▕ use Silber\Bouncer\Database\HasRolesAndAbilities;
     13▕ use Silber\Bouncer\Database\Role;
     14▕
  ➜  15▕ class User extends Authenticatable
     16▕ {
     17▕     use HasFactory, Notifiable, HasRolesAndAbilities;
     18▕
     19▕     /**

      +1 vendor frames
  2   [internal]:0
      Whoops\Run::handleShutdown()
eafarooqi commented 3 years ago

i also have the same issue, but only on Linux, on windows, i don't have this issue. still no fix to this issue?

eafarooqi commented 3 years ago

This is what i get in the log file

[2021-09-27 20:50:32] staging.ERROR: Cannot declare class App\Models\Administration\Region, because the name is already in use {"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Cannot declare class App\\Models\\Administration\\Region, because the name is already in use at /var/www/twap/app/Models/Administration/Region.php:10)
[stacktrace]
#0 {main}
"} 
illusive-ch commented 3 years ago

Same issue here @DarkGhostHunter

DarkGhostHunter commented 3 years ago

Hands full and overtime guys, you will have to sit this one out.

eafarooqi commented 2 years ago

@DarkGhostHunter #26 Please merge, this should fix the issue.

ricventu commented 2 years ago

Same issue here, with traits

renepardon commented 2 years ago

I have the same problem with my User model:

PHP Fatal error:  Cannot declare trait App\Models\Traits\Encryptable, because the name is already in use in /var/www/html/app/Models/Traits/Encryptable.php on line 9

   Symfony\Component\ErrorHandler\Error\FatalError

  Cannot declare trait App\Models\Traits\Encryptable, because the name is already in use

  at app/Models/Traits/Encryptable.php:9
      5▕ use Illuminate\Contracts\Encryption\DecryptException;
      6▕ use Illuminate\Contracts\Encryption\EncryptException;
      7▕ use Illuminate\Support\Facades\Crypt;
      8▕
  ➜   9▕ trait Encryptable
     10▕ {

My user model looks like that:

class User extends Authenticatable implements MustVerifyEmail
{
    use HasApiTokens;
    use HasFactory;
    use HasProfilePhoto;
    use Notifiable;
    use TwoFactorAuthenticatable;
    use HasRoles;
    use HasConfig;

So I dont even use the Encryptable trait on the user model itself and it's really only declared once in my application. I called artisan optimize and composer dump-autoload without success

renepardon commented 2 years ago

Is there maybe an alternative to use the settings without "migration" command in the meantime?

ricventu commented 2 years ago

Are you updated with latest master?

this commit must fix that

renepardon commented 2 years ago

Are you updated with latest master?

this commit must fix that

I usually don't install master or dev versions in production code. The latest available version 1.3.5 is 6 months old. Therefore I guess I need to wait for the next version ;)