Skip to content
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

Open
svenoe opened this issue Sep 30, 2024 · 0 comments
Open

Internal server error on AdminProcessManagment in new session. #3845

svenoe opened this issue Sep 30, 2024 · 0 comments
Labels
bug Something isn't working as intended
Milestone

Comments

@svenoe
Copy link
Contributor

svenoe commented Sep 30, 2024

Please try to reproduce on OTOBO 11.0 but see, whether older versions are affected:

  1. Log into OTOBO, go to AdminProcessManagement and open a process.
  2. In another tab remove your session in the session management and login again (to start a new session).
  3. In the first tab directly clock on "new activity"

To my understanding from looking at the code this leads to an undefined ScreensPath:

$Self->{ScreensPath} = $Kernel::OM->Get('Kernel::System::JSON')->Decode(
Data => $SessionData{ProcessManagementScreensPath}
);

And a following

Modification of non-creatable array value attempted, subscript -1 at /opt/otobo/bin/psgi-bin/../../Kernel/Modules/AdminProcessManagementActivity.pm line 672.

in:

if ( $Self->{ScreensPath}->[-1]->{Action} eq 'AdminProcessManagement' ) {

@svenoe svenoe added the bug Something isn't working as intended label Sep 30, 2024
@svenoe svenoe added this to the OTOBO 10.0.23 milestone Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended
Projects
None yet
Development

No branches or pull requests

1 participant