Bug #57386
closed
Fatal error after update from 6.1.7
Added by Bernd Wilke over 10 years ago.
Updated over 9 years ago.
Description
I'm unable to enter install-tool after changing the typo3_src-link from 6.1.7 to 6.2.0 (end deleting all from typo3temp):
Fatal error: Uncaught exception 'BadFunctionCallException' with message 'TYPO3 Fatal Error: Extension key "flux" is NOT loaded!' in /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:118 Stack trace: #0 /var/www/vhosts/typo3/t3.emoto2.local/www/typo3conf/ext/fluidcontent/ext_autoload.php(2): TYPO3\CMS\Core\Utility\ExtensionManagementUtility::extPath('flux', 'Classes/Utility...') #1 /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Package/Package.php(258): require('/var/www/vhosts...') #2 /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Core/ClassLoader.php(575): TYPO3\CMS\Core\Package\Package->getClassFilesFromAutoloadRegistry() #3 /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Core/ClassLoader.php(478): TYPO3\CMS\Core\Core\ClassLoader->loadClassFilesFromAutoloadRegistryIntoRuntimeClassInformationCache(Array) #4 /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Package/PackageManager.php(616): TYPO3\CMS\Core\Co in /var/www/vhosts/typo3/typo3_src-6.2.0/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php on line 118
there was an announcement, that install-tool always is accessable. even if you have errorous extensions installed.
I managed to resolve this issue by hand:
moving the extension flux in front of fluidcontent.
extension flux was one of the last because of an update some time ago.
install tool should be able to handle it automatically!
I will check with some of the involved people whether we can catch fatal errors in the ext_autoload.php files.
- Status changed from New to Accepted
- Assignee set to Nicole Cordes
- Status changed from Accepted to Needs Feedback
Hi Bernd!
thanks for your feedback and your investigation!
Bernd Wilke wrote:
I managed to resolve this issue by hand:
moving the extension flux in front of fluidcontent.
extension flux was one of the last because of an update some time ago.
Can you please post the exact version numbers of flux and fluidcontent (and maybe other dependent extensions) you were using during upgrade?
install tool should be able to handle it automatically!
Two different issues need to be checked.
- Does the dependency handling of the package management is working correctly in this case? The dependency handling should correctly set the loading order.
- Exceptions/ Errors in ext_autoload.php from extensions should be handled gracefully
Just another information which would be helpful. Could you please check the loading order in your old localconf.php? Is flux loaded before or after fluidcontent?
Hey Nicole, I experienced the same issue and I'm still trying to solve that. For me the flux extension was loaded "after" fluidcontent. I swapped both lines of code in LocalConfiguration.php, but the issue is still pending. As soon as I get it running again I'll post the version of the respective extensions.
UPDATE:
Within file LocalConfiguration.php I changed the position of element flux prior element fluidcontent in array "extListArray". That seems to be change Bernd also did.
- Status changed from Needs Feedback to Accepted
- Status changed from Accepted to Needs Feedback
Robert Peter wrote:
Hey Nicole, I experienced the same issue and I'm still trying to solve that. For me the flux extension was loaded "after" fluidcontent. I swapped both lines of code in LocalConfiguration.php, but the issue is still pending. As soon as I get it running again I'll post the version of the respective extensions.
UPDATE:
Within file LocalConfiguration.php I changed the position of element flux prior element fluidcontent in array "extListArray". That seems to be change Bernd also did.
Just to be sure:
So in extListArray (in 6.1 installation) the extension fluidcontent was before flux despite fluidcontent depends on flux?
And once you swap the order before upgrade, the upgrade works fine?
@Helmut:
As I wrote above: I found the entry for the extension flux at the end of the extension list in LocalConfiguration.php. The 6.1 installation works flawless, so I assume the order of extension does not need to match the order of dependencies in 6.1 (other extensions may proove me wrong).
The upgrade worked fine after 'moving' the entry for flux to a point earlier than fluidcontent.
- Assignee deleted (
Nicole Cordes)
- Target version deleted (
next-patchlevel)
In 6.1 the order of extensions should be in line with dependency.
Anyway, there were fixes in 6.2.1 for the dependency ordering so this may be fixed.
Can you reproduce this issue with 6.2.4?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by