Closed fivitti closed 4 years ago
We need fix it
Yes. Fixed in 960f042d1474bb1039c2c5b0e1807aec27bb5f98
and add unittest for check if it works.
No. The problem was caused by the timestamp being checked on the file itself (without full path). This only happened if you ran the server from a different directory than the sources. This is a marginal deployment nuance. IMHO writing unit-tests for this would be both tricky and a waste of time.
Version and timestamp isn't present on production server. We need fix it and add unittest for check if it works.