-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All dates being set to 1969 #31
Comments
Could you please provide a screenshot, and the address of one of the feeds you are using? |
The feed: http://feeds.reuters.com/reuters/topNews |
Just for background, this is running against the dev version of FreshRSS |
@Asara Hum, I cannot immediately reproduce the bug you are facing (see screenshots).
|
OS: Debian 3.16.39-1+deb8u2 x86_64 GNU/Linux PHP: 5.6.30-0+deb8u1 Database: PostgreSQL Android version: Android 6.0 gmp was not installed but I installed and reloaded apache, but still nothing. The dates show up fine on the browser side though. |
Hum, there should not be any problem with this config. I am away from my development machine for some days, but my main suspicion is a bug somewhere when combining PostreSQL and EasyRSS. Let's try to find it :-) Could you please show a few SQL lines from your entry table? Something like (change the name of your table): SELECT "id", "guid", "link", "date", "id_feed" FROM "freshrss_asara_entry" LIMIT 5; |
|
Sorry for the lag. Travelling. It looks good. Are those lines among those which had a date problem? If not, you could maybe select the lines of a given feed, or the newest ones, e.g.: SELECT "id", "guid", "link", "date", "id_feed" FROM "freshrss_asara_entry" ORDER BY "id" DESC LIMIT 10; |
It is not just one feed that is having this issue. It is all of them. No stress about the lag, appreciate the help! |
Dont mean to bother, any ideas what could be causing this? |
I am away from my main dev machine until the end of the week, so my
debugging abilities are limited, but my current guess is a bug somewhere in
the interaction between PostgreSQL and EasyRSS, because each of them
individually work fine in another context.
If you are willing to test a little bit, I can send you a piece of code
tomorrow to log the JSON responses and hopefully isolate the problem.
Le 17 juil. 2017 20:40, "Amarpreet Minhas" <notifications@github.com> a
écrit :
… Dont mean to bother, any ideas what could be causing this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA9ixHieUV49cfctx9XjUZd5yr7QQQI3ks5sO6qXgaJpZM4Ny-O->
.
|
Always willing to debug! :) Just give me some instructions and I'll help out however I can. |
👍 Please try with this file https://github.com/Alkarex/FreshRSS/blob/debug_api/p/api/greader.php which logs a bit more info Alkarex/FreshRSS@f57c549#diff-d820fde0e95b775a390ca9bae6216979 in |
Hope this helps. Hope I cleared up any personal info as well :x |
Thanks @Asara |
Hey! That seems to have fixed it. Thanks so much @Alkarex |
Currently using 2017-xx-xx FreshRSS 1.7.0-dev on the server side, all of my items are being displayed as an epoch time of 0. Not sure how to go about debugging this.
On the webui of FreshRSS all dates seem to be appropriately displayed, but articles downloaded to EasyRSS show them as my timezone (EDT/UTC-4) 1969.
The text was updated successfully, but these errors were encountered: