Auto-publish: newly-entered event disappears if another event is entered in same session



Internal Components
14 years ago
12 years ago


(Reporter: Randy Gobbel, Assigned: John Gray)





14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

Note: this may not be a libical issue, but I'm guessing that it is.

I have several calendars that are kept on an Apache WebDAV server, with
auto-publish turned on.  If I enter two events on the same calendar, the first
event disappears when the second event is entered.  Previously-entered events
are not affected.  If I quit after entering the first event, then restart, I can
enter the second event without zapping the first one.

Reproducible: Always

Steps to Reproduce:
1. Enter a new event on a calendar with auto-publish.
2. Without quitting the application, enter a second event on the same calendar.
3. Wonder what happened to the first event.

Actual Results:  
When the second event is entered, the first event disappears.

Expected Results:  
I should wind up with two events.

The .ics is being written to the server after each event is added.  I can enter
an event on another auto-published calendar without affecting the first event
entered, but if I then enter another event on the same calendar as the first,
the first event still disappears.  I do not see this problem with calendars that
do not have auto-publish enabled.

Comment 1

14 years ago
More detail: the bug only appears if auto-publish is turned on when Mozilla
starts up.  If auto-publish is turned off at startup, then turned on, I can
enter as many events as I want to in a single session, with no problem.

Comment 2

14 years ago
I also saw this when working on bug 200012. It may have been the cache issue
which was fixed with this checkin:
I wasn't able to reproduce this after the change was made.

Can you apply the change and see if it also fixes the issue for you?
Ever confirmed: true

Comment 3

14 years ago
Yes, the above-mentioned caching fix gets rid of this bug.

Comment 4

14 years ago
Fixed then.
Last Resolved: 14 years ago
Resolution: --- → FIXED


12 years ago
QA Contact: gurganbl → libical
Component: libical → Internal Components
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base
You need to log in before you can comment on or make changes to this bug.