Project

General

Profile

Actions

Bug #29001

closed

Warning: ksort() in Backend Layout Wizard Popup

Added by Simon Schaufelberger over 12 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2011-08-16
Due date:
% Done:

0%

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

Description

When opening the backend layout wizard as a popup, i get the following warning message at the bottom of the screen (if display_errors is set to 1).

Warning: ksort() expects parameter 1 to be array, null given in /typo3/sysext/cms/layout/wizard_backend_layout.php on line 185

TYPO3 Version: 4.5.4

Actions #1

Updated by Chris topher over 12 years ago

  • Subject changed from Warning: ksort() in Backend Layout Wizart Popup to Warning: ksort() in Backend Layout Wizard Popup
Actions #2

Updated by Philipp Gampe over 10 years ago

  • Status changed from New to Needs Feedback

Can you still reproduce this?

I do not get warnings there.

Actions #3

Updated by Simon Schaufelberger over 10 years ago

let me check that. can you assign that issue to me?

Actions #4

Updated by Philipp Gampe over 10 years ago

  • Category set to Backend API
  • Assignee set to Simon Schaufelberger
  • Complexity set to easy
Actions #5

Updated by Simon Schaufelberger over 10 years ago

i tried to reproduce it today even with 4.5.4 but was not able to do so. i have so many typo3 installations that i dont know which one was the one that had that problem. so i think until i don't find this problem again, you can just close this issue.

Actions #6

Updated by Philipp Gampe over 10 years ago

  • Assignee deleted (Simon Schaufelberger)

lets see if someone else comes up with that

Actions #7

Updated by Philipp Gampe over 10 years ago

Maybe you can still have a look at the code and (if possible) code some safeguard around it?

Actions #8

Updated by Alexander Opitz about 10 years ago

  • Is Regression set to No

Hi,

so after 5 months, can we close this issue?

Actions #9

Updated by Simon Schaufelberger about 10 years ago

if it's not reproduceable at the moment, i think yes.

Actions #10

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed
Actions

Also available in: Atom PDF