adam pw smith
04-27-2006, 09:23 PM
Perhaps if this problem* gets reported as a bug over and over again it should be considered a design flaw.
With all due respect, I don't think anyone could be accused of mental laziness for loading their home page and thinking it's the wrong picture when they see a future photo and the current date displayed in the calendar.
May I suggest that either you default to the current photo and offer those who are logged in the chance to click on future dates on the calendar, or show the date of the displayed photo correctly in the calendar.
I love my photoblog and I am extremely appreciative of the effort put into the project, but while this may be correct behaviour programmatically, it's obviously causes more than a few people to be confused.
adam
[* if you're logged and you load the home page using just the base URL you see the most recently dated photo, but the calendar shows today's date. To actually see today's photo you need to back up a day and then go forward so that the URL points explicitly to today's date.]
With all due respect, I don't think anyone could be accused of mental laziness for loading their home page and thinking it's the wrong picture when they see a future photo and the current date displayed in the calendar.
May I suggest that either you default to the current photo and offer those who are logged in the chance to click on future dates on the calendar, or show the date of the displayed photo correctly in the calendar.
I love my photoblog and I am extremely appreciative of the effort put into the project, but while this may be correct behaviour programmatically, it's obviously causes more than a few people to be confused.
adam
[* if you're logged and you load the home page using just the base URL you see the most recently dated photo, but the calendar shows today's date. To actually see today's photo you need to back up a day and then go forward so that the URL points explicitly to today's date.]