TimeZones

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter joshuacollinson

    (@joshuacollinson)

    Hi,
    Ignore the above, thanks.

    I got it working, but now it says my server is 46 years out of date?

    I enabled the debug – because the rule wasnt showing, and this is what i see:

    Notice

Debugging has been turned on for a shortcode on this Post/Page. Only website users who are currently logged in and can edit this Post/Page will see this. To turn off this message, remove the debug attribute from the shortcode.

The show attribute is not set.

The hide attribute is currently set to: 19/01/2016 13:40 Europe/Vienna,
The Timed Content plugin thinks the intended date/time is: Tuesday, January 19th, 2016, 1:59 PM GMT <strong>(46 years ago.)</strong>.

Current Date/Time: Tuesday, January 19th, 2016, 12:59 PM UTC
Content Filter: timed_content_filter

    I got the date from php to see if my server is wrong, but it is fine. it says 2016.
    any idea what causes it to think it is 46 years ago?

    Thanks,
    Josh

    Plugin Contributor K. Tough

    (@kjvtough)

    Interesting; I was able to replicate your issue with your date/time string. Just curious what your locale settings are w.r.t. dates/times. What happens if you restate your date/time in another format (or by using the Timed Content dialog in the editor)?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘TimeZones’ is closed to new replies.