Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

Mention requirement to put the autoload config into the central composer.json for new extensions #231

Closed
hmb opened this issue Mar 7, 2019 · 2 comments
Labels
content Issues / PR about changing / updating / adding ... content

Comments

@hmb
Copy link

hmb commented Mar 7, 2019

After working through the example Creating a first extension with a composer installed TYPO3 V9.4 I get an error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1278450972:
  Class MyVendor\StoreInventory\Controller\StoreInventoryController does not exist.
  Reflection failed.

The reason seems to be that the autoload configuration has to be put into the root composer.json. I posted the details in an answer to a similar question on SO. Maybe this can be put into the appropriate place into the documentation.

@sypets sypets added content Issues / PR about changing / updating / adding ... content content missing New content must be written labels Jul 14, 2019
@sypets sypets removed the content missing New content must be written label Oct 15, 2019
@alexanderschnitzler
Copy link
Contributor

The question is how people develop new extensions. There is a way to do this with composer from the beginning on. In that case, the autoload section of the extenision's composer.json is used. I don't know if the Extbase book needs to explain such things since this is true for every extension, even those that don't use Extbase.

In my opinion there should be a documentation about creating extensions and it's very basics. The info about ext_emconf.php and such. But it should be outside this book and we should be able to reference it.

@linawolf
Copy link
Member

This is a general topic of Extension development and handled in TYPO3 Explained

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
content Issues / PR about changing / updating / adding ... content
Projects
None yet
Development

No branches or pull requests

4 participants