View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004375 | SOGo | Web Calendar | public | 2018-01-22 02:38 | 2018-04-04 21:06 |
Reporter | satya | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 3.2.10 | ||||
Summary | 0004375: saveAsAppointment saves event on wrong day | ||||
Description | When creating a calendar appointment event using the web interface, the day actually saved to is one day behind the day passed to saveAsAppointment. POST to saveAsAppointment is attached for debugging purposes. | ||||
Steps To Reproduce |
| ||||
Additional Information | {"categories":[],"alarm":{},"delta":15,"type":"appointment","pid":"personal","summary":"Lunch","startDate":"2018-01-24","isAllDay":0,"start":"2018-01-24T17:00:00.000Z","end":"2018-01-24T17:15:00.000Z","$hasAlarm":false,"destinationCalendar":"personal","freebusy":{"20180124":{"12":[1]}},"selected":false,"isNew":true,"id":"78A4-5A654B80-B-5DD3F10.ics","classification":"public","sendAppointmentNotifications":0,"startTime":"12:00","endDate":"2018-01-24","endTime":"12:15","dueDate":"","dueTime":"","completedDate":""} | ||||
Tags | No tags attached. | ||||
Admins, could this be changed to Backend Calendar, since moving an event seems to work correctly? Also, if it helps, the server is configured to |
|
This usually happens when: 1- you're not using GNUstep from our depo if you're using CentOS/RHEL |
|
This misbehavior is occurring despite a reinstall of the sogo and sope packages. This was done using trizen under Arch Linux. |
|