We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14673
    • 18 Posts
    I’m not sure if I’m just doing this wrong or what but it’s confusing me.

    Basically, I have the server time offset setting to 15 (my server is somewehere in Texas I believe and I’m in Canberra, Australia). As this screenshot shows, the "local" time setting is correct for my region.


    I’ve got a resource with a publish date of 19 Sep 2010 @ 13:00 - in my timezone that’s yesterday. Looking at the calendar in the date picker for the resource, the 20th of September has an outline around it which indicates to me that MODx knows that today is the 20th.

    If I click the today button at the bottom of the date picker, it does update it to choose the 20th.

    When I attempt to reference the publish date in my template/chunks etc, if I just use a straight call to [[*publishedon]] or [[+publishedon]], it spits out the correct date in timestamp format.


    The problem I’m finding is that if I then add the :fuzzydate filter to the publishedon call, it seems to think that the article was published today, even though the date clearly specifies it was yesterday, despite MODx apparently knowing what the currentt date is (as demonstrated above).


    Can anyone shed any light on what I’m doing wrong?
      • 28215
      • 4,149 Posts
      Can you file that as a bug here: http://bugs.modx.com/
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com