1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Not a Bug Expiration Time Issue with Month Warnings

Discussion in 'Resolved Bug Reports' started by Amaury, Jul 20, 2015.

  1. Amaury

    Amaury Well-Known Member

    I tested this on our test site before reporting this just to make sure it wasn't an add-on or a style issue.

    When you issue a user a warning, the expiration time is the same time the warning was given. For example, if you issued a one-week warning on May 30, 2015, at 3:15 PM, then that means it will expire on June 6, 2015, at 3:15 PM. However, this doesn't appear to be the case when issuing a warning for:
    • Four months
    • Five months
    • Six months
    • Seven months

    There may be more (and it may not even be solely months), but obviously I couldn't test every single number. Those are the ones I noticed.

    Anyway, the issue when using any of the above is that it takes an hour off the expiration time. Uusing my example above again, if I did five months, instead of the warning expiring on October 30, 2015, at 3:15 PM, it would expire on October 30, 2015, at 2:15 PM.

    Here are a couple screenshots (from bottom to top) with tests:

    Warnings 1.PNG

    Warnings 2.PNG
    Last edited: Jul 20, 2015
  2. Martok

    Martok Well-Known Member

    That would be correct. It you look at the expiration dates, they are all after DST has ended, hence the times appearing to be 1 hour earlier than expected. The times are correct though.
    Amaury likes this.
  3. Mike

    Mike XenForo Developer Staff Member

    @Martok's explanation is correct.
    Amaury likes this.
  4. Amaury

    Amaury Well-Known Member

Share This Page