Skip to content
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

Meal Plan Calendar Places Meal a Day ahead after Refresh #3355

Closed
stoltenbergnathan opened this issue Oct 10, 2024 · 6 comments
Closed

Meal Plan Calendar Places Meal a Day ahead after Refresh #3355

stoltenbergnathan opened this issue Oct 10, 2024 · 6 comments

Comments

@stoltenbergnathan
Copy link

Tandoor Version

1.5.20

Setup

Docker / Docker-Compose

Reverse Proxy

No reverse proxy

Other

No response

Bug description

When creating a meal plan and setting the date range the meal at first shows up on the correct dates in the calendar. After refreshing the page the meal plan moves backwards a day. When opening the edit page for the meal plan and pressing save (without changing the dates) and then refreshing the meal plan again moves back. This can be repeated until the current day.

Relevant logs

No response

@smilerz
Copy link
Collaborator

smilerz commented Oct 10, 2024

duplicate #2171

@smilerz smilerz closed this as completed Oct 10, 2024
@AlanMW
Copy link

AlanMW commented Oct 22, 2024

What @stoltenbergnathan is experiencing is a similar but different issue that I was able to resolve by adding the TZ=America/Chicago environmental variable... it should likely be a default in the compose / .env file for fresh installs.

@stoltenbergnathan
Copy link
Author

@AlanMW after setting a TZ in the .env file my problem went away.

@vabene1111
Copy link
Collaborator

while this is a fix for you who are using this only in a single timezone it appears that this must be an issue for all clients in a different timezone than the server.

I will need to look into that.

@zkhcohen
Copy link

while this is a fix for you who are using this only in a single timezone it appears that this must be an issue for all clients in a different timezone than the server.

I will need to look into that.

This issue appeared between version 1.5.15 and version 1.5.20, not as far back as November 2022. Furthermore, my time zone and configuration haven't changed between the versions.

Shouldn't this issue be reopened and tagged as a bug for tracking purposes? I'm unsure why it was closed.

@vabene1111
Copy link
Collaborator

probably should but I am drowning in issues. I have using only timezone aware datetime stamps on the agenda for #2976 and hope i dont forget it

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

No branches or pull requests

5 participants