Class Foo\Bar\Baz located in ./foo/bar/utility/baz.php does not comply with psr-4 autoloading standard. Skipping

by

This can happen for a variety of reasons.

The important thing is to pay attention to the error message which generally points very accurately to the source of the issue.

Path Case

The most common reason for this is that, as shown in the error message, the case for the different components of the pathname for Bar.php do not match with the case for the fully qualified class name;

foo/bar/Baz.php does not match App\Bar\Baz.

Simply update your application or package so that each path component matches the case of its the namespace it holds:

Foo\Bar\Baz.php

File name and Class name or Namespace differences

Check the pathname against the namespace very carefully. Sometimes your named your class (or your namespace) FooBar, but its path on disk is “foo-bar”, for example. Or simply for any reason your namespace does not fully match the pathname of the files.

This will trigger a notice/warning as well. You need to either rename the files or rename the classes (or namespaces).

Usually, changing the path or files is much easier, since changing the class or namespace names would require you refactor code to match the new names, whereas changing the paths will not need you to refactor anything.

Nested namespaces and missing declaration

Let’s say that you have:

"autoload": {
        "psr-4": {
            "Fizz\\Buzz\\": "src/"
        }
    },

And the class Dummy, defined inside src/Buzz:

// src/Buzz/Dummy.php
namespace Fizz\Buzz

class Dummy {}

The above will work, but will throw the notice like the others. The correct way would be:

// src/Buzz/Dummy.php
namespace Fizz\Buzz\Buzz

class Dummy {}

You’ll need not only to make the change on the affected class, but on any other file where this class is used or imported. (e.g. by now declaring use Fizz\Buzz\Buzz\Dummy;).

More Related Contents:

  1. Why use a PSR-0 or PSR-4 autoload in composer if classmap is actually faster?
  2. How to create a PSR-4 autoloader for my project?
  3. Autoloading classes in PHPUnit using Composer and autoload.php
  4. Using Composer’s Autoload
  5. PHP adding custom namespace using autoloader from composer
  6. How to use Composer to autoload classes from outside the vendor?
  7. What are these exactly?: Composer, Git and Pyrus [closed]
  8. How to explain Composer’s error log?
  9. How to require a fork with composer?
  10. Override PHP base dependency in composer
  11. Composer error: “PHP extension fileinfo is missing from your system”
  12. How do I install Composer PHP packages without Composer?
  13. Composer Warning: openssl extension is missing. How to enable in WAMP
  14. Run composer with a PHP script in browser
  15. Autoload classes from different folders
  16. How to specify Composer install path?
  17. Laravel 5 Class ‘form’ not found
  18. PHP Composer behind http proxy
  19. Composer require local package
  20. What are the differences between composer update and composer install?
  21. Running Composer returns: “Could not open input file: composer.phar”
  22. 3rd party dependency conflict in developing WordPress Plugin
  23. How to downgrade or install a specific version of Composer?
  24. Could not open input file: composer.phar
  25. How to deploy correctly when using Composer’s develop / production switch?
  26. Skip composer PHP requirement
  27. What is autoload in php? [duplicate]
  28. but these conflict with your requirements or minimum-stability
  29. Difference between require and install vs create-project in composer
  30. Class Firebase\JWT\JWT not found

Leave a Comment