#14322Error messages when open Install tool from Backend
Description
The error applies to the zip-dist.
My configuration: Windows XP prof, Apache 1.3.31, PHP 4.3.7, MySql Client API version 3.23.49. This is my testinstallation.
Upgraded from zip as recommended in Installation an Upgrade of TYPO3 manual. After login to the backend, when trying to open install tool i got following error messages.
Warning: main(c:/webprogram/apache group/apache2/htdocs/site_a/typo3/ext/install/mod/class.tx_install.php): failed to open stream: No such file or directory in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\init.php on line 215
Fatal error: main(): Failed opening required ‘c:/webprogram/apache group/apache2/htdocs/site_a/typo3/ext/install/mod/class.tx_install.php’ (include_path=’.;c:\php4\pear’) in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\init.php on line 215
I also got following messages in the treestructur
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\t3lib\class.t3lib_db.php on line 711
Warning: mysql_free_result(): supplied argument is not a valid MySQL result resource in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\t3lib\class.t3lib_db.php on line 748
Warning: Cannot modify header information – headers already sent by (output started at c:\webprogram\apache group\apache2\htdocs\site_a\typo3\t3lib\class.t3lib_db.php:711) in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\template.php on line 601
I supposed the messages indicate somthing wrong in the where the files where located, so i copied all the content from typo3/sysext/install/mod/ to typo3/ext/install/mod/.
It did the trick, no problem open the install tool, and doing the upgrade of db. But one problem is still there. Trying to look at the php-info give an error.
Fatal error: Call to undefined function: imagetypes() in c:\webprogram\apache group\apache2\htdocs\site_a\typo3\ext\install\mod\class.tx_install.php on line 943
(issue imported from #M366)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.