Closed (fixed)
Project:
Archive
Version:
5.x-1.7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Nov 2007 at 13:57 UTC
Updated:
12 Jan 2008 at 17:21 UTC
Jump to comment: Most recent file
Hi
been having a spot of trouble with archive - see mine here: http://commercial-archive.com/archive
In the old version I changed the number of past years displayed from 3 to 37 but it didn't work as planned. Upgraded to 5.x-1.7 now. Did not touch the code. Still have bizarrley formatted years prior to 1991. Can get http://commercial-archive.com/archive/all/1991 just fine but not a proper page on 1990 or 1987 or whatever. Monthly archive shows that I do indeed have stuff in the earlier years see: http://commercial-archive.com/monthlyarchive
Possibly related? http://drupal.org/node/161278
I have ads from 1958 and 1969 but that is thanks to the Unix timestamp a whole'nother can or worms.
Comments
Comment #1
Susurrus commentedSee #197492: "All" link browses back to all types even when browsing by type as I think that's your problem right there. If that works for you, then we're gtg.
Comment #2
Dabitch commentedI applied that patch, and I see no change. Cleared cache and waited fifteen minutes even. No change. Bummer.
Comment #3
Susurrus commentedIt was a problem with my code and having some arbitrary hard-coded dates. Try this patch, should fix it.
Comment #4
Susurrus commentedI also encourage you to check out the development snapshot for the 5.x branch. It should be stable and includes changes that would benefit your site, since you have posts ranging over a wide range of years.
Comment #5
Dabitch commentedThat patch worked like a charm*! Thanks so much! Happy new years!
* well except on 1970, but this has more to do with the unix timestamp and mysql combo than anything else, as we don't have ads from 1970 but do have ads from 1969: http://commercial-archive.com/monthlyarchive/197001
Comment #6
Susurrus commentedThen this's closed. Using timestamps is causing the 1970 issue, but there's nothing I can do about that. Hopefully Drupal will switch to a little better date/time storage system soon...
Comment #7
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.