Project

General

Profile

Actions

Feature #45487

closed

Inexsistant error messages when trying to configure ImageMagick in Install Tool

Added by Lucas Jenß almost 12 years ago. Updated almost 11 years ago.

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

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

As it currently stands, when one tries to configure ImageMagick, there is
no feedback from the install tool if an error occured while trying to execute
ImageMagick commands.

For example, I recently had the problem that a webserver environment hat
a wrong library path, which resulted in the wrong libfreetype being used
by ImageMagick, but only when executed from within PHP. That particular
issue was very hard to debug (had to dig into the install tool methods), because
there was no feedback provided by the install tool.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #49162: Rewrite install toolClosed2011-10-30

Actions
Actions #1

Updated by Gerrit Code Review almost 12 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/18265

Actions #2

Updated by Gerrit Code Review almost 12 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/18265

Actions #3

Updated by Christian Kuhn about 11 years ago

  • Status changed from Under Review to Needs Feedback

Hey Lucas, we abandoned the patch for now since the install tool was fully rewritten in 6.2.

Could you maybe take a look at the 6.2 solution and see if your issue still exists? The patch itself would then probably look very different, too.

Actions #4

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