TYPO3 Core

After deleting package 10.4.9 the error was gone.

Hi, this seems like a caching issue regarding the service containers. Should have been resolved with flushing the cache in the install tool (Maintenance > Flush TYPO3 and PHP Cache), which should generally be performed after every core update.

If it's however already fixed for you, can this issue be closed?

Hello Oliver
Yes, of course I cleared the cache.
After deleting package 10.4.9 on the server the error was gone.
For me it is fixed. I'm already on version 10.4.12.
Can be closed.
Thank you for your commitment.

Hello Patrick,
what does it mean "deleting package 10.4.9."?

I have the same problem on a Windows, the paths in services.yaml causing the issue:

(1/1) Symfony\Component\DependencyInjection\Exception\InvalidArgumentException
Expected to find class "xxx\yyy\Command\AbstractCommand\AbstractCommand" in file "C:\Git-Typo\xxx\Classes/Command\AbstractCommand\AbstractCommand.php" while importing services from resource "../Classes/*", but it was not found! Check the namespace prefix used with the resource.

If i change to "..\Classes\*" it works but then another Exception is throwing with path issues:

"Class xxx\yyy\Domain\Model\Typo\SysLanguage does not exist" but the class def. exists in this dirrectory.

Hello Ralf
I think we don't have the same problem. Or did you also make an update?
Unfortunately, I cannot help you with your problems. It's about DI. DI is well described in the documentation.

With "deleting package 10.4.9." I mean the physical deletion of the entire package on the server.
It's the old package, so it can be deleted without hesitation.
And this after an update of the package (on a unix server with sim-links, Windows is different)!
Take a look at the procedure for an update, then you will surely understand what I mean by that.

Hello Patrik,

yes, i mean an composer update to 10.4.11.

In 10.4.9. all works fine, after upgrade the exception Symfony\Component\DependencyInjection\Exception\InvalidArgumentException occurs.

So I think the Path-Syntax in services.yaml is not valid anymore on a windows platform? "\" vs. "/"

Hello Ralf

It can (does not have to) have a connection if the definition regarding autoload is missing in ext_emconf.php.

ext_emconf.php

'autoload' => [
        'psr-4' => [
            'Vendor\\ExtensionName\\' => 'Classes',
        ],
    ],