TYPO3 Core

Hi everyone.

I might shed some light on this one:
When you point the composer to some none existing directory or files, it "breaks" the ClassMapGenerator.

Just add something like this:

  "autoload": {
    "psr-4": {
      "Whatever\\Break\\": "Classes" 
    },
    "files": ["somedir/somefile.php"]
  }

As far as I can see, is the mainproblem here, that it stops the ClassMapGenerator in it's tracks. New extensions can not be installed afterwards without a fatal.
Tested with TYPO3 7.6.10

How to reproduce:
1.) Create an extension with wrong autoloader configuration.
2.) Install something new from the TER
3.) Get a "class not found" fatal, because the ClassMapGenerator could not reach the new installed extension.

Hope this helps.

Tobi

Hi Tobi,

thanks for your answer. But referring to a non-existing path in your composer.json is breaking in every way because not only the ClassMapGenerator will throw an error, but composer itself will fail with installation.

If the problem only occurs with invalid paths this is not a core issue at all.

Hi Nicole.

The installation of the faulty extension actually works, but composer class map will crash with a handled TYPO3 warning.

If the problem only occurs with invalid paths this is not a core issue at all.

That is how I see it, too. Although I have not tested, what happens if I disable all error handling. If disabling the error handler works, the core might be able to work around this issue.

Edit: Disabling error handling does not work, because a \RuntimeException is explicitly thrown, halting the code.

Tobi

I can report a similar behavior.

Just update my local installation with composer update which jumped from 7.6.9 to 7.6.11 and at the end of the process I get the following error message

[RuntimeException]
Could not scan for classes inside "web/typo3/sysext/extbase/Tests/Unit/Object/Container/Fixtures/" which does not appear to be a file nor a folder

The same I get with composer dump-autoload.

The problem may be the composer.json of extbase which contains

"autoload-dev": {
    "psr-4": {
        "TYPO3\\CMS\\Extbase\\Tests\\": "Tests/" 
    },
    "classmap": ["Tests/Unit/Object/Container/Fixtures/"]
}

As a result the system doesn't run properly.

Do you need these fixture files? If not please remove the autoload-dev information from your root composer file.

Ah, perfect. Good to know. Works perfectly now. Thank you very much for that fast hint.

Just trying to install extension PerfectLightBox 4.0.2 on Typo3 7.6.11. It says:

Could not scan for classes inside "D:/wamp/www/typo3conf/ext/perfectlightbox/Classes/" which does not appear to be a file nor a folder

After manual creating of "Classes" folder the problem is gone.

Hi Alex!

The problem with perfectlightbox in version 4.0.2 is, that is hasn't any Classes folder but specifies this one in its composer autoload information. This is no core but an extension bug and has to be resolved in there.