Add notification about replying to a very old post

[#1]

Have more faith Hmm, I'm afraid there is little of that left.
I will have a look on Staging.

Oh, and I don't think that there are many cases where replying to a a very old thread should be disallowed. In cases where it might not be an appropriate thing, there is the Report to Moderator option, where it can be reviewed and the post (and any replies) moved to their own thread with appropriate mod notes.

[#2]

It won't stop someone replying. All it will do is provide a message warning that the thread hasn't been replied to for 120 days.

[#3]

I thought that it was quite clear it was only going to be a warning from messages 13 & 14.

I was just responding and giving my opinion on an earlier suggestion about the possibility of stopping posts to old threads. I would have thought that was obvious from the context of my reply and reference to the 'Report to Moderator' comment.

[#4]

As an aside what is the SP on the image browser lightbox affair? If I click on that image there is nothing that lets me see it at its native resolution so it is shrunk to my screen height, which means I cannot read the text all that well.

I've also noticed that the lightbox breaks the history as well. Pretty major bug there I think.

Also I replied to @jaread83 (the dropdown for this doesn't work either, it's somewhat haphazard at actually finding members, either none found or not the ones you were expecting) and the post shows no reference to that so what is the point in the reply button on each post, there should be some reference to the post that it was in reply to. The actual relevant part of the post I was replying to was this bit but I was trying to avoid quoting it but it seems to be the only way to give this post relevance;

---

@jaread83 wrote:

---

 In addition an inverse problem to the above is that there is no "general reply to thread" option or the like, so it's a bit neither one nor the other, with none of them really doing what you expect.

[#5]

Don't forget it hasn't been implemented here yet, that's an image from the test site.

As far as the drop-down list of @ it should initially prompt you with the names of those who have posted in the thread. To get other names you need to type at least 3 (consecutive) characters of the name, but the major problem is that with the much larger user base here the list does not drop-down enough / is not scrollable.

[#6]

---

@Anotherone wrote:

Don't forget it hasn't been implemented here yet, that's an image from the test site.

---

Yeah, that bit I get. The actual image itself is the issue. The rest of the post is the several bugs/features I encountered whilst trying to reply!

@IF I type @ I get a list of members in this thread, if I then start typing it seems to search for members NOT in this thread so for instance if I type @JA it returns no matches. The @ thing also hijacks your cursor so you cannot just type you replay and include a mention for the forum to parse as you post without carefully checking what you have accidentally typed. I think the cursor skips back a space when you hit space and then type a another character after typing @someone.

[#7]

---

Anotherone wrote:

To get other names you need to type at least 3 (consecutive) characters of the name, ......

It's a bit worse than that?  It looks for the first 3+ chars you type anywhere in the name and still makes a mess of it!  Try typing the first 1, then 2, then 3, then 4, then 5 chars of Anotherone to see what I mean   Not the most intuitive of searches.

[#8]

Just typing the @ symbol will list all participants in the thread. After that it relies on having the first 3 characters. I'd prefer there to be more results as trying to tag someone with a generic name yeilds far too many users. I agree that could be better implemented.

So to answer @Lurch, sorry about the screenshot. I literally used the Firefox dev tools to take a capture of the entire page and when uploading to this system it compressed it. Sorry about that, I should have taken a screenshot of the area of interest.

Back to the topic though.. I have spoken to @LouisaMartin about this and I have got this to be part of the frontend changes I have been doing even though it wasn't scheduled in and I decided to do this anyway (hooray). I will be posting details of all of that soon, just trying to find out a date I can release the changes to the live site so I can put those in the thread.

[#9]

Just going through the threads that were mentioned in the latest update thread.

A fix for this issue will be pushed live today, you can view details of the fix on the update thread here. See the eighth item on the 'regular changes' section.

[#10]

Another one working a treat, so @Oldjim is going to be busy marking all his threads as fixed