Fix this please

[doodle]

1. https://gyazo.com/72a315b3d4dbc84c58242b159f6438ed
2. https://gyazo.com/0d9051ebd0f0e3651894be195c6b68e3
3. https://gyazo.com/eff31f6abd0b3d0f9959a3f996dfc730
4. https://gyazo.com/79160e14a5380eaf36011e7374a3d488

 

[Harry]

This isn't exactly a bug - the this happens when someone bumps a thread (so the last reply is shown).

What do you suppose should happen in this instance?

 

[doodle]

This isn't exactly a bug - the this happens when someone bumps a thread (so the last reply is shown).

What do you suppose should happen in this instance?

It is a bug? It says the user replied 6 minutes ago, when they replied over a month ago.

 

[Harry]

It is a bug? It says the user replied 6 minutes ago, when they replied over a month ago.

It's always been like that, so it's not a bug per se.

I do admit, I've always found it odd but if you think the behaviour should change, it'll probably be best to make a suggestion thread instead.

 

[doodle]

It's always been like that, so it's not a bug per se.

I do admit, I've always found it odd but if you think the behaviour should change, it'll probably be best to make a suggestion thread instead.

What? Just because it's always been like that doesn't mean that it isn't a bug, it just means it's been a bug forever. I get I don't know much about websites and coding, but that definitely seems like a bug, not a feature. Why does it says 6 min ago when it shouldn't even be on the Recent Posts?

 

[Harry]

What? Just because it's always been like that doesn't mean that it isn't a bug, it just means it's been a bug forever. I get I don't know much about websites and coding, but that definitely seems like a bug, not a feature. Why does it says 6 min ago when it shouldn't even be on the Recent Posts?

It's been an accepted behaviour for years, and there are arguments as to why a bumped thread should and shouldn't be shown in the recent posts panel. This is why I say it would be better to make a suggestion thread if you think this behaviour should change.

From Mick (https://www.mc-market.org/threads/341041/ - can't quote):

This isn't a bug, it's just how it displays when a user bumps. I'll move this to the bug report archive. Thank you.

 

[doodle]

It's been an accepted behaviour for years, and there are arguments as to why a bumped thread should and shouldn't be shown in the recent posts panel. This is why I say it would be better to make a suggestion thread if you think this behaviour should change.

From Mick (https://www.mc-market.org/threads/341041/ - can't quote):

Right, I'm saying the bug itself is that it displays the user's reply date. I think we can all agree it shouldn't be 6 minutes ago if they didn't reply 6 minutes ago?

 

[Justis]

Right, I'm saying the bug itself is that it displays the user's reply date. I think we can all agree it shouldn't be 6 minutes ago if they didn't reply 6 minutes ago?

Would you prefer we change the word “replied” to “bumped” in that message?
Whether you’re using the bump system or posting a very important response, you’re bumping the thread. So it wouldn’t be inaccurate.

The bump system alters the display order of a thread by updating the last-reply date. There is no way to “fix” the fact that the last reply date is updated, because that is the bump system itself. So if the inaccuracy of the text is to be resolved, it’ll need to be resolved by alteration of the text.

 

[doodle]

Would you prefer we change the word “replied” to “bumped” in that message?
Whether you’re using the bump system or posting a very important response, you’re bumping the thread. So it wouldn’t be inaccurate.

The bump system alters the display order of a thread by updating the last-reply date. There is no way to “fix” the fact that the last reply date is updated, because that is the bump system itself. So if the inaccuracy of the text is to be resolved, it’ll need to be resolved by alteration of the text.

Yes, that is what everyone was saying.

 

[doodle]

Whoooo caressssss

Go away lmao

 

[doodle]

no smelly

 

[doodle]

 

[Mick]

Justis' solution seems like the best way to solve this issue, but I still don't understand the need to fix such a ridiculously minor display inaccuracy.

This is just how it displays and isn't worth custom development to fix.

I'll move this to the bug report archives.