Project

General

Profile

Actions

Feature #16926

closed

Connection between errors in Template Object Browser and Template Analyzer

Added by Andreas Balzer almost 18 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2007-01-31
Due date:
% Done:

0%

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

Description

As i'm using T3 4.0.4 I don't know whether this feature is already implemented into T3 4.1b3, but it would be very cool if you can do it.
If you go to Template Object Browser and you have some errors there, it shows you the line where the error occurs. Well, you now have to go to the Template Analyzer, look for this line and then open the template in order to fix this. It would be cool, if Template Object Browser can link the linenumber of the error message to the according point in Template Analyzer and maybe Template Analyzer can provide a nice link to the correct template file... Just some nice things I'd like to see.

(issue imported from #M4897)

Actions #1

Updated by Alexander Opitz over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • PHP Version deleted (4)

As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?

Actions #2

Updated by Chris topher over 11 years ago

Nice idea. With t3editor, you do have line numbers in your template, but two things are not possible currently:

  • The according lines are not linked to from the Object Browser.
  • The line numbers given in the Object Browser often (always?) are different from the ones in your template, as the Object Browser numbers the complete template code from line 1 to line xxx while t3editor only numbers the current template.
Actions #3

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to New
Actions #4

Updated by Georg Ringer almost 10 years ago

  • Status changed from New to Resolved

this works already quite a long time, at least in 6.2 and 7.

Actions #5

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF