FlatPress support forum

Posted: **Wed Mar 30, 2022 3:58 pm**

Hi,

last week I did a test install of FlatPress and configured time offset to +1 to get the correct time in entries.
Today I created a test comment on one of these entries and noticed, it the comment's time stamp is one hour off. I had to change FlatPress' time offset to +2 for the next comment.
Do I really have a change the time offset twice a year?

Can anyone confirm this?

Posted: **Sun Apr 17, 2022 8:06 pm**

Anyone?

Posted: **Thu Apr 28, 2022 12:23 pm**

Hello, everyone

Wow, 1 month and nobody responds? I'm almost afraid that nobody takes a closer look at what they're actually installing.

We both (bttr and I) have already dealt with the topic.
I still suspect that FlatPress's handling of the time is unfavorable (not to say wrong) from the outset. You set your "time zone" in the configuration, Flatpress saves it (probably) in a corrected form (I haven't gotten around to taking a closer look at it yet).

The result is definitely confusing. In my case (CET Berlin +2h) the display on the website is correct, plugins are 2h behind and my FeedReader 2h ahead ... you're confused? Understandable!

So, 8 a.m. I write a post, for some plugins it's only 6 a.m. and for my FeedReader it's already 10 a.m. That's... kinda crazy

Why is this happening? With the plugins, tried with fbstats, which I found somewhere on the web, it's not tragic, but shows that plugins sometimes ignore the correction, which is more of a problem with the plugin and not important in this case.

For me it's worse with the feed. A time is transmitted here which is apparently not marked as CET (which would not matter if the corrected time were not transmitted). The reader knows - for me it's CET Berlin, so I have to add 2 more hours ... and the feed is ahead of its time.

Alright, I'm done confusing

see you later

Posted: **Mon May 02, 2022 1:05 pm**

I just ran my RSS feed through the validator because of the Discord topic. I think that's why I got the wrong time in the reader.
To test it yourself: https://validator.w3.org/feed/check.cgi ... %2Frss2%2F

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 21, column 46: Implausible date: Mon, 02 May 2022 14:14:28 +0000 [help]

<pubDate>Mon, 02 May 2022 14:14:28 +0000</pubDate>

Posted: **Tue May 03, 2022 7:23 pm**

As you're currently rebuilding your site w/o FlatPress, the validator.w3.org link doesn't work.

I have no probs here for the feed of my own site. ('This is a valid RSS feed.')

Looking for more hints about the 'implausible date" ...
https://validator.w3.org/feed/docs/warn ... eDate.html reads:
"While this date-time value is formatted correctly, it either appears to be in the future, or far enough in the past to indicate that there might either be a software error, or an incorrectly set clock, involved. ... One common error, particularly among the British and Western Europe during the summer time (i.e., during the periods of BST and WEST), is for the numeric part of the time to reflect local time and for the zone part of the time to hard code GMT."

Okay. My blog posts are a few days old, while yours were new.
There we have it again. A DST or timezone problem in FlatPress.

Posted: **Tue May 03, 2022 7:48 pm**

Unfortunately, I only have my demo installation available at the moment, on which the error does not occur. However, only the Welcome post is saved there.
https://validator.w3.org/feed/check.cgi ... %2Frss2%2F
The error does not occur here, but nothing has changed since installation. Maybe another user can test his feed in the validator.

Posted: **Tue May 03, 2022 7:59 pm**

As I guessed, the error reappeared after posting a new entry to my blog and running the validator within two hours after posting.
The validator complains, because:

I posted the entry on 21:52 CEST.
'pubDate' states +0000, which means UTC (formerly known as GMT).
Current, as of this forum post, UTC time is 19:59 only.
So, I can't have posted (past tense) an entry already on my blog at '21:52:31 +0000'. -> 'Implausible date'

Excerpt from the feed:

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Notepad</title>
<link>https://www.robertriebisch.de/</link>
<description><![CDATA[Ein privates Blog von Robert Riebisch]]></description>
<copyright>Copyright 2022, robert</copyright>
<language>de-de</language>
<atom:link rel="self" href="https://www.robertriebisch.de/feed/rss2/" type="application/rss+xml" />
<generator>FlatPress</generator>
<item>
<title>Test 21:52 CEST</title>
<link>https://www.robertriebisch.de/2022/05/03/test-2152-cest/</link>
<description><![CDATA[<p>Lorem ipsum</p>
]]></description>
<category><![CDATA[ FlatPress ]]></category> <guid isPermaLink="true">https://www.robertriebisch.de/2022/05/03/test-2152-cest/</guid>
 
<pubDate>Tue, 03 May 2022 21:52:31 +0000</pubDate>
<comments>https://www.robertriebisch.de/2022/05/03/test-2152-cest/comments/</comments>
 
</item>

Posted: **Sat Jun 18, 2022 7:58 pm**

Hi,

thanks for reporting, I need to check this...there are some more findings regarding the time zone handling of FlatPress. I opened issue 116.

All the best,
Arvid

FlatPress support forum

DST problem?

DST problem?

Re: DST problem?

Re: DST problem?

Re: DST problem?

Re: DST problem?

Re: DST problem?

Re: DST problem?

Re: DST problem?