TYPO3 Core

Hi Manuel,

there is an option in the Install Tool to set the file permissions. Search in "All Configuration".
Is the value which is set there correct? And is it used or is it not?

Hi Christopher

Thank you for your fast reply. To be honest: There is a file-permission-flag set in the install tool. I've quickly attached you a screenshot of the current setting in my system-installation.

Even if i change both of these values from 0755 to new 755 it doesn't help.

I also added new information about the current settings in the second screenshot. mybe this helps solving the problem...

I can confirm that problem. It is typical for apache servers running fastcgi with php. typo3 needs to change the permissions after generating the temp files. otherwise the permissions will be 0600. The BE settings mentioned above seem not to work anymore since the update to 4.4.0.

To be honest, I've tried on and detected there is a thumbnail-preview in the system itsselfs which allows you to preview the files exactly the way it should work.

There is a public Function in class.t3lib_div.php which intends to repair / to fix file and folder permissions. But somehow it seems to be either the correct BE-Function/Class or the one from the FE with errors....

public static function fixPermissions($path, $recursive = FALSE) {

It would be great, if you could figure out, how that worked in older versions and why it does not work anymore now.
I think then you already have the fix. :-)

I can make out two basic changes between an elder and the current TYPO3 version for so far:

first of all, earlier TYPO3 developer used "t3lib_div::" insted of the new used "self::" calls in their functions, seccondly they used to include a newer function called "fixPermissions()". These two are the main changes in the used procedures in my point of view.

f.e. in the function writeFileToTypo3tempDir($filepath,$content):

if (self::validPathStr($filepath) && $fI['basename'] && strlen($fI['basename'])<60) {
if (self::isFirstPartOfStr($fI['dirname'],$dirName)) {
self::mkdir_deep(PATH_site.'typo3temp/', $subdir);
self::writeFile($filepath, $content);

Earlier on the mentioned parts looked like this:
if (t3lib_div::validPathStr($filepath) && $fI['basename'] && strlen($fI['basename'])<60) {
if (t3lib_div::isFirstPartOfStr($fI['dirname'],$dirName)) {
t3lib_div::mkdir_deep(PATH_site.'typo3temp/', $subdir);
t3lib_div::writeFile($filepath, $content);

I also tried to check further files - such as PDF-Documents with a preview. The PDF Preview doesn't turn up in the FE. So there must definitively be somtehing wrong with the file permissions.

by the way: The use of 0755 instead of 755 should be taken, because the octdez() function, which is used in TYPO3.

we think we solved the problem: just add

$path = (self::isAbsPath($path)) ? PATH_site . $path : $path;
before
if (self::isAllowedAbsPath($path)) {
in fixPermissions declareation.
The problem referes to a absolut path problem when the image path is put into the fixPermissions function. The "isAllowedAbsPath" will always return false if the path is not absolute.

Using self:: is done for performance reasons. I think, this does not cause the problem.

The function fixPermissions() is new; most probably it is the reason for this issue.
It was integrated in #3977. Here is a diff-view:
http://forge.typo3.org/projects/typo3v4-core/repository/revisions/7430/diff

Alexander Grein: That's it! Nice, cheers!

Can you add the diff-view/Bugfix on this Thread? This seems to work very well!

Christopher: Maybe this didn't work in your point of view because might not have cleaned up the Cache. As soon I've cleaned it up - the pictures turned up well!

Thank you Alex!

By the way: does anyone in here know how i can pay the fee of 30 euros? the description isn't available here - or maybe I didn't finde it....

Alex: Please attach the patch file here and send it as an RFC to Core List. Then it will be included in the next versions.
See http://typo3.org/teams/core/core-mailinglist-rules

Manuel, Alex: You should exchange your e mail addresses or phone numbers so that you can clear that.

Hello Manuel,

you can use PayPal to send me the money.
My Email for this is a.grein [Klammeraffe] mediaessenz.de

Thanks!

bug_0015133.diff is made against current trunk version

Christopher:
I have looked into the core-mailing-ist-rules page, but get no idea, how to do this.
Can you please explain me, how i can do this.

Deutsche Anleitung zu diesem Thread:
http://www.typo3.net/forum/list/list_post//100055/

Hi Guys... actually i wanted to quit this thread, but didn't get any chance or button to finish up this right now... could you then please assign the complete flag? cheers

@ Alex:
You need a newsreader. For example Outlook (Express), Windows Live Mail or Thunderbird.
Use the newsreader of your choice and subscribe to the newsgroups at lists.typo3.org
The port (if asked for) is 119.

You will see, that there are several newsgroups on that server; you need to subscribe to the one called typo3.teams.core.

This is the newsgroup you must post a new mail to.
Just have a look at all the other thread-starting-mails there. They all look as described here: http://typo3.org/teams/core/core-mailinglist-rules#c4741
Just copy that scheme and put in the title, description and so on from this bug report. Don't forget to attach the patch!

Happy posting!

@ Manuel:
That is right that way.
This issue will be set to resolved, when Alex' bugfix has been integrated in the TYPO3 SVN repository. (The SVN repository is the place where the source code for the next versions of TYPO3 is stored.)

To get that done, Alex has to post his patch in the Core List (as described above).
In this thread (in Core List), you should then give your "+1 on reading and testing", because you successfully tested the patch. After at least two "+1"s the patch can be integrated in the repository (which will be done by a Core Developer).

Christopher
Thanx for guiding through and for your time and patiency. " Why do noobs always ask such adorable questions ;)"

I have posted the request in the typo3 core list.

Christopher: Thanks for help.

Manuel: Please do the "+1 on reading and testing" part

+1

I'm sorry, but i don't find any +1 on reading and testing.... nowhere in bugtracker... how do I manage this? how do I set it to solved with patch status?

• trunk rev. 10019
• 4.4 rev. 10020