Bug #48523: Reports Module $className must be a non empty string. - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #48523

closed

Reports Module $className must be a non empty string.

Added by Matthias Eberlein over 11 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

Reports

Target version:

Start date:

2013-05-25

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

6.0

PHP Version:

5.4

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

If last selected report type isn't available any more (by removing the extension which have the report) the reports module try to load an empty className and crashs.

i get this error while opening the Reports Module on 2 diff TYPO3 systems

$className must be a non empty string.

1.) Version 6.1.1

2.) Version 6.1.2

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #45508: Reports module broken

Closed

2013-02-15

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Alexander Opitz over 11 years ago

Status changed from New to Needs Feedback

Hi Matthias,

we need some more Informations on this issue as it seems nobody can reproduce the issue. It may come from an extension we do not use. Do you have a backtrace in a log file?

Maybe you can edit /typo3/sysext/core/Classes/Utility/GeneralUtility.php and go to the function makeInstance (around line 4000: "static public function makeInstance($className) {")
and add before the "throw new \InvalidArgumentException('$className must be a non empty string.', 1288965219);" following statement:

debug_print_backtrace();

Then open the reports module and copy the output to this bug report.

Actions

Copy link

Updated by Matthias Eberlein over 11 years ago

Hi Alexander,
if got it.

So, i have installed before the "deprecationloganalyzer" from George. And from the last access of the module "reports" was the deprecationloganalyzer log Activated (dropdown). Then after some Checks i'm uninstall the Extension deprecationloganalyzer, but i don't change before in the module Reports the dropdown status from "deprecationloganalyzer log" to the normal reports status or overview. So, if you try to open then the reports module, you get the $className error.

This surprise i saw after activate some deeper error logging.

28-05-13 17:39 - Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1288965219: $className must be a non empty string. | InvalidArgumentException thrown in file /var/www/virtual/webspace/sources/typo3core/TYPO3.CMS/typo3/sysext/core/Classes/Utility/GeneralUtility.php in line 4077. Requested URL: webspace ://webspace.webspace.uberspace.de/typo3/mod.php?M=tools_ReportsTxreportsm1&tx_reports_tools_reportstxreportsm1%5Bextension%5D=tx_deprecationloganalyzer&tx_reports_tools_reportstxreportsm1%5Breport%5D=index&tx_reports_tools_reportstxreportsm1%5Bredirect%5D=1&tx_reports_tools_reportstxreportsm1%5Baction%5D=detail&tx_reports_tools_reportstxreportsm1%5Bcontroller%5D=Report

But there was no "deprecationloganalyzer" installed, so i'm install them and all works as normal.

Sorry sorry.
so, many thanks for your attention.

Matthias

Actions

Copy link