-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
TC-6.0.25, TC-6.0.27
-
None
-
9
-
Severity 3 - Minor
-
0
-
Steps to Reproduce
- Install Confluence and Team Calendars
- Set Confluence's timezone to a value that is not considered valid by Team Calendars, using a JVM parameter. For example, "UTC":
-Duser.timezone=UTC
- Try to import this .ics file into Team Calendars: [^example.ics]
Expected Results
The calendar either imports or displays a reason in the UI why it cannot be imported.
Actual Results
The UI shows no action when the Import button is pressed, and the dialog remains up.
Application logs show that a particular VM file cannot be found:
2018-11-21 20:07:57,826 ERROR [http-nio-8090-exec-4367] [opensymphony.webwork.dispatcher.VelocityResult] doExecute Unable to render Velocity Template, '/com/atlassian/confluence/extra/templates/velocity/calendar3/calendar-import-subcalendar-timeZoneRequired.vm'
...
Notes
From the error, we can see that the VM file does not actually exist where plugin is expecting it. In the Team Calendars JAR file, it is located in a slightly different path:
Context | Path |
---|---|
In the exception message | /com/atlassian/confluence/extra/templates/velocity/calendar3/calendar-import-subcalendar-timeZoneRequired.vm |
Within the Jar file | /com/atlassian/confluence/extra/calendar3/templates/velocity/calendar-import-subcalendar-timeZoneRequired.vm |
A related ticket to improve Team Calendars timezone detection has been raised here: CONFSERVER-57757
Workaround
Ensure that the .ics file contains a valid timezone. Definitions and examples below:
- relates to
-
CONFSERVER-57757 Improve timezone recognition for Team Calendars
- Gathering Interest
- mentioned in
-
Page Loading...