next month button remains disabled
goodsanket - September 21, 2009 - 11:11
| Project: | Event |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | goodsanket |
| Status: | active |
Jump to:
Description
Issue on Block:
1st I dint add any event, Next month button was disabled. I used prev month button to go back, still it was disabled.
Then I added event in previous month, again next month was showing disabled only. Only when I added a event in next month both were enabled. Is this how it is purposely kept?
#1
I have this problem too. And not only in block.
http://img16.imageshack.us/img16/769/image41031835.png
http://img16.imageshack.us/img16/3272/image41041803.png
Please, help.
#2
I'm pretty sure it's done on purpose, guys.
It only enables it once an event ahead of that month is made. What reason would you need to go forward at that point, prior to any future event being created outside the current month?
#3
That would make sense if it didn't go backwards when there's no events in previous months. By default it's starting on the current date so if I go back I should at least be able to go forward to the current date. That's my opinion anyways.
#4
Same issue here and if I go back to previous months, I would at least like to go forward again to today.
#5
And what would this accomplish if that were the case? This is assuming there are no upcoming events, of course, since this is the only scenario it does not allow you to go forward.
What purpose would it serve? Peace of mind?
#6
I suppose users expect to be able to browse indefinitely into the future in thus module. Since it is possible where they come from: Google Calendar, Apple iCal, Microsoft Outlook, Novell GroupWise all let them browse their calendars that way.
I have a calendar set up for a local community where anyone can book a cabin and this behavior is a bit problematic for us when looking for prospective dates. The workaround I have done so we can browse future dates is to make dummy bookings that go far into the future.
I would like to start a discussion on the merits of this. Can we perhaps solve the "no more bookings ahead of this date" information in another way?