A bug was reported where topics with a 6-month auto-close timer incorrectly display “This topic will close a few seconds after the last reply,” despite closing on schedule. The issue appears only in older topics, not newly created ones, and resolves temporarily when opening the topic timer modal. martin investigated and confirmed the bug stems from an incorrect migration affecting the duration and duration_minutes fields in the database — older topics have duration = 43 20 and duration_minutes = NULL, while newer ones correctly use duration = NULL and duration_minutes = 259200. martin identified the root cause in a prior migration and advised upgrading to at least commit 18da1d5 or running manual SQL updates to fix affected topics. A UI improvement replacing manual hour-to-month calculations with a new duration component was also introduced in a merged PR. Overgrow confirmed the fix and plans to upgrade promptly.
Now the troubling part: I don’t see it in every topic. Some are correct some are not. Also some topics created after the update show the error (so it is probably not due to migration).
Fortunately it only displays that it will close in few seconds, in reality topics are closed on correct schedule (e.g. 6 months)
Hmm that is interesting that it fixes itself when you open the modal. I will have a look into this. Also, I have a PR open to introduce a new duration component; I am glad you opened this issue because now I can also replace this:
I’ve done some more investigation (still on f6e6ae5e24) and found that only old topics exhibit this strange behaviour so the migration bug probably will be the case after all..
Old buggy timers have duration = 4320 and duration_minutes = NULL.
New ones working well have duration = NULL and duration_minutes = 259200