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

get a 500 error when a reviewer is disabled #9841

Open
forgive38 opened this issue Mar 28, 2024 · 3 comments
Open

get a 500 error when a reviewer is disabled #9841

forgive38 opened this issue Mar 28, 2024 · 3 comments

Comments

@forgive38
Copy link
Contributor

Describe the bug
If a reviewer is assigned to a submission and this reviewer became disabled, get an error 500 for reviewerGrid.

To Reproduce

  • assign a reviewer on a submission (you can accept the review or cancel review)
  • disable the reviewer in Users &Roles
  • Come back to the submission, check error, you get an error 500

What application are you using?
OJS 3.4 (test-drive)

Additional information
this bug has a very low priority ;) maybe showing a message near the reviewer name like "User disabled" could be useful

@touhidurabir
Copy link
Member

@forgive38 unable to produce the issue on latest checkout of stable-3.4.0 for OJS following the reproduction steps . I can still access/view the reviewer details for the submission in the review stage of workflow . Or am I missing something ?

@forgive38
Copy link
Contributor Author

try
https://ojs34.testdrive.publicknowledgeproject.org/index.php/testdrive-journal/workflow/index/968/3
I disabled reviewer Claris Clevinger. and for the reviewerGrid you can't see the grid because of error500
(I hope you can see this before testdrive will be reset)

@touhidurabir
Copy link
Member

@forgive38 probably something going odd with the test drives . I can see that this issue exist there but can not reproduce it in the latest checkout of stable-3.4.0 . Also during test I noticed that if you disable any user, then the user view does not load also which I was not able to reproduce in the latest checkout of stable-3.4.0 . wondering is there certain setting/configuration in the test drive causing these issues .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants