-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix the never-ending load loop #50
Comments
|
Not fixed |
Never mind. |
I've been agonized over this issue probably far longer than I needed to (DSpace/DSpace#9884) before realizing that, if this is truly the cause of the problem (might not be), this has been a known issue with the DSpace backend for nearly two years (DSpace/DSpace#8577). If this isn't it, then there's some other problem going on with asynchronous functions not executing in the right order and causing or leading to the authorization token that indicates you're a logged-in administrator expiring. Either way, I'm not going to be able to fix this problem with the time that I have. |
(We're just going to have to wait until they fix it in an update.) |
I think I should try removing the commit where I introduced conditionally displaying the dev code. |
Huge thanks to Arta for pushing this issue up to the DSpace community. Turns out this is an issue beyond us: DSpace/dspace-angular#3584 Hoping for a swift resolution from the DSpace community developers soon. |
Never-Ending Loop was fixed yesterday and will be included in the release of 8.1. |
I'm keeping this issue open because it's been resolved and all we will need to do is upgrade to 8.1 once it's released. However, for all intents and purposes, we can consider this issue closed. |
When logged in and navigating to edit a record or create new records, sometimes (though more often than not) the page gets stuck loading. It will not stop loading until the user refreshes several times, or opens the link in a new tab. Sometimes letting the page load for several minutes then refreshing once is more useful than refreshing many times in quick succession.
The text was updated successfully, but these errors were encountered: