Bug #24151
closed
conf.php files aren't corrected when installing extensions
0%
Description
I installed the dummy package on a clean typo3 created database with the src tgz file.
When i install an extension the conf.php files aren't correctly created. The mod1/conf.php file from templavoila looks like this:
define('TYPO3_MOD_PATH', 'templavoila/mod1/');
$BACK_PATH='';
and it should be:
define('TYPO3_MOD_PATH', '../typo3conf/ext/templavoila/mod1/');
$BACK_PATH='../../../../typo3/';
Tried it twice with a clean installl
Typo3 is installed in this folder:
/var/www/public_html/typo3
Basic configuration shows all paths correct
Apache/2.2.14 (Ubuntu)
php 5.3.2-1ubuntu4.5 with Suhosin Patch 0.9.9.1
(issue imported from #M16495)
Files
Updated by Rob Vonk about 14 years ago
Found out why this happens.
In refactoring the extension manager some classes are splitted.
Now in the file typo3/sysext/em/classes/tools/class.tx_em_tools.php on line 895 and 901 this array is used:
$this->typeRelPaths[$type]
But the array is not in the class tx_em_Tools. It's defined in the class SC_mod_tools_em_index.
It works when you add a global $SOBE in function writeTYPO3_MOD_PATH and replace the $this->typeRelPaths[$type] with $SOBE->typeRelPaths[$type] and $this->typeBackPaths[$type] with $SOBE->typeBackPaths[$type] but i'm not sure if thats the best solution.
Updated by Jigal van Hemert about 14 years ago
Because tx_em_Tools is meant to be called statically there can't be a reference to $SOBE, so I added two parameters.
The Extension Manager is in progress of being refactored/rewritten, so I consider this to be a temporary fix until the new EM is ready.
Updated by Jigal van Hemert almost 14 years ago
Committed v2 to trunk in rev 9502 (will appear in version 4.5.0)
Updated by