|
|
Not sure if there's still a problem or what it is.
Also try with 3.2.4.
If you can reproduce the issue, provide a step-by-step procedure. |
|
|
|
The problem is still there in 3.2.4 and in yesterday's nightly.
Reproduction:
1 Choose main calendar or create a new one
2 Choose Import from the context menu (scrnshot1)
3 Select an ICS file and choose UPLOAD (scrnshot2)
4 in the top right corner the message tells that a total of n events were imported in the calendar. (scrnshot3)
5 by now (I have tried this plenty of times) you should see about hundred events alone in December but none recurring ones are visible, also in the event list view when I choose All (scrnshot4 and scrnshot5) you only see the onetime events
I can provide the account and the ICS file if required
The same file is properly visible in any 2.3.x variant of SOGo |
|
ablaha
2016-12-21 06:57
reporter
|
|
|
ablaha
2016-12-21 06:57
reporter
|
|
|
ablaha
2016-12-21 06:58
reporter
|
|
|
ablaha
2016-12-21 06:58
reporter
|
|
|
ablaha
2016-12-21 06:58
reporter
|
|
|
|
|
additional information: I am currently running yesterday's nightly, and creating events works fine unless they are recurring AND allday events. I have now tried to export and import events that are NOT allday events but recurring, and these work fine ... |
|
ablaha
2016-12-21 07:15
reporter
|
Test Calendar.ics (1,834 bytes)
BEGIN:VCALENDAR
PRODID:-//Inverse inc./SOGo 3.2.4//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:Europe/Vienna
X-LIC-LOCATION:Europe/Vienna
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:21D2-585A2A80-1-23E736C0
SUMMARY:Event not allday not recurring with alarm
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER;VALUE=DURATION;X-WEBSTATUS=triggered;RELATED=START:-PT5M
ACTION:DISPLAY
END:VALARM
TRANSP:OPAQUE
DTSTART;TZID=Europe/Vienna:20161221T081500
DTEND;TZID=Europe/Vienna:20161221T091500
CREATED:20161221T071002Z
DTSTAMP:20161221T071002Z
LAST-MODIFIED:20161221T071002Z
END:VEVENT
BEGIN:VEVENT
UID:21D2-585A2B00-7-23E736C0
SUMMARY:Event allday not recurring with alarm
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER;VALUE=DURATION;X-WEBSTATUS=triggered;RELATED=START:-PT5M
ACTION:DISPLAY
END:VALARM
TRANSP:OPAQUE
DTSTART;VALUE=DATE:20161221
DTEND;VALUE=DATE:20161222
CREATED:20161221T071058Z
DTSTAMP:20161221T071058Z
LAST-MODIFIED:20161221T071058Z
END:VEVENT
BEGIN:VEVENT
UID:21D4-585A2B00-5-3EE7BE80
SUMMARY:Event allday recurring with alarm
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER;VALUE=DURATION;RELATED=START:-PT5M
ACTION:DISPLAY
END:VALARM
RRULE:FREQ=MONTHLY
TRANSP:OPAQUE
DTSTART;VALUE=DATE:20161221
DTEND;VALUE=DATE:20161222
CREATED:20161221T071136Z
DTSTAMP:20161221T071136Z
LAST-MODIFIED:20161221T071136Z
END:VEVENT
BEGIN:VTODO
UID:21D4-585A2B80-B-3EE7BE80
SUMMARY:Task
CLASS:PUBLIC
CREATED:20161221T071226Z
DTSTAMP:20161221T071226Z
LAST-MODIFIED:20161221T071226Z
END:VTODO
X-WR-CALNAME:Test Calendar
END:VCALENDAR
|
|
ablaha
2016-12-21 07:16
reporter
|
|
|
ablaha
2016-12-21 07:39
reporter
~0011059
Last edited: 2016-12-21 07:59
|
odd, I just changed the timezone to America/Toronto and all events are visible!
changing back makes them disappear again ...
I am usually on Europe/Vienna, and tested a few now also out of Asia or Austrialia, but it seems only America/* works for me. |
|
|
|
All day events have no timezone information, so it shouldn't matter if you created them in Europe/Vienna or America/Toronto.
Can you reproduce the issues on demo.sogo.nu/SOGo ? |
|
|
|
I cannot logon to the demo system for v3, users sogo1,2 and 3 do not work there with the usual pwd ... it works vor version 2 , also on the demo |
|
|
|
demo.sogo.nu has been fixed. |
|
|
|
Hi,
somehow I cannot reproduce the environment in demo.sogo.nu, because the timezone defaults to Montreal. With this it also works in my envrionment. Unless I change the timezone to anything outside the Americas ... |
|
|
|
forget the last. I have swapped browsers (from IE to Firefox), and I can change timezone in demo environment there.
Unfortunately, I cannot reproduce my problem in demo.sogo.nu, so it seems it is my system that plays up :-( Any ideas what could cause this? |
|
|
|
On which Linux distribution is SOGo installed?
Show the complete list of SOGo, SOPE and GNUstep packages that are installed. |
|
|
|
[root@mail ~]# cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)
[root@mail ~]# yum list installed sog sope gnu*
Installed Packages
gnupg2.x86_64 2.0.22-4.el7 @base
gnustep-base.x86_64 1.24.9-1.el7 @epel
gnustep-base-libs.x86_64 1.24.9-1.el7 @epel
gnutls.x86_64 3.3.24-1.el7 @base
sogo.x86_64 3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sogo-activesync.x86_64 3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sogo-ealarms-notify.x86_64 3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sogo-tool.x86_64 3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sope49-appserver.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-cards.x86_64 3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sope49-core.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-gdl1.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-gdl1-contentstore.x86_64
3.2.4.20161220-1.el7.centos @sogo-nightly-v3-rhel7
sope49-gdl1-mysql.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-ldap.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-mime.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-sbjson.x86_64 2.3.1-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
sope49-xml.x86_64 4.9-20161203_1664.el7.1 @sogo-nightly-v3-rhel7
[root@mail ~]# |
|
|
|
You're using GNUstep from EPEL - you must use our version.
Also make sure you're using the same nightly version of the SOPE and SOGo packages - this is NOT the case right now. |
|
|
|
IC, I will have to look into this. Ever since I installed SOGo I just yum update both SOGo and sope, eventually the versions diverge, this is the case also in 2.3.x, no idea why. As for the GNUstep, I'll need to find guide lines too. Will come back then. tx |
|
|
|
Closing the ticket for now, 99.99% sure the issue is due to incorrect software packages installed. Reopen if necessary. |
|
|
|
Sorry that I had to reopen this ticket (cannot add comments to closed case) just to say that the issue has been resolved by correcting the wrong software packages as stated by you, Ludovic. Many thanks!
Case can be closed for good. |
|
