By Guest on Sunday, 17 April 2016
Replies 6
Likes 0
Views 3.9K
Votes 0
Hi Developer,

I have a problem with the ICS file when I download it with JEvents 3.4.10 in Joomla 3.5.1

The exported ICS-file cannot be imported to the Android Program ICSDroid.
According to the website severinghaus.org/projects/icv/ the ICS-file from JEvents has a wrong tag "DTSTAMP"

Here is a example of the Event

BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:VEVENT
UID:949a79f2879942d80c47b6b44029f3d6
CATEGORIES:Communitytreffen
SUMMARY:Monatliches Treffen (Thema: Messenger)
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:\n\ntest test test testt test
aslach i.K. statt.\n\n\ntest test test

DTSTAMP;TZID=Europe/Berlin:20160417T223830
DTSTART;TZID=Europe/Berlin:20150714T193000
DTEND;TZID=Europe/Berlin:20150714T150000
RECURRENCE-ID;TZID=Europe/Berlin:20150714T193000
SEQUENCE:0
TRANSP:OPAQUE
END:VEVENT


The error from severinghaus.org/projects/icv/ is:
Sorry, your calendar could not be parsed.
Error: Error was: Error at line 15: Cannot set timezone for UTC properties
Cause: Caused by: Cannot set timezone for UTC properties

12: 	DESCRIPTION;ENCODING=QUOTED-PRINTABLE:\n\ntest test test testt test
13: aslach i.K. statt.\n\n\ntest test test
14:
15: DTSTAMP;TZID=Europe/Berlin:20160417T223830
16: DTSTART;TZID=Europe/Berlin:20150714T193000
17: DTEND;TZID=Europe/Berlin:20150714T150000
18: RECURRENCE-ID;TZID=Europe/Berlin:20150714T193000


Now comes the strange thing!
- the above event is a repeating event!! And in all repeating events this error raises.
- BUT in all single events (not repeating events) the DTSTAMP is correct!! (e.g. DTSTAMP:20160417T223830Z)

--> so I think it is a error in the export of repeating events. The DTSTAMP is exported false
--> i repeating events the DTSTAM should be in UTC

Could you fix this?

Greetings
Eugen
Hello Eugen,

I beleive the issue is down to ICSDroid not accepting Europe/Berlin as a timezone. Can you try removing the timezone and see if it imports then?

Many thanks
Tony
·
Monday, 18 April 2016 08:03
·
0 Likes
·
0 Votes
·
0 Comments
·
I beleive the issue is down to ICSDroid not accepting Europe/Berlin as a timezone. Can you try removing the timezone and see if it imports then?


Hello, ICSdroid is able to handle time zones, and unless there is an incorrect VTIMEZONE definition, Europe/Berlin shouldn't be a problem. However,


DTSTAMP;TZID=Europe/Berlin:20160417T223830


is a wrong timestamp and can't be parsed by ical4j (thus not by ical4android, thus not by ICSdroid). According to RFC 5545 3.8.7.2 (I'm not allowed to post a link), DTSTAMP must always be in UTC time format.
·
Monday, 18 April 2016 12:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry for this - this is the first time I've seen a calendar that takes any notice of the DTSTAMP value - please remove the code
$tzid
from line 423 of components/com_jevents/views/icals/tmpl/export.php so that
$html .= "DTSTAMP$tzid:" . $stamptime . "\r\n";

becomes
$html .= "DTSTAMP:" . $stamptime . "\r\n";

that should resolve the issue
·
Monday, 18 April 2016 13:00
·
0 Likes
·
0 Votes
·
0 Comments
·
@bitfire: Yes, I also think, that DTSTAMP must always be in UTC time format

@geraint: I have changed the line 423 of components/com_jevents/views/icals/tmpl/export.php and will test it (ok, my friend is testing it, because he has the problem on his android)

btw: @geraint : if the issue will be resolved by changing the line 423, would it be possible to fixe the issue in the next version of JEvents?

Greetings
Eugen
·
Monday, 18 April 2016 18:34
·
0 Likes
·
0 Votes
·
0 Comments
·
@geraint: the problem with the ICSAndroid App is fixed.
Your fix ist correct.

Please fix in it the next release of JEvents
Thanks!

Greetings
·
Tuesday, 19 April 2016 17:49
·
0 Likes
·
0 Votes
·
0 Comments
·
The change will be included in the next release of JEvents.
·
Wednesday, 20 April 2016 09:22
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post