logos date mismatch?

Hello. I am confused about something and hope someone here can help. I like to use the daily devotional "Connect the Testaments" but the date that Logos says I am on is wrong. For instance, today it is 24 Aug 2016, but Logos says I should be reading for 25 Aug 2016. In other words my daily devotional feature on the Logos Home Page thinks it is a day ahead of what date it actually is. I hope that makes sense, and I hope there is someone that can teach me how to fix that issue. Thank you.

Find more posts tagged with

Comments

Dwayne, I just checked it out on my homepage and Connect the Testaments shows the 24th (which is today's date).

Is your computer clock correct? and... are you half way around the world from my central Illinois home?

https://community.logos.com/discussion/comment/842053#Comment_842053

Dwayne, I just checked it out on my homepage and Connect the Testaments shows the 24th (which is today's date).

Is your computer clock correct? and... are you half way around the world from my central Illinois home?

TC, The clock on my computer is showing the correct day and time for where I am currently located. I am half-way around the world from Illinois, although I can't say where for security reasons. I can say that it is very hot and there is lots of sand. However, that shouldn't matter. If the clock on my computer says 24 august, then the date on Logos should be 24 August as well, correct?

https://community.logos.com/discussion/comment/842268#Comment_842268

...unless there is something happening with the timezone difference from Bellingham.

Do other devotionals match your date?

https://community.logos.com/discussion/comment/842277#Comment_842277

...unless there is something happening with the timezone difference from Bellingham.

Do other devotionals match your date?

I only use the one devotional right now. When I get home to my computer, I will "start" another one or two and test that out. I will post the results of the experiment. Thank you for your interest in my issue.

https://community.logos.com/discussion/comment/842326#Comment_842326

I look forward to the results as well.

I suspect that since the Bellingham servers are what provides a good portion of the news items on the front page, they are polling the server, rather than your computer for the date.

If that's the case I would consider it a bug.

https://community.logos.com/discussion/comment/842384#Comment_842384

I think I may have figured out the problem: LEAP YEAR!

https://community.logos.com/discussion/comment/842567#Comment_842567

Well that's interesting. I would not have thought about that. But that doesn't explain why it is on the proper date on my system, but not yours. Unless of course there is a local to you reason this might be the case.

https://community.logos.com/discussion/comment/842621#Comment_842621

Well that's interesting. I would not have thought about that. But that doesn't explain why it is on the proper date on my system, but not yours. Unless of course there is a local to you reason this might be the case.

TC, yeah, I don't know what the deal is, but here is a screenshot from my reading plan. Notice how the dates got jacked up in the red circle. Any thoughts on how to fix it?

https://community.logos.com/discussion/comment/844397#Comment_844397

Disregard. I don't know what the issue was, but all I did was click "Edit" in the upper right (red arrow) and the dates realigned (red circle). I don't know what happened in all of this, but it seems to be fixed now. Thanks.

https://community.logos.com/discussion/comment/844398#Comment_844398

Disregard my disregard. It is still messed up. today is definitely not Aug 29:

https://community.logos.com/discussion/comment/844405#Comment_844405

Alright. I think I may have figured out what is going on here. This is a reading plan based on a devotional book. The book was published in 2012, which I'm guessing was not a leap year. Therefore, since the book only has devotions for 365 days, not 366, the dates got misaligned on Feb 29. I need to search the Logos Bookstore and see if they have a 2016 version of this book. I don't know if anybody has been reading this thread, but I am posting the "solution" here just incase anybody else runs into this same situation. In essence, there really is no solution except to realize why there is the 1 day discrepancy and decide if you are willing to deal with it or not.

https://community.logos.com/discussion/comment/844405#Comment_844405

I'm half around the world as well.

Reading lists update at midnight local time for me. So this is very strange...

Have you double chekced that you've set your computer to the correct time zone, and not just changed the system clock when you arrived in your new time zone?

https://community.logos.com/discussion/comment/844415#Comment_844415

Dwayne,

I'm looking through this and try as I might, I cannot replicate the issue.

Maybe.... you're special? I just don't know what to suggest.

If you create a brand new reading program with that book what happens?

https://community.logos.com/discussion/comment/844598#Comment_844598

Dwayne,

I'm looking through this and try as I might, I cannot replicate the issue.

I appreciate your trying. I wouldn't expect you to waste any more of your time on this. I am just giving up on it. It really isn't that important. I can deal with it for a few more months.

Maybe.... you're special? I just don't know what to suggest.

Oh, I'm definitely special !! LOL!

If you create a brand new reading program with that book what happens?

same, same. I tried that a few times to no avail. I'm over it...

https://community.logos.com/discussion/comment/844709#Comment_844709

same, same. I tried that a few times to no avail. I'm over it...

Have you looked at my suggestion at all?

https://community.logos.com/discussion/comment/844709#Comment_844709

If you create a brand new reading program with that book what happens?

same, same. I tried that a few times to no avail. I'm over it...

Did you try to do a reading plan covering the whole year? I would try to do a reading plan covering only today until the end of this year time-wise as well as book-wise; that should escape the leap year problem.

https://community.logos.com/discussion/comment/844869#Comment_844869

If you create a brand new reading program with that book what happens?

same, same. I tried that a few times to no avail. I'm over it...

Did you try to do a reading plan covering the whole year? I would try to do a reading plan covering only today until the end of this year time-wise as well as book-wise; that should escape the leap year problem.

Yes, thank you for the tip. The problem with that solution is that the readings will be off. It would start off today with Genesis, but I am in Isaiah.

https://community.logos.com/discussion/comment/844711#Comment_844711

same, same. I tried that a few times to no avail. I'm over it...

Have you looked at my suggestion at all?

Yes, ma'am. GTG there

https://community.logos.com/discussion/comment/844961#Comment_844961

1. Time zone settings look good, which makes this even more mysterious.

2. Note to self - change the profile picture. so I'm not gonna be called ma'am again.

https://community.logos.com/discussion/comment/844974#Comment_844974

2. Note to self - change the profile picture. so I'm not gonna be called ma'am again.

LOL! No, I called you ma'am because your name is Jan, which I went ahead and assumed was a female name. And since my momma didn't raise no scrub I call all females ma'am and all males sir.

https://community.logos.com/discussion/comment/844979#Comment_844979

LOL! No, I called you ma'am because your name is Jan, which I went ahead and assumed was a female name. And since my momma didn't raise no scrub I call all females ma'am and all males sir.

No problem. I'm used to confusion about my name. I just have never been called ma'am before. [:D]

One more piece of funny trivia: My wife's name here in Cambodia is a male name! So she tend to be mistaken for a male Cambodian. [:S]

https://community.logos.com/discussion/comment/844958#Comment_844958

Yes, thank you for the tip. The problem with that solution is that the readings will be off. It would start off today with Genesis, but I am in Isaiah.

I'm sorry I wasn't clear--you would also have to set the Reading Plan to only cover the part of the book that you haven't gone through yet. Then it would start in Isaiah today.

https://community.logos.com/discussion/comment/845196#Comment_845196

Yes, thank you for the tip. The problem with that solution is that the readings will be off. It would start off today with Genesis, but I am in Isaiah.

I'm sorry I wasn't clear--you would also have to set the Reading Plan to only cover the part of the book that you haven't gone through yet. Then it would start in Isaiah today.

Could you please walk me through how to do that? I tried, and these are the only options Logos gives me:

Thank you.

Andrew Batishko

I assume you created this reading plan using the predefined reading plan for 365-Day Connect the Testaments Plan. That plan works well when there are 365 days in the year (which is not this year).

You can edit your plan, setting it to start on Dec 31 of 2015. Then scroll down to yesterday's date, right click and select "Catch up to here". This should put everything back on schedule.

https://community.logos.com/discussion/comment/845980#Comment_845980

I assume you created this reading plan using the predefined reading plan for 365-Day Connect the Testaments Plan. That plan works well when there are 365 days in the year (which is not this year).

You can edit your plan, setting it to start on Dec 31 of 2015. Then scroll down to yesterday's date, right click and select "Catch up to here". This should put everything back on schedule.

Thanks for the advice. Funny story. I actually tried that about half an hour before you suggested it. It didn't work. This is what happens:

It thinks today is Sep 1, but Sep 1 isn't until tomorrow. I believe there is something within Logos that makes it think it is a day later than it actually is. I just don't know how to access that setting if it is even possible to access those parameters. Thanks for the input, though. I really do appreciate it.

Andrew Batishko

https://community.logos.com/discussion/comment/845984#Comment_845984

Your screenshot isn't saying that it thinks today is September 1. It's saying that today you are supposed to read the reading that is titled September 1. That's exactly what I see when I create the plan to start on January 1, 2016. But if you change your plan to start December 31st, 2015, then things will line up correctly.

https://community.logos.com/discussion/comment/846001#Comment_846001

But if you change your plan to start December 31st, 2015, then things will line up correctly.

the above screenshot is from me starting the plan on December 31st 2015

Andrew Batishko

https://community.logos.com/discussion/comment/846014#Comment_846014

OK, first off, my apologies for getting confused and providing incorrect information.

The correct adjustment would be to start the plan on January 2nd, 2016. I tried changing my system timezone to match yours, and created the plan in this way, and it all lined up. I can't see any way in the program that local timezone or time would matter at all.

Could you paste a screenshot of the top part of your reading plan (that includes the line with the settings, and includes the first few readings in your plan)? Also please include the current date and time according to your system clock.

https://community.logos.com/discussion/comment/846032#Comment_846032

Mr. Batishko,

Here is the screenshot from me trying to develop the plan on 31 Dec 2015:

Here is the same shot but starting on 1 Jan 2016:

(this was from last night which was 31 Aug. It is now 1 Sep) So, here it looks like it got fixed, right? I thought so, too. But then on the home page:

Now, the shot you asked for (starting the plan on Jan 2 2016 with a shot of my computer's time/date:

Here is the plan from the home page:

In summary: It looks like you fixed it! Thank you very much, sir!

Andrew Batishko

https://community.logos.com/discussion/comment/846142#Comment_846142

Excellent! I'm glad that fixed it.

Quick Links