[TYPO3-english] owner and group

[Styrmir Magnússon]

On Wed, 07 Jan 2009 10:01:07 +0530, J. Bakshi wrote:

> Styrmir Magnússon wrote:
>> Hello
>>
>> I am trying to find out what is wrong with my TYPO3 setup. There are
>> some things that are not working with my page and it doesn't event show
>> in error.log what it is.
>> RTE is not working even thou it is enabled everywhere it should be.
>> t3editor has the same problem.
>>
>> Everything works with my dev server where I am root But at my ISP then
>> I have this problem mentioned above.
>>
>> safe mode is off open_basedir is off
>> I have now been trying for at least a week. Next guess is if it is
>> possible that is has to do with the ownership and the groups on the
>> server
>>
>> this is my structure
>>
>> total 48
>> -rw-r--r-- 1 kfum ftpuser   46 Nov 11 03:29 clear.gif drwxrwx--- 4 kfum
>> apache  4096 Jan  6 13:55 fileadmin -rw-r--r-- 1 kfum ftpuser 5051 Nov
>> 11 03:29 _.htaccess lrwxrwxrwx 1 kfum ftpuser   19 Jan  6 13:10
>> index.php -> typo3_src/index.php -rw-r--r-- 1 kfum ftpuser 7087 Nov 11
>> 03:30 INSTALL.txt -rw-r--r-- 1 kfum ftpuser 7695 Nov 11 03:30
>> README.txt -rw-r--r-- 1 kfum ftpuser  425 Nov 11 03:30
>> RELEASE_NOTES.txt lrwxrwxrwx 1 kfum ftpuser   15 Jan  6 13:10 t3lib ->
>> typo3_src/t3lib lrwxrwxrwx 1 kfum ftpuser   15 Jan  6 13:10 typo3 ->
>> typo3_src/typo3 drwxrwx--- 4 kfum apache  4096 Jan  6 13:55 typo3conf
>> lrwxrwxrwx 1 kfum ftpuser   18 Jan  6 13:10 typo3_src ->
>> ../typo3_src-4.2.3 drwxrwx--- 9 kfum apache  4096 Jan  6 13:55
>> typo3temp drwxrwx--- 5 kfum apache  4096 Jan  6 13:55 uploads
>>
>> Best regards
>> Styrmir Magnusson
>> _______________________________________________ TYPO3-english mailing
>> list
>> TYPO3-english at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>>
>>
>>   
> Hello,
> 
> Never mix the owner:group combination.  you have 2 different types of
> combination
> 
> kfum ftpuser
> kfum apache
> 
> Typo3 needs apache owner or group access rights to work properly.
> 
> If you have access then try to read the apache error.log. Generally it
> shows the problem correctly
that is the problem there are no errors in the error.log file

> 
> hope these help