Old constraints in ext_emconf.php after extension update with active opcode cache
In a clean TYPO3 installation on a server with an activated opcode cache install an extension, f.e. static_info_tables. Then change the dependencies in the extensions ext_emconf.php. Then install the extension again by uploading the .t3x file in the extension manager.
The dependencies in the ext_emconf.php will not be updated.
This happens also, if you want to update an extension with the extension manager.
This happens only, if the extension gets installed/updated with a .t3x file. If you upload the .zip version in the extension manager, everything works fine.
In the .t3x file is no dependency information (and the other constraints, too) stored. So `\TYPO3\CMS\Extensionmanager\Utility\EmConfUtility::includeEmConf()` is called, to get the missing informations. But the `include` in this function gets the old ext_emconf.php from the opcode cache.
One solution would be, to call `\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Core\Service\OpcodeCacheService::class)->clearAllActive($path);`. But I have the feeling, that everything gets really slow then.
Another solution would be, to get the missing information from the table tx_extensionmanager_domain_model_extension or from the array $extensionData['FILES'].
I've found this issue in TYPO3 6.2 and 7.6, and I think it is still present in master.
What do you think would be the best solution?
#2 Updated by Riccardo De Contardi about 2 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, please reopen it or open a new issue with a reference to this one. Thank you.