You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I activated the Program (Sponsor) option in the server settings, as shown in the screenshot below.
After creating a program and setting a non-SEEK-admin as Program-admin, I tried to create Trial Projects in the Program.
I gave the Trial Project a titel and pushed "create".
The next page was an Error 500 page.
After going back in the browser, I saw, that the project was created. As I tried to open it, I saw Error 500 again.
However, the Error 500 appears randomly (see attached mp4).
I observed no difference in the error appearance between the Program-admin and the SEEK-admin account.
I noticed, that the Error also appeared on other unrelated sites in the LDH (My items, non-Program Trial Projects).
After deactivating the Program option, everything was fine again.
It looks like the whole Program function is buggy.
Mijar007
changed the title
Error 500 during and after Trial Project creation in a Program/Sponsor
Randomly appearing Error 500 with activated Program/Sponsor function
Dec 5, 2024
Describe the bug
I activated the Program (Sponsor) option in the server settings, as shown in the screenshot below.
After creating a program and setting a non-SEEK-admin as Program-admin, I tried to create Trial Projects in the Program.
I gave the Trial Project a titel and pushed "create".
The next page was an Error 500 page.
After going back in the browser, I saw, that the project was created. As I tried to open it, I saw Error 500 again.
However, the Error 500 appears randomly (see attached mp4).
I observed no difference in the error appearance between the Program-admin and the SEEK-admin account.
Expected behavior
No error 500.
Screenshots
Server Settings:
Error 500 MP4 clip:
https://github.com/user-attachments/assets/e9382063-de60-4454-9757-5dd57e44bc0e
The text was updated successfully, but these errors were encountered: