V3 Class "Filament\PanelProvider" not found

[jcgmalave]

I get the following error during the update process:

In AdminPanelProvider.php line 22:

Class "Filament\PanelProvider" not found

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

[mondherid]

add AdminPanelProvider to list of providers in config/app.php ('providers'=[......... ,' AdminPanelProvider::class'])
it is not montioned in the documentation

[jcgmalave]

HI, how are you? i was able to install the latest beta version, but now im getting this related to taiwind:

i get the following error trying to upgrade v3:

[vite:css] C:\xampp\htdocs\modatex-chile-tres\resources\css\app.css:4:1: 'colors.gray.950 / 5%' does not exist in your theme config. 'colors.gray' has the following valid keys: '50', '100', '200', '300', '400', '500', '600', '700', '800', '900'

Any ideas?

thanks in advanced

[emjay64]

@jcgmalave I am facing the same issue:

In AdminPanelProvider.php line 22:
  Class "Filament\PanelProvider" not found 

did you get this resolved?

[danharrin]

What is your Filament version, check with php artisan about

[emjay64]

Version ........................................................................................................................... v3.0.0-alpha67

[danharrin]

composer require filament/filament:"^3.0-stable" -W

[JayrousJr]

I too get the same error

In AdminPanelProvider.php line 22:

Class "Filament\PanelProvider" not found

[danharrin]

You have the wrong version installed then

[Wan237]

Have you solved this problem?it cost me a day already!

[leandrocfe]

Are you updating it?

[Jigsaw5279]

I'm having the same issue on a fresh install of both Laravel 10 and Filament, copying commands from the docs.

The classes just don't exist.

[Jigsaw5279]

Funny enough, artisan about still reports the same stats about Filament after running that command

[danharrin]

I've just seen the problem. You didn't actually install Filament panel builder. You just installed all the other packages. That class is part of the panel builder. You were on the correct version.

[Jigsaw5279]

Maybe adding a check if the PanelProvider exists in the install command would help?

[danharrin]

Good idea, please PR it :)

[Jigsaw5279]

Done #7673

[Nes-cmd]

I have also encountered this error. It happened after upgrading process was finished. Then I deleted the vendor folder then run composer update It worked.

[Wan237]

Problem solved, thanks for replying.

…

On Fri, Feb 23, 2024 at 5:38 PM Leandro Costa Ferreira < ***@***.***> wrote: Are you updating it? — Reply to this email directly, view it on GitHub <#7213 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYLVIFOQFZU4G4YZD6C2LA3YVFAC5AVCNFSM6AAAAAA2X4HW2KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKNZUGE4TM> . You are receiving this because you commented.Message ID: ***@***.***>

[Quantumben]

To fix this error run "composer require filament/filament:"^3.0-stable" --ignore-platform-reqs --with-all-dependencies"

[Erickhrs]

Guys, I resolved it by following these steps on a shared host (Hostinger):

1. Zip all my Laravel files (with Filament) and upload them to the host directory.
2. Update the database information in the .env file.
3. Add the .htaccess file:

RewriteEngine On

# Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Redirect Trailing Slashes If Not A Folder...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} (.+)/$
RewriteRule ^ %1 [L,R=301]

# Remove public URL from the path
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ /public/$1 [L,QSA]

# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

4. Access the host via SSH and run in the laravel directory:

composer --version

If the version is < 2.0, run the following commands:

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === 'dac665fdc30fdd8ec78b38b9800061b4150413ff2e3b6f88543c636f7cd84f6db9189d43a81e5503cda447da73c7e5b6') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"

(This will create a .phar file)

5. Run the following commands:

php artisan key:generate
php artisan migrate
./composer.phar install

If it still doesn’t work, try:

./composer.phar dump-autoload

This will either resolve the issue or indicate what the problem is.

In my case, the problem was:

[u369742331@br-asc-web1845 public_html]$ ./composer.phar dump-autoload
Generating optimized autoload files
Class App\Http\Controllers\Api\QuestionsController located in ./app/Http/Controllers/api/QuestionsController.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Answer located in ./app/Models/answer.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Question located in ./app/Models/question.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Comment located in ./app/Models/comment.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

So basically, what you need to do is fix all the file or folder names that don’t follow the PSR-4 standard. After fixing them, run ./composer.phar dump-autoload again. It needs to run until all errors are resolved.

Tip: If you don’t understand what is PSR-4, paste the error into ChatGPT. It will tell you which folders and files names need fixing.