271305 - publishing event deletes calendar

Status: RESOLVED DUPLICATE of bug 218983

(Calendar :: General, defect)

Description

[Mike]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.10.1 StumbleUpon/1.998
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041112 Mozilla Sunbird/0.2b

when publishing a single event to a file for a calendar, all other events are
deleted.

Reproducible: Always
Steps to Reproduce:
1. publish calendar
2. publish single event to same URL

Actual Results:  
the other events were deleted

Expected Results:  
the event should be added to the existing calendar file, not replace it

Comment 1

[Richard Greenwood]

When using the Tools->Publish Selected Events option, the file entered is
overwritten if it exists with no warning or choice.
 - This makes sense if you want to publish a subset of your calendar to be
viewed by others.
 - It doesn't make sense if you add a new event to your calendar and want to add
it to that published calendar.  You must find all the original events, including
the new one, and publish again.

This feature would be much more useful if it discovered the existence of the
file and prompted for overwrite/append/cancel.

Comment 2

[Yann Coupin]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20050203 Mozilla
Sunbird/0.2

I'm not sure I should open a new bug for this, but here's my problem, I wan't to
have a calendar shared. I first have to create it locally, create an event,
publish it, delete that calendar and finally suscribe to it remotly. If I don't
delete the calendar and suscribe to it, every time I publish my calendar, it
overwrites anything published from another computer. So either, there should be
an option when subscribing to create the calendar if it doesn't exists, or the
publishing procedure shouldn't overwrite anything created from outside the local
calendar. I even think the best solution would be to be able to change the
status from a calendar with 3 different status : "local", "publish to remote"
and "synchronize with remote". When a calendar is local, you can't publish or
update, neither input a URL, when it's "publish to remote", every modification
triggers an upload which erases anything present on the remote site, a URL is
mandatory. When "synchronize" is choosen, every modification is published
without erasing the remote modification (which get's added locally, if missing).

Comment 3

[Joey Minta]

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

Comment 4

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!