Summary | Add a message to let users know to select a calendar |
Queue | Kronolith |
Queue Version | 2.0.5 |
Type | Bug |
State | Not A Bug |
Priority | 2. Medium |
Owners | |
Requester | luke (at) 3degreemedia (dot) com |
Created | 12/07/2005 (7161 days ago) |
Due | |
Updated | 12/07/2005 (7161 days ago) |
Assigned | 12/07/2005 (7161 days ago) |
Resolved | 12/07/2005 (7161 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
have checked there first. In my version (Horde - 3.0.7; Kronolith -
2.0.5), the code dosen't look like it picks a default if none are
selected, but I'm not familiar enought with your code base to know for
sure. I guess it's a moot point if the CVS version does it correctly.
I have done some more testing, and found out that it does in fact have
the default calendar selected on the user's first login. I think what
I did was to go to the drop down menu to select a calendar not
realizing that it would actually unselect it if it was already
selected. I then tried to enter events and couldn't figure out why I
couldn't see them. Using a drop down menu as a toggle is confusing
and probably a bad idea. Maybe a list of check boxes under the
calender display would be better? Or has this all been fixed already?
Anyway, I guess the reason it dosen't work for me is because I just
didn't know how to use it ;)
Thanks
State ⇒ Feedback
every page view) to add the user's personal calendar if no calendars
are enabled. See line 129 of base.php (for HEAD, anyway). So why
doesn't that work for you?
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Add a message to let users know to select a calendar
Queue ⇒ Kronolith
results in adding an event, but still having an apearantly blank
calendar. Instead of displaying a blank calendar, it would be nice to
let people know that they need to select a calendar to display. It
may sound trivial, but I'm a pretty smart guy and I spent a couple of
days trying to figure out what was wrong. There have even been bug
reports because of it (bug# 1508 for e.g.) Nag has the same issue.