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
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
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?
The text was updated successfully, but these errors were encountered:
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.
After SOCVR was re-opened, I encountered this error when trying to move messages to the Graveyard:
and in the console:
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?
The text was updated successfully, but these errors were encountered: