180970 - No visible results (success or failure) are returned when publishing an event or calendar

Status: NEW

(Calendar :: Import and Export, defect)

Description

[Fred]

User-Agent:       Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2b) Gecko/20021016

As I was experimenting with publishing set of events, NO indication of results
was given when the action completed. I was trying to set up DAV on my web server
and I was forced to check the web server logs to determine if it worked or not.
Some sort of indication of success AND failure (along with some diagnostics)
would be useful.

Reproducible: Always

Steps to Reproduce:
1. Publish an event (say to http:// kuipers.dhs.org :1333/webdav/ -- remove
spaces  to make it work :-) and it will fail because you need to have a password
to do so.
2. Notice Calendar gives NO indication of the error

Actual Results:  
Nothing... :-(

Expected Results:  
I should have been presented an alert box (or something) indicating success OR
failure.


Using the calendar.xpi build as of Nov. 19, 2002...

Comment 1

[Mike Potter]

I've added in a progress meter that should show you that its doing something. 
Still not completely done, but its better than it was.

Comment 2

[Mike Potter]

New contact from [e-mail] to [e-mail]
Filter on string OttawaMBA to get rid of these messages. 
Sorry for the spam.

Comment 3

[daneel]

Is this publishing thing supposed to work with FTP? Because I enter an FTP url
(ftp://mysite.tld/somedirectory/text/test.xsi), hit Publish, and it just sits
there doing nothing. It doesn't ask for username, password, or anything :(. Btw,
I have Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040809
Mozilla Sunbird/0.2a. I also tried the Firefox and Thunderbird Extensions. Same
thing.

Comment 4

[Matthew (lilmatt) Willis]

Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove

Comment 5

[Olexi Pasyuk]

I confirm the same behavior for Lightning. It is the same for all types of publish destination.