Bug #68417
closed
Check for broken extensions fails with direct_mail and tt_address
0%
Description
The Install Tool upgrade from TYPO3 6.1.12 to 6.2.14 marks extensions tt_address 2.3.3 and direct_mail 3.1.1 as broken.
Check for broken extensions Incompatible extension found! direct_mail tt_address
If I press [Uninstall all incompatible extensions], then it fails.
Something went wrong. Check failed. Message: The package "direct_mail" depends on "tt_address" which is not present in the system.
[21-Jul-2015 11:47:30 Europe/Berlin] PHP Fatal error: require_once(): Failed opening required 'PATH_t3libclass.t3lib_treeview.php' (include_path='/home/myusername/public_html/myusername/typo3/contrib/pear/:.:/usr/share/php:/usr/share/pear') in /home/myusername/public_html/myusername/typo3conf/ext/tt_address/class.tx_ttaddress_tcefunc_selecttreeview.php on line 27
[21-Jul-2015 11:47:30 Europe/Berlin] PHP Stack trace:
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 1. {main}() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Start/Install.php:0
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 2. TYPO3\CMS\Install\Controller\AjaxController->execute() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Start/Install.php:119
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 3. TYPO3\CMS\Install\Controller\AjaxController->dispatchAuthenticationActions() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Classes/Controller/AjaxController.php:63
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 4. TYPO3\CMS\Install\Controller\Action\Ajax\AbstractAjaxAction->handle() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Classes/Controller/AjaxController.php:149
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 5. TYPO3\CMS\Install\Controller\Action\Ajax\ClearCache->executeAction() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Classes/Controller/Action/Ajax/AbstractAjaxAction.php:29
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 6. TYPO3\CMS\Install\Service\ClearCacheService->clearAll() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Classes/Controller/Action/Ajax/ClearCache.php:35
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 7. TYPO3\CMS\Core\Core\Bootstrap->loadExtensionTables() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/install/Classes/Service/ClearCacheService.php:82
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 8. TYPO3\CMS\Core\Utility\ExtensionManagementUtility::loadExtTables() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/core/Classes/Core/Bootstrap.php:944
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 9. TYPO3\CMS\Core\Utility\ExtensionManagementUtility::loadSingleExtTablesFiles() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:1754
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 10. require() /home/myusername/public_html/myusername/typo3_src-6.2.14/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:1776
[21-Jul-2015 11:47:30 Europe/Berlin] PHP 11. include_once() /home/myusername/public_html/myusername/typo3conf/ext/tt_address/ext_tables.php:99
Updated by Franz Holzinger over 9 years ago
Info: direct_mail_subscription has also been installed. It depends on tt_address.
Updated by Josef F. Glatz (Old User) over 9 years ago
I don't know if it helps, but I'm using tt_address 3.0.0-dev from git.typo3.org with TYPO3 6.2.14 and direct_mail 4.0.1 from ter without problems. If I try to install ext:direct_mail from ter with composer, the composer throws a warning:
Warning: Ambiguous class resolution, "ext_update" was found in both "$baseDir . '/typo3conf/ext/direct_mail/class.ext_update.php" and ".../typo3conf/ext/tt_address/class.ext_update.php", the first will be used.
But for me, all is green in the install tool function "Check for broken extensions". I can't reproduce it.
Could you also try it with the master of tt_address?
Updated by Wouter Wolters over 9 years ago
Both extensions are not up to date to run on 6.2. Please update them first before upgrading to 6.2
Updated by Stefan Neufeind over 9 years ago
@Wouter: But still it should work to uninstall them when broken extensions are found.
Updated by Wouter Wolters over 9 years ago
That would be really hard to achieve. The problem is that there is no dependency check done when unloading an extension.
And to implement the whole dependecy logic in Install Tool too is IMO an big overhead.
Updated by
Updated by Christian Kuhn over 7 years ago
- Status changed from New to Closed
please fix extensions and dependencies.