Skip to content
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.

fix datetime issues with CFP #476

Closed
bridgetkromhout opened this issue Apr 10, 2017 · 4 comments
Closed

fix datetime issues with CFP #476

bridgetkromhout opened this issue Apr 10, 2017 · 4 comments
Labels
Milestone

Comments

@bridgetkromhout
Copy link
Contributor

Expected behavior

CFP would remain open through end of day local time (in the absence of a hour/minute setting which we don't yet have). Not actually expected - just incorrectly assumed.

Actual behavior

After midnight UTC, CFP appears closed on deployed site even though end of day isn't yet reached in the local TZ. Note that Minneapolis is missing on the deployed site but still appears locally. Conclusion: datetime is sadness.

screen shot 2017-04-09 at 7 26 24 pm

screen shot 2017-04-09 at 7 26 33 pm

Reproduction Steps

Set a CFP date to closing on a given day, and check after UTC-midnight.

@mattstratton mattstratton modified the milestone: Next Tasks May 11, 2017
@bridgetkromhout
Copy link
Contributor Author

This is related to many other issues that we're probably going to have to solve with a real datetime. Le sigh.

@mattstratton
Copy link
Member

Truth be told, as annoying as it is, having the time will actually help us a bit with some additional features (regarding knowing exactly when something ends, like CFP's, etc)

Plus I have a sneaking suspicion this will solve our occasional event ordering problem.

@bridgetkromhout
Copy link
Contributor Author

bridgetkromhout commented Aug 24, 2018

Anything we fix, let's document in https://github.com/devopsdays/devopsdays-theme/blob/master/REFERENCE.md#date-related-fields too.

GitHub
devopsdays-theme - Hugo theme for devopsdays.org

@bridgetkromhout
Copy link
Contributor Author

This is solved by devopsdays/devopsdays-web#5213 - thanks, @tgross!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants