Lightning doesn't work well with egroupware

RESOLVED INCOMPLETE

Status

Calendar
Lightning Only
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: raths, Unassigned)

Tracking

Lightning 0.9
All
Windows XP

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: lightning 0.9

If I accept an event in lightning, egroupware sent a mail of reject to the author of event

Reproducible: Always

Steps to Reproduce:
1.an invitation for an event is sending from somebody
2.Accept the event 
3.a mail is of reject the event is sent by egroupware

Comment 1

9 years ago
Please provide more information. What type of calendar do you use, e.g. local, ics, caldav? Do you receive the invitation via email or via invitation pane? Is the reject mail send by Thunderbird or by eGroupWare server? In the latter case why do you think it is a Lightning issue?
Version: unspecified → Lightning 0.9
(Reporter)

Comment 2

9 years ago
I juste reproduce it. I accepted an event in lightning (click on event and accept). I watch in egroupware and my statut is "rejected. I use lightning "read only" to avoid problems.

My lightning for egroupware is here http://intranet.xxx.ch/egroupware/icalsrv.php

Comment 3

9 years ago
I'd like you to export the event to the iCalendar format before and after accepting it. Maybe the comparison of both files provides more information.

How do you accept the invitation? Do you receive it via email and accept it via the calendar bar in the message pane? Or is it shown in the invitations section in the left pane in calendar view?
raths@foyer-handicap.ch, can you still reproduce this issue with Lightning 0.9 or even Lightning 1.0pre/1.0b2pre?
No response for a while now, closing INCOMPLETE. Please reopen if you can reproduce or answer any unanswered questions.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.