Project

General

Profile

Actions

Bug #23351

closed

Uncaught TYPO3 Exception when trying to edit old tt_news plugins or records

Added by Strg-F-Bug over 14 years ago. Updated over 10 years ago.

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

0%

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

Description

Uncaught TYPO3 Exception when trying to edit old tt_news plugin instances or tt_news records records

#1: PHP Catchable Fatal Error: Argument 2 passed to t3lib_iconWorks::getSpriteIconForRecord() must be an array, null given, called in /var/www/_global/typo3_src-4.4.1/t3lib/class.t3lib_treeview.php on line 663 and defined in /var/www/_global/typo3_src-4.4.1/t3lib/class.t3lib_iconworks.php line 736

Exception File attached

newly added tt_nwes records work fine

tt_news 3.0.1, I ignored the version requirements

seems related to 14880, patch did not help
related to 15202, patch did not help

(issue imported from #M15352)


Files

exeption.htm (13.7 KB) exeption.htm Administrator Admin, 2010-08-04 17:32
Actions #1

Updated by Strg-F-Bug over 14 years ago

...and i did the tt_news update process

Actions #2

Updated by Daniel Wagner about 14 years ago

have you set up the general record storage page?

Actions #3

Updated by Alekc about 14 years ago

I had this issue as well for one of my users. Turns out it was a problem of "mount" settings in user profile (I've had 2 storages mounted)

Actions #4

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • TYPO3 Version set to 4.4
  • 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 #5

Updated by Alexander Opitz over 10 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