Bug #81311
closed
Autoloading-Informations not created after install extension
0%
Description
2. Install TYPO3
3. Create a Test-Extension with following depends configuration:
- array( 'extbase' => '8.7.0', 'fluid' => '8.7.0', 'typo3' => '8.7.0', 'recycler' => '', 'dce' => '', 'mask' => '', 'realurl' => '', 'cs_seo' => '', ),
4. Download the current extension list in extension manager via get extensions (I have not update via the update button, only over initial switch to "get extension")
5. Install the test extension which download the extensions from depends array
6. Error throws (class not found in my case from dce extension)
7. Delete autoload folder in typo3conf
8. Try reinstall the test extension
9. It works
When I add in this case in ext_emconf.php the autoload configuration which is since 6.2 not needed (you find a conversation about this here https://github.com/FriendsOfTYPO3/extension_builder/issues/39#issuecomment-303324207), it works.
Updated by Christian Forgács Forgács almost 7 years ago
- Description updated (diff)
Updated by Markus Klein almost 7 years ago
When I add in this case in ext_emconf.php the autoload configuration
What configuration are you adding there exactly?
Updated by Christian Forgács Forgács almost 7 years ago
In this case at DCE extension in typo3conf/ext/dce/ext_emconf.php:
'autoload' => [
'psr-4' => ['ArminVieweg\\Dce\\' => 'Classes']
],
as last child of the config array.
Updated by Markus Klein almost 7 years ago
This for sure should never be necessary, as long as the extensions define their autoloading correctly.
Updated by Markus Klein almost 7 years ago
- Status changed from New to Needs Feedback
To be sure, please add your OS, PHP version and if you use opcache or not. Thanks.
Updated by Christian Forgács Forgács almost 7 years ago
- OS: Debian 8.8
- PHP 7.0.19-1~dotdeb+8.1
- opcache enabled
Updated by Riccardo De Contardi almost 7 years ago
- Status changed from Needs Feedback to New
Updated by Markus Klein almost 7 years ago
- Status changed from New to Needs Feedback
I cannot reproduce the issue.
Maybe your opcode cache does weird stuff?
(it should get cleaned on each extension install though)
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Needs Feedback to Closed
90 days without feedback => closing it.
If you think that this is the wrong decision or experience the issue again or have more information about how to reproduce it, then please reopen it or open a new issue with a reference to this one. Thank you.