Topic timer does not accept values <1 hour

Bug
1

Stable channel, shallow bug.

Topic time does not accept values less than 1 hour. Has worked before, for a very long time.

  • Auto-close topic
  • Close based on last post
  • Try to set a value below 1 hour, say 0.25 for 15 minutes

One hour is a very long time for a heated discussion. We actively use values around 10 minutes to end our game chats. It works very well as the timer triggers when things start to cool down (our game topics get up to 1000 posts in a couple of hours).

Propose the fix to be backported to the stable channel. Reasoning: Old basic functionality broken.

3 Likes
2

Reproduced with 2.6.0 beta4.

2 Likes
3

@martin is planning to revamp this dialog entirely in the next version of Discourse so we will probably deal with it then.

(I was hoping it would make this release but probably not)

2 Likes
5

Just verified this in production (CDCK’s SaaS Discourse). Value of 0.1 hours was accepted (6 minutes) and topic closed accordingly.

2 Likes
6

I am glad you found this yourself, I had a reminder set to post an update here :slight_smile:

2 Likes