Error message when leaving comments on posts

For the past week (maybe) the following message appears on a blank page once I submit a comment.

{"success":true,"msg":"Thank you for your comment!","redirect_url":"\/could-tablets-and-smartphones-kill-the-inflight-movie-screen#comments-14145"}

Hi Mark, can you please share which browser (and version, if known), operating system or mobile device you're using when this issue appears so that we can investigate further?

I have been getting this as well

Chrome

Version 60.0.3112.113

Edit: Win7Pro

I've experienced a few (possibly related) issues when posting a comment, so clearly there are some gremlins loose in the code, our tech guys are looking into this...

Chrome - Version 61.0.3163.100 (Official Build) (64-bit)

@markpk:

This issue (among a number of others) has been happening for at least the past 2 months.

I have had issues

1. since the backend redirect - from http to https - occurred
2. inability to post a 'Community Comment' with two verified links embedded
3. identical messages similar to @markpk's (above)
4. posts disappearing into 'thin air' after receiving the obligatory 'Thank you for your post'
5. along with the internal AUSBT email system actioning /processing actual text code segments (received as error messages) in the email.

I have advised AUSBT of this and am still awaiting a response.

David, it's a great site - but it would help make it better if issue reports could be promptly addressed and responded to. As you can see, it's not just me experiencing these issues.

Here's another issue, David. Just typed out a response to the Bloomberg IFE Phone/Tablet thread and clicked on POST. The EDIT screen remained, although .. as you can see .. a 'Thank you for your post' message appears - at the bottom of the EDIT screen! I opened a new window to check if the post appeared in the relevant thread .. and it did not. So closed the new windows and went back to the original screen window. Took a screenshot of the page and then pressed POST again. Interestingly, no 'Thank you' message, but the EDIT page remained .. until I refreshed it with a good old F5 (refresh) command. Only then did the post appear. Had I not done the above and just relied on the 'Thank you' message, it would be probable that the contents of the post would have been lost in the ether.

I've had intermittent issue when posting from my phone (Safari and ios 10.3) Sometims once a comment has posted the 'edit' option never shows against the comment. This looking at the comment when logged in via my phone, via my computer (Mac OS, and Chrome) or Ipad (Safari and ios 10.1)

Hi Chris - a couple of points, based on your reply to @Thenormissin:

1. If I recall correctly, when the new website was introduced. editing of both Community and story posts was possible. Can you advise why the Edit function is now enabled only for Community posts? This, to me, doesn't seem rational. People make typos, spelling / format errors, omit words etc. quite often. It makes sense for both types (Community and editorial) of 'user' input to be editable. After all, the edit function contains a tracker / marker so that all can see where a post has been edited.
2. Second, can anything be done to 'clean up' the QUOTE function? Often, one may wish to highlight or reference PART of a quote, rather than the whole paragraph. Unless you are particularly careful with the edit tags, QUOTE functionality is particularly messy - often resulting in variations of the quote not being highlighted correctly or even the post containing a part-quote being appended to the END of a thread (rather than in answer to a particular post (above). This affects 'readability' for all users.
3. Can we have a 'Reply (without QUOTE) option, as well as WITH quote option? I wanted to reply to David's answer above, but the REPLY function only offers a 'with quote' option. It is not necessary to repeat David's full answer (which quotes my post also) again .. for the sake of a two or three sentence reply. Hence, I have not replied.

Ho Chris, TBH, I can't recall but maybe that's the case.