After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 252618 - unable to view 'exception' calendar entries through connector
unable to view 'exception' calendar entries through connector
Status: RESOLVED DUPLICATE of bug 239004
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.0.x
Other All
: Normal normal
: 2.0.1
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2004-01-06 00:33 UTC by Nathan Neulinger
Modified: 2004-09-09 12:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nathan Neulinger 2004-01-06 00:33:02 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Try to view or create an exception calendar event. There is no option
for this, and it always shows you the underlying event. This makes
evolution useless for viewing a calendar maintained by other people. 
2. 
3. 

Actual Results:
Always shows the recurring event instead of the exception.

Expected Results:
Should prompt for which one to show. 

How often does this happen? 
Every time.

Additional Information:
Using connector against e2k. OWA correctly prompts for the exception entry.
Comment 1 Dan Winship 2004-09-02 19:00:22 UTC 
hopefully fixed in 2.0... needs testing
Comment 2 Sarfraaz Ahmed 2004-09-09 12:29:48 UTC 
This is similar to 39004. For recurring meetings, if an exception is
deleted, then the behaviour is as expected. But, if an instance of a
recurring appointment is modified to change its time, etc, then
exchange doesnt seem to read the non-recurring event [ the moveable
one ] from the server. It also doesnt read the exception for that
moveable event and thus displays all the recurring events unchanged.

*** This bug has been marked as a duplicate of 239004 ***