New Comment Posts Never Appear

Anyone else having problems with posting new comments to an existing topic on this site ?

Over the past 4 days I have attempted to respond to a few existing posts on the site. I type the response and click the POST button. The entire post disappears (as if it has been accepted), but the response does not show at all. The page simply reverts to the 'new' post blank / unfilled page.

I have seen this happen occasionally on previous instances, but it has seemingly been a 'one-off' instance, where re-posting solves the problem.

In the case of the last few days, the posts never appear. I don't believe that this is a 'new' problem, but something that has existed since the new software / format went into public mode in July 2019 with the ET launch. I and other members have had occasion to comment on this previously.

I am aware that the board software has an issue when a post is 3 or more indent-levels down from the original post - but this is not the case with any of the posts I have had the issue with. Neither has it been a 'Cloudflare' outage issue with the site's availability.

Interesting : new post (above) lodged correctly without issue, but note - this is a new (not existing) thread.

Hi Kimshep, thanks for sharing this. Can you please let us know which topic you posted on so we can see why they are not showing? I know sometimes they can get caught in the automated spam filter.

This happens to me on occasions when using Safari on the IPad, there is also a lag when typing and the page stalls at times, then hit post and it just disappears, doesn’t happen on chrome.

Happens to me too - posts haven't gone through, but also votes aren't counted sometimes I re login and out and it works - I think it's browsers issues on the phone rather then the site. Bit it started happening about 2 months ago.

Hi Sid,

Thanks for your prompt reply. A good example is a post reply to the discussion of "Qantas Price Gouging". I lodged a reply to member "DY"s comment, which did not go through. Fortunately, I had a 'cut & paste' of my reply active and tried a repost. That did not work, so I tried a few more times, through sheer frustration. In all, there may be 5-7 identical replies, floating around and non-assigned. None have found their way to the thread.

Unfortunately, this issue is inherently unpredictable, but it does seem to occur on a continuous - but random - basis. Also, it makes no difference whether I click on the POST button using either my Microsoft Mouse or the inbuilt track-pad.

The environment is a premium name-brand Intel Core I-5 processor, Windows 10 64 bit (all updates applied). Browser - problem has occurred with Windows Edge, Firefox and Google Chrome (all current 64 bit versions). Malware Bytes, CCleaner and Microsoft Security are all resident.

This morning I was answering a post of 'KW72' regarding a comment made, advising users to avoid QF and instead use UA and DL instead. This was in the "Qantas Back To Selling International .." thread. The initial response was composed and did not process when POST was clicked on. I subsequently initiated this problem discussion. After lodging this successfully (note: a NEW post, not an answer or response to an EXISTING post) I then decided to again attempt to respond the the KW72 post. Slightly different wording, but this time the post worked correctly.

• Hi Sid,

NOTE: THIS reply also failed at 2:34pm ESDT

Thanks for your prompt reply. A good example is a post reply to the discussion of "Qantas Price Gouging". I lodged a reply to member "DY"s comment, which did not go through. Fortunately, I had a 'cut & paste' of my reply active and tried a repost. That did not work, so I tried a few more times, through sheer frustration. In all, there may be 5-7 identical replies, floating around and non-assigned. None have found their way to the thread.

Unfortunately, this issue is inherently unpredictable, but it does seem to occur on a continuous - but random - basis. Also, it makes no difference whether I click on the POST button using either my Microsoft Mouse or the inbuilt track-pad.

The environment is a premium name-brand Intel Core I-5 processor, Windows 10 64 bit (all updates applied). Browser - problem has occurred with Windows Edge, Firefox and Google Chrome (all current 64 bit versions). Malware Bytes, CCleaner and Microsoft Security are all resident.

This morning I was answering a post of 'KW72' regarding a comment made, advising users to avoid QF and instead use UA and DL instead. The thread was "Qantas Back To Selling US ". Replied to KW72's comment and hit POST. This failed and content of my post disappeared. I then decided to lodge a report (this one) advising of the problem. New post - went through fine. I then decided to have another go at re-posting a response to KW72. This time, the post (which was a reply to an existing post) went through correctly.

Whilst composing THIS specific reply, clicking on POST failed - as noted at the beginning of this POST (at 2:34pm). Any other info - please ask.

My response to your post above has failed twice in this session. Once at 2:34pm ESDT and a further 'rebuild' attempt at 2:34pm. Both posts have details of my personal setup and version details of software / browsers. Hopefully, you'll find a copy of it somewhere in the detritus. Frankly, this is becoming particularly annoying and a real turn-off on a site that I generally enjoy.

Sid,

I have tried and failed 3 times to reply to your question above. Look for abandoned posts at 2:34pm, 2:43pm and 2:48pm ESTD.

Each response has been a direct, sub-level reply to your question and each has failed. The (time) replies detail the environment that I use, so should be easily identified in the detritus of 'abandoned / rejected / dumped' posts.

This really is becoming a significant deterrent to using a site which I normally enjoy.

So, I have discovered that a top-level post seems to work consistently.

It is posts which are (sub-level) replies to other posts which exhibit the problem. Chris previously explained that your software had known problems with 3rd level-down posts, but apparently this is now also applying to simple replies to top-level posts.

Please note that I am experiencing the problem on a high-end 64 bit laptop, configured with Windows 10 (64 Bit) and Windows Edge, Firefox and Google Chrome. All software is updated daily for updates, and Malware Bytes, CCleaner are installed and updated automatically.

I do not use a cell phone to reply to articles, at all. That's another world of pain, in it's own right. Anyone else using an Android handset with Google Chrome seeing a story on South African Airways' $2.3B Bailout as one of the top leading articles? LOL

Thanks Kimshep, we are looking in to it now.

Could you please also share where you are seeing the SAA Bailout story as one of the top articles?

It would be extremely unlikely that your client hardware and software (laptop, device, os) would have anything to do with what you are experiencing. This is a moderated blog and so the issues are at the server end and what the web administrator has setup. Perhaps your comments were censored for some reason, or your postings are flagged for review before being accepted or removed. There is obviously human intervention.

Hi Sid,

The issue with cell phone and the old SAA Bailout article as a prominent lead article is as follows:

Medium level 10 month old Android-based cell phone, with Google Chrome loaded as the default Browser.

Note: the Operating System is Android 7.1, which could be part of the problem. However, there is no offered upgrade path to Android 8 or higher.

On the Home page, under "Recommended News", the first article is "Qantas Closes Bookings on US,UK flights to October 2021". The next item is the "South African Airways to fly again, with $2.3bn Govt bailout".

The NEWS section at the top of the page lists today's articles:

"Government hits back at Qantas on overseas flights"

"5 things to know about Emirates' new premium economy"

"AirNZ adds Honolulu .. "

" Qantas replaces SYD-LHR Airbus A380with Boeing 787" etc.

It is the RECOMMENDED News heading / section that is not updating.