Bug #25316

meaningfulTempFilePrefix generates bad file names in some cases

Added by Dmitry Dulepov over 10 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-03-14
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

If you:
- create an IMAGE object using GIFBUILDER, and
- use meaningfulTempFilePrefix, and
- use text from a field, which contains CR, NL, commas or exclamation marks,
image's file name will contain all those symbols. If it has a CR symbol, it will show a 404 error in the backend. In other cases it will not be accessible by regular shell commands.

Example TS:

config.meaningfulTempFilePrefix = 100
page.777 = IMAGE
page.777 {
    file = GIFBUILDER
    file {
        XY = 200,100
        backColor = red
        20 = TEXT
        20 {                    
            text {
                dataWrap (
Hello, world!
I love you!
)
            }
            fontSize = 18
            fontColor = yellow
            offset = 5, 20
        }
    }
}

The problem affects only TYPO3 version 4.4.7 (not 4.5.0, not 4.4.6).

(issue imported from #M17936)


Files

17936.diff (1 KB) 17936.diff Administrator Admin, 2011-03-14 13:47

Related issues

Related to TYPO3 Core - Bug #23382: meaningfulTempFilePrefix does not convert Umlauts and special charactersClosedJeff Segars2010-08-16

Actions
#1

Updated by Mr. Hudson about 10 years ago

Patch set 3 of change Icf6a33a75856dc004e1db67fa14696ca264904e8 has been pushed to the review server.
It is available at http://review.typo3.org/1159

#2

Updated by Dmitry Dulepov about 10 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
#3

Updated by Benni Mack over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF