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

Calendar - Event From External calendar scheduling coming with incorrect Timezone #487

Open
leaofelipebr opened this issue Nov 23, 2023 · 7 comments

Comments

@leaofelipebr
Copy link

Hi,

My OnlyOffice is configured with the America/Sao_Paulo timezone.
When I send an calendar scheduling, it is sent with the correct time. But when I receive a calendar scheduling from a third party, such as Google Calendar or Outlook, they are added one hour less.

Is it a bug or is there something I can do?

Thank you in advance.

Version:
Control panel: Current 3.5.0.516
Community Server: Current 12.5.2.1848
Document Server: Current 7.4.1.1

@Carazyda
Copy link
Member

Hello @leaofelipebr we can't reproduce your problem. Please describe in more detail how you create an event in Google Calendar, do you choose the correct time zone?

@leaofelipebr
Copy link
Author

Hello @Carazyda ,

1 - I access Google calendar and create a new event. In the example, December 5th at 10am until 10:30am and I send it to my email registered in the workspace.
print1
2 - I receive the appointment in the workspace email app with the correct time.
print2

3 - However, in the workspace Calendar, the schedule appears 1 hour less, in the example at 9 am.
print3

4 - Timezone on my calendar is America/Sao_Paulo
print4

Thanks again for your attention.

@Carazyda
Copy link
Member

Carazyda commented Dec 5, 2023

We found the problem. It consists of events of less than 1 hour. We will try to fix this in future versions. In the meantime, you can try creating events for 1 hour.

@leaofelipebr
Copy link
Author

Events with an hour or more also reproduce the same error.

@leaofelipebr
Copy link
Author

Hi. Is there any expectation that this problem will be fixed in a future version? Thank you.

@Carazyda
Copy link
Member

Hi. Is there any expectation that this problem will be fixed in a future version? Thank you.

Hello @leaofelipebr the fix is ​​already included in version 12.6.0. Have you updated? Is the issue still there?

@leaofelipebr
Copy link
Author

Thanks for the feedback.
I will schedule the update for next week and update this thread with the result.

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

2 participants