When someone makes a submission to our journal, the buffering wheel never stops spinning (never, even after a few hours). This is despite the submission having been made and registered as a submission, with automatic emails having been sent.
What is most likely happening is that the PHP backend is returning some unexpected error (5xx), which is incorrectly handled by the UI, which causes UI to get stuck. I will address the error handling to display the error instead of getting stuck.
But I suspect that it won’t resolve the underlying problem, which is that the PHP backend is likely returning some crash error and probably have reason to do so.
To identify the underlying cause of that it would help if you can provide some additional information.
Does it happen for every submission on your install?
If not - do you have some particular submission that would trigger this problem consistently?
In other words if we could reproduce it - that would help us to address it accurately.
Another place to look at are web server log errors and find some errors coming from the PHP happening in the time of submission being sent.
I am having this issue as well. There seems to be an associated error with the wizard in the “comments for the editor” box. I ran a test submission and anything entered into this box does not carry over into the submission as a “pre-review discussion” as it should. It shows a blank line instead where the discussion message should go. Perhaps this is what is causing the submission button to get stuck.
Unfortunately I am still not able to replicate it. I did try to create submission with “comments for the editor” and submission work as expected, including starting the “pre-review discussions”.
