-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal server error on AdminProcessManagment in new session. #3845
Comments
replicated on ov276 for rel-11_0
|
So |
replicated on 10_0 - Internal Server Error (looks different, probably custom error page instead of default, but nonetheless same Internal Server Error):
|
my %SessionData = $Kernel::OM->Get('Kernel::System::AuthSession')->GetSessionIDData(
SessionID => $Self->{SessionID},
);
# convert JSON string to array
$Self->{ScreensPath} = $Kernel::OM->Get('Kernel::System::JSON')->Decode(
Data => $SessionData{ProcessManagementScreensPath}
);
At this point - if Session got killed/renewed in between - %SessionData will simply NOT hold a ProcessManagementScreensPath Hash key, causing the attempt to JSON decode to fail, resulting in $Self->{ScreensPath} being set to undefined. Treating it as an Array-Reference later on leads to the error msg reported. Strategies:
|
The bug described in #4100 actually relates to the changes made for this issue in #4026. Initially, the EntityID is an empty string for newly created activities, therefor the |
closing the issue with merged #4101 |
Please try to reproduce on OTOBO 11.0 but see, whether older versions are affected:
To my understanding from looking at the code this leads to an undefined ScreensPath:
otobo/Kernel/Modules/AdminProcessManagementActivity.pm
Lines 54 to 56 in 52c1cbc
And a following
in:
otobo/Kernel/Modules/AdminProcessManagementActivity.pm
Line 672 in 52c1cbc
The text was updated successfully, but these errors were encountered: