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

Request Archiver Enhancement: Ajax error is misleading/vague when destination room is frozen #224

Open
Tyler-H opened this issue Aug 7, 2023 · 1 comment

Comments

@Tyler-H
Copy link
Contributor

Tyler-H commented Aug 7, 2023

After SOCVR was re-opened, I encountered this error when trying to move messages to the Graveyard:

$.ajax encountered an error moving some posts. See console for details. error: Not Found.

and in the console:

AJAX Error moving some posts
- status: error
- error: Not Found
- targetRoomId: 90230

image
image2

Upon investigation, I found that the graveyard was frozen, so only moderators could move messages into it. Once the graveyard was unfrozen, the error disappeared and I was able to move messages again via the script.

If a destination room is found but is frozen, can the error message be updated to indicate that, rather than indicating a 'not found' error?

@makyen
Copy link
Contributor

makyen commented Aug 7, 2023

Is there anything in the AJAX response from SE/SO that provides better information? I thought it was just forwarding the error declared in the AJAX response, but there might be more information. Beyond that, it would be significant work to determine the exact state of the room. OTOH, additional text could be added to the alert letting the user know that the problem could be that they just don't have access to post messages into the room.

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

No branches or pull requests

2 participants