-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Date Mismatch from Tags Pages to Article itself and Main Page #864
Comments
Hmm, not sure why are you getting different dates. I checked and verified that they all use the the same |
I am going to give this a try and report back on my findings! Thank you for getting back to me!! |
I tried this and it still has the wrong dates is there any particular manner in which I should try this? I have it uploaded via Vercel and tried to delete .next locally and repush it after rebuilding it. In the dev server the dates were all wrong by -1, but when I reuploaded to Vercel it was the same. Do I need to do this differently? I have a knowledge disconnect between how the data is stored locally versus on Vercel upon uploads. @timlrx |
@timlrx I've experienced the same bug today. Did you ever discover the reason for this? One thing I noticed, is that it seems as though the issue isn't in the static date. When the page first loads it loads with the correct date, and then some javascript must run that rolls all dates back one day. I've tried to investigate, but can't get much further than that. If you want to see for yourself, check out https://aheadinthecloud.com/tags/how-to/ and refresh the page a few times while looking at the dates, you'll see them flicker between the two times. |
Describe the bug
The dates are not matching up on certain pages with the date set in the articles themselves in .mdx.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The dates are consistent and match the .mdx set dates across all pages.
System Info (if dev / build issue):
Browser Info (if display / formatting issue):
The text was updated successfully, but these errors were encountered: