roundcube-plugins issueshttps://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues2019-01-27T07:43:13Zhttps://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues/83Not Compatible with Roundcube 1.4 beta2019-01-27T07:43:13ZNathan CoulsonNot Compatible with Roundcube 1.4 betaCalendar icon appears as a unclickable greyed out button (looks like a button), vs Roundcube 1.3 where it shows an icon and is clickable.
This also appears to not allow the display of emails when this plugin is enabled.
I was able to g...Calendar icon appears as a unclickable greyed out button (looks like a button), vs Roundcube 1.3 where it shows an icon and is clickable.
This also appears to not allow the display of emails when this plugin is enabled.
I was able to get around the disabled button by using &task=calendar, which did appear to work.https://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues/82Kolab calendar plugin - Webmail import/export calendar icons are incorrect2018-12-11T10:13:00ZGaƫlleKolab calendar plugin - Webmail import/export calendar icons are incorrect**Steps to reproduce:**
1. Visit the webmail calendar using Larry Theme
2. Look at the buttons to import/export
**Address (URL) of faulty icons:**
https://cl.ly/e221a6ac301d
**Expected behaviour:**
"Export" has an arrow going from the ...**Steps to reproduce:**
1. Visit the webmail calendar using Larry Theme
2. Look at the buttons to import/export
**Address (URL) of faulty icons:**
https://cl.ly/e221a6ac301d
**Expected behaviour:**
"Export" has an arrow going from the calendar to somewhere else, "Import" is the reverse
**Actual behaviour:**
"Export" has an arrow going into it as if you were importing information, which doesn't make sense. "Import" is the reverse.https://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues/65Migrate to new OAuth2 client ...2017-07-21T18:14:58ZDaniel Morlockdaniel.morlock@awesome-it.deMigrate to new OAuth2 client ...https://github.com/fkooman/php-oauth2-clienthttps://github.com/fkooman/php-oauth2-clientKolab 3.4 ReleaseDaniel Morlockdaniel.morlock@awesome-it.deDaniel Morlockdaniel.morlock@awesome-it.dehttps://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues/50libvcalendar.php does not handle VEVENTS with a start date but no end date or...2017-07-21T18:14:58ZRoy Thompsonlibvcalendar.php does not handle VEVENTS with a start date but no end date or durationHi,
Found this with the caldav feature, but not sure if it should really go in kolab bugzilla...
I notice when using the caldav back end against my radicale server these in the roundcube log:
[24-Mar-2015 15:59:59 +0000]: <iqquo...Hi,
Found this with the caldav feature, but not sure if it should really go in kolab bugzilla...
I notice when using the caldav back end against my radicale server these in the roundcube log:
[24-Mar-2015 15:59:59 +0000]: <iqquotvj> PHP Error: iCal data parse error: Object validation failed: missing mandatory object properties in /var/www/localhost/htdocs/roundcube1x/plugins/libcalendaring/libvcalendar.php on line 153 (POST /roundcube1x/?_task=calendar&_action=event?_task=&_action=)
I have tracked this down to VEVENTs in my calendar that have a DTSTART but no DTEND.
This check in libvcalendar.php is raising this error:
// minimal validation
if (empty($event['uid']) || ($event['_type'] == 'event' && empty($event['start']) != empty($event['end']))) {
example event:
BEGIN:VEVENT
DTSTART:20120710T230000Z
DTSTAMP:20121010T112105Z
SEQUENCE:1349868065
SUMMARY:test appt
UID:-CALENDAR-ROY-0000001055
EXDATE:
X-RADICALE-NAME:-CALENDAR-ROY-0000001055.ics
END:VEVENT
My reading of RFC 5545 leads me to believe DTEND is optional in this case, from here:
3.6.1. Event Component
....
For cases where a "VEVENT" calendar component
specifies a "DTSTART" property with a DATE-TIME value type but no
"DTEND" property, the event ends on the same calendar date and
time of day specified by the "DTSTART" property.
It looks like there should be a check for the scenario where DTSTART is a datetime and there is no DTEND or DURATION and then set end to the same value as start.
RoyKolab 3.4 ReleaseDaniel Morlockdaniel.morlock@awesome-it.deDaniel Morlockdaniel.morlock@awesome-it.dehttps://gitlab.awesome-it.de/kolab/roundcube-plugins/-/issues/1Add option to accept self signed certs from caldav server2018-02-16T18:57:22ZRoy ThompsonAdd option to accept self signed certs from caldav serverMy caldav server is on https with a self signed cert, by default the caldav driver would not connect to it.
I've worked around this by going to plugins/calendar/lib/SabreDAV/lib/Sabre/DAV/Client.php and adding:
$curlSettings[CURLOPT_...My caldav server is on https with a self signed cert, by default the caldav driver would not connect to it.
I've worked around this by going to plugins/calendar/lib/SabreDAV/lib/Sabre/DAV/Client.php and adding:
$curlSettings[CURLOPT_SSL_VERIFYPEER] = 0;
at line 331
It would be great to have an option when creating the calendar in the ui for the verifyPeer setting passed to the SabreDAV Client constructor.
Kolab 3.4 ReleaseDaniel Morlockdaniel.morlock@awesome-it.deDaniel Morlockdaniel.morlock@awesome-it.de