Skip to Content

Unable to edit own comment in a blog

I am trying to correct a typing mistake in

The link from the edit option is:

After pressing the button 'Update Comment" I encounter this message:

I was not logged out. I already tried logging out, closing the browser, clearing all data (I use private browsing mode by default, anyway).

I encounter the same error message in Firefox ESR 52.5.2, Firefox 57.0.2, Pale Moon 27.6.2, Google Chrome portable 63.0.3239.84 and IE11 (Windows 7, 32-bit)

My user is not a moderator (I do not know if this makes any difference).

I have encountered this problem before, but I attributed it at that time to the existence of subsequent comments - in this example there are none.

Would somebody with user authorizations similar to mine check for what browser/OS combination editing own comments in blogs does not result in such error and help me figure out what settings I need to adjust on my end, please?

In the web console I see as response to : You are posting comments too quickly. Slow down.

If this is indeed the reason why I cannot edit my own comment - the first problem is that the error message that I see (from the first screenshot) does not correspond to the root cause, which makes it useless.

The second problem (assuming that the response in the web console may be the correct one) - I have absolutely no idea how long time should pass between edit attempts so that I can submit an edited the comment - 5 minutes, an hour, a day?

update-error.jpg (9.6 kB)
response.jpg (13.8 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 19, 2017 at 09:53 AM

    I have already reported this issue to Mynyna Chau a few days ago (the issue disappears after about one hour delay). And she told me it was reported to Community IT support.

    Hope that it will be solved in a reasonable time.

    Add comment
    10|10000 characters needed characters exceeded

    • Hey guys,

      We're still investigating to see if this is related to a known WordPress functionality or something more sinister. Obviously, there is an issue here with the error message relating to the backend functionality that is causing the issue. We'll get it sorted. Thanks for reporting :)