2

I don't know how to reproduce this error (maybe the error happens the first time one runs into that error), but I encountered this error:

"You have too many pending edits. Further edits cannot be submitted until prior edits have been approved." on https://serverfault.com/q/710576/126950

instead of:

The same message appearing as an error popup instead of as a separate page

I experienced this while using Brave+Windows.


Plain text of the error message:

You have too many pending edits. Further edits cannot be submitted until prior edits have been approved.

2
  • 5
    Did you by any chance load the page before you ran out of pending edits, and then try to edit the post? Chances are that the page didn't have a chance to load in the status through WebSockets yet, and thus sent you to the separate editor page which loaded the error message. Commented Oct 1 at 2:06
  • 2
    @SonictheAnonymousHedgehog "Did you by any chance load the page before you ran out of pending edits, and then try to edit the post?" Yes. Thanks, your explanation makes sense. Commented Oct 1 at 2:10

2 Answers 2

9

As you confirmed in the comments, you loaded the post you were trying to edit before you reached your edit limit, then after submitting suggested edits to other posts in other tabs or windows, you tried to edit this one.

I do believe that whether you can suggest an edit to a post is updated in the WebSocket pings, but that had likely not loaded yet when you tried to edit (or the connection was closed somehow). As such, clicking it sent you to the post editing page (/posts/[x]/edit), which loaded with the plain text error message instead of the editing form.

7

Just tacking on an official answer that this is pretty much .

There are a couple of scenarios where this can legitimately occur:

  1. The window is opened, suggested edit is raised elsewhere that hits cap, you click the edit button on the original page.
  2. If you middle click to open in a new tab, we actually bypass the inline JavaScript handlers.
  3. You manually navigate to the edit URL.

We try to load the popup notice on the client, but since client side stuff can easily be avoided as well, we also verify on the server when the edit route is loaded to do one last check before rendering the edit page.

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.