error Kernel Output HTML Layout BuildSelection Need Data!

[fritzfreund]

Ever since I installed ITSM I tried to update a notification event and when I save it, I get this error in the syslog, and the notification stops working. I can also not create a new notification for some reason!

Code: Select all

 OTRS-CGI-13[2658]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!

I've looked at the Layout.pm on line 2154 and it seems like I'm not filling in a required field. But everything work just fine before I upgrade from 3.1.? to 3.1.11 and installed ITSM. Now my ticket close notification isn't working.. so I"m kind of in a bad place right now..

[crythias]

Now my ticket close notification isn't working.. so I"m kind of in a bad place right now

There's always the ability to use the reply feature (as designed) to send the "I'm closing this ticket. Thanks" next state closed.

[fritzfreund]

True, but I would still like to have a closure message and fix the error. It bugs me that nothing was changed on the notification yet I still get an error.

[reneeb]

Are there any chances that you know which drop down can't be filled?

[fritzfreund]

Are there any chances that you know which drop down can't be filled?

We installed ITSM but haven't configured it yet. I assume it has to be a required field that isn't set in the interface as required.... but I can't figure out what it is.

[fritzfreund]

So, I removed ITSM however I still get the same error. The changes I made to the form are made, but the logs are still being spammed.

[crythias]

It's three months later. Can you please better describe the path to replicate this issue?

[fritzfreund]

Yeah, sorry about that. Here is a little more background.

I had a standard install of OTRS 3.0.?.
I upgraded to OTRS 3.1.11.
I installed ITSM via the package manager.

We started getting this issue at that time. It could be due to not configuring ITSM correctly.

I removed all the ITSM components via Package Manger.

However now we are still getting the same error.

Code: Select all

    742 Mar  6 10:31:40 IME-HQOTRS00 OTRS-CGI-13[11619]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!
    743 Mar  6 10:32:09 IME-HQOTRS00 OTRS-CGI-13[16189]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!
    744 Mar  6 10:32:16 IME-HQOTRS00 OTRS-CGI-13[16189]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!
    745 Mar  6 10:33:39 IME-HQOTRS00 OTRS-CGI-13[16176]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!
    746 Mar  6 10:33:58 IME-HQOTRS00 OTRS-CGI-13[11108]: [Error][Kernel::Output::HTML::Layout::BuildSelection][Line:2154]: Need Data!

I'm not sure why we would be getting this issue. The notifications I was modifying accepted the changes I made. I'm just worried that something isn't being updated correctly or that I'm going to run into issues later due to the errors.

Thank you.

[crythias]

You don't get this error message just by installing a module (typically). You get *this* error message from a screen (Module) that calls BuildSelection and it tries to build a selection for a field that doesn't have values.

What could that be?

Don't know. But you'd know. Probably you have customer .dtls or a custom theme.

This message is specific to your implementation in ways that wouldn't happen to everyone else.

Further, "Need Data" means that the array key "Data" isn't being passed to BuildSelection (Or it could be null in scope).

Where?

Again, I don't know. But it's a module related to a screen you're using.

[fritzfreund]

The screen I'm using when I get that error is the normal way you would edit a notification event. I haven't added custom themes or anything. I did notice when we did the upgrade that the log in screen seems to be missing something when I log in. Could be an issue from the upgrade? Maybe the new theme didn't come over correctly during the upgrade?

How do I go about getting the default theme back on for 3.1.11?

[crythias]

copy from source. But this is a data issue. I don't know what's missing, but it's one of the fields in notification.