Project

General

Profile

Actions

Bug #24284

closed

Make all code plugin locations accept class names instead of full file / class paths

Added by Ingo Renner almost 14 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-12-03
Due date:
% Done:

0%

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

Description

Since we introduced an autoloader mechanism in TYPO3 4.3, every location in core code where one can register code to hook in or being executed additionally should support the autoloader.

Currently there are still a lot of locations that require developers to provide full paths to classes and methods to be executed. The goal is to allow providing just the class name to achieve the same result.

(issue imported from #M16660)

Actions #1

Updated by Ingo Renner over 12 years ago

  • Target version deleted (0)
  • TYPO3 Version changed from 4.3 to 6.0
Actions #2

Updated by Ingo Renner over 12 years ago

  • Target version set to 6.0.0
  • TYPO3 Version changed from 6.0 to 4.3
Actions #3

Updated by Wouter Wolters almost 10 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

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

Actions #4

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed
  • Target version deleted (6.0.0)

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

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