Project

General

Profile

Actions

Bug #22919

closed

Gifbuilder Mask processing failure for "mask.import.cObject" within GIFBUILDER-Object

Added by Gabriel Kaufmann over 14 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-07-07
Due date:
% Done:

0%

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

Description

I have build a dynamic Gifbuilder-Image on that I want to apply a dynamic Mask.

If you want to add a dynamic mask ob an IMAGE-Object, this is no issue:

10 = IMAGE
10.file = test.png
10.mask.import.cObject = GIFBUILDER
10.mask.import.cObject { # apply any dynamic mask build using GIFBUILDER
}

Doing the same into GIFBUILDER is NOT possible:

10 = IMAGE
10.file = GIFBUILDER
10.file {
XY = [10.w],[10.h]

10 = IMAGE
10.file = test.png
10.mask.import.cObject = GIFBUILDER
10.mask.import.cObject { # apply any dynamic mask build using GIFBUILDER # HERE IT WILL FAIL!
}
}

I found this error on TYPO3 4.4 on a new Web-Project.

I tracked the problem back to gifbuilder:

class.tslib_gifbuilder.php on Line 225 (where IMAGE is defined):

--[ CODE: start ]--
if ($conf['mask']) { # image processing
[...]
}
--[ CODE: end ]--

This cannot work because the "import" on "mask.import.cObject" will be defined with a "dot" after 'mask'.

I made a patch that corrects this behaviour. The CODE Line above will simply be replace by the following code. Now even an empty mask-Object with "import" will be processed (verifyied to work).

--[ CODE: start ]--
if ($conf['mask'] || $conf['mask.']) {
--[ CODE: end ]--

PATCH ATTACHED ;-)

This seems to be a Bug! I've not tested if this bug is also present in recent TYPO3 Versions!
(issue imported from #M15026)


Files

Actions #1

Updated by Alexander Opitz about 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF