Closed Bug 168557 Opened 22 years ago Closed 22 years ago

Event placed only in default calendar

Categories

(Calendar :: Sunbird Only, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: charles.s.libby, Assigned: mikeypotter)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Even with the default clendar un checked, I add a new event to the calendar.  If
I make the event greater than the default length, it does not appear in the
checked calendar.  I check the default calendar and it is there.  If I edit the
event, and try to select something other than the default the event is never
placed in the calendar.

I am using Windows 2000 Service Pack 3.  I just upgraded to Mozilla 1.1 and
installed the calendar addin.  Today September 13, 2002.

This really may be two bugs

Reproducible: Always

Steps to Reproduce:
1.Start with only the default calendar (I just installed the program)
2.Add a new calendar by right clicking in the calendars box
3.Give it a name
4.Right click on hour where you want the event to appear and select add event
5.Give it a name
6.Change the calendar file to the name of the other calendar you just created
7.Click OK
8.Deselect the Default menu to see only the second calendar
9.Even right clicking on the time where the event should be does not give you
the event.

Actual Results:  
No Event appeared in any calendar.

Expected Results:  
There should have been and event there.

Windows 2000 Service Pack 3 and all current patches as of 9/6/02
The filing events part duplicates bug 168339.

What file should new events start in?
* The 'default' file?
* The selected file (black background)?

Adding may be mysterious if the added file's checkbox is not checked --- the
event would be added but not appear, so it may appear mysteriously lost,
particularly when selecting a file toggles off its checkbox.  If the event were
to start in the selected file, then selecting a file should not toggle its checkbox.
When adding events, even with the Default deselected (un checked) and the other
calendar selected, the event does not appear.  I took this to a different
computer same OS, and it did exactly the same thing.  This is a brand new
install as well.
Try this in the XPI available now. It should be working fine, it works fine for me.
There should be a bug filed for the selected server not being the one that is
highlighted.
I do not confirm. Steps to reproduce do work just fine for me and the new event
is where it should be. Try to check with new build.
Build 2002091215 on WinME
I believe I have found the problem.
When adding a new calendar I right clicked in the calendar section of the
screen.  I then selected the new option.  The dialog box which appeared asked
for a calendar name which I provided "test" I did not specify any file location.
 I expected the file to be created for me in some default location.  I clicked
OK.  The Entry went into the Calendar entry, but when I went to edit the
calendar, the file location was greyed out.  When I went to browse for the file,
it showed the file name as "MozillaCalendartest.ics" This file is not existant
on my machine.  I tried to add a calendar again but this time I put a file path
in the location spot and I can add and delete events to that calendar.  It did
bring up a new bug.  When I delete a calendar and add a new calendar, the old
calendar place is still there and does not go away until I close and re-open the
calendar program.

As to this bug, it seems the "add a new calendar" should create a calendar file
in some default location.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is now fixed in CVS and in builds available now.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
VERIFIED FIXED
Status: RESOLVED → VERIFIED
The bugspam monkeys have been set free and are feeding on Calendar :: Sunbird Only. Be afraid for your sanity!
QA Contact: colint → sunbird
You need to log in before you can comment on or make changes to this bug.