This issue has been created
There is 1 update.
 
 
FullCalendar Macro / cid:jira-generated-image-avatar-2dcff9a2-241a-4294-b86e-ce442e61f8d6 FULLCAL-79 Open

Event times shift since v2.4.0

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-19858b66-38d9-4f67-9f1a-89915e304c56 Nikita Petrenko created this issue on 13/Feb/25 15:19
 
Summary: Event times shift since v2.4.0
Issue Type: cid:jira-generated-image-avatar-2dcff9a2-241a-4294-b86e-ce442e61f8d6 Bug
Affects Versions: 2.4.2
Assignee: Unassigned
Created: 13/Feb/25 15:19
Labels: regression
Priority: cid:jira-generated-image-static-blocker-d6c3fd54-4702-48a8-a9db-efde3427a7a9 Blocker
Reporter: Nikita Petrenko
Description:

Prerequisites:

  • XWiki 14.10.20
  • latest version of FullCalendar (for reporting time v2.4.2)
  • calendar with events

Steps to reproduce:

  1. import calendar into XWiki page via syntax 
    {{calendar iCal=" URLtoICS"/}} 
  1. save the page

Actual result

The event from calendar will be shifted for 1 hour (start and end time) while in Google Calendar those events will have correct start and end time.

Expected result

The event from calendar has same layout as in Google Calendar

 Note

I labeled this issue as blocker, because I'm not reproducing it if I downgrade to version 2.3.2, the bug arises since v2.4.0.

 
 

1 update

 
cid:jira-generated-image-avatar-19858b66-38d9-4f67-9f1a-89915e304c56 Changes by Nikita Petrenko on 13/Feb/25 15:22
 
Description: h3. Prerequisites:
* XWiki 14.10.20
* latest version of FullCalendar (for reporting time v2.4.2)
* calendar with events

h3. Steps to reproduce:
# import calendar into XWiki page via syntax 
{code:java}
{{calendar iCal=" URLtoICS"/}} {code}

# save the page

h3. Actual result

The event from calendar will be shifted for 1 hour (start and end time) while in Google Calendar those events will have correct start and end time.

h3. Expected result

The event from calendar has same layout as in Google Calendar

h3. Note

I labeled this issue as blocker, because I'm not reproducing it if I downgrade to version 2.3.2, the bug arises since v2.4.0.