0.0 m surveyed this year.
Table of all trips and surveys aligned by date
|July 25, 1983||travel - The journeys out.||travel|
|Aug. 1, 1983|| Phil's 29th birthday trip down
|| Phil's 29th birthday trip down
|Aug. 4, 1983|| 132 or
|| 132 or
|Aug. 5, 1983||Salzburg - Friday 5th Mass Jacking Day||Salzburg|
|Aug. 6, 1983||142 - connection 142/41||142|
|Aug. 7, 1983||look for resurgences||look for resurgences|
|Aug. 8, 1983||WOLFHÖHLE 145||WOLFHÖHLE 145|
|Aug. 9, 1983||142 - 41 CONNECTION SURVEYING AND DERIGGING||142|
Horrible bug here but only when there is more than one survex block per day, e.g. see Wookey 1999 where there are 3 eiscream survex blocks on 5th August. it duplicates the entry but gets it wrong. The length from the first block is displayed twice but there should be 3 rows: eiscream, eiscream2, eiscream3.
Fortunately it is just this display on this page which is wrong: no bad calculations get into the database.
The interaction of django database query idioms with django HTML templating language is a bit impenetrable here.
I blame Aaron Curtis who was too fond of being clever with the Django templating system
instead or writing it in python anyone could understand.
- The template is in troggle/templates/personexpedition.html
- The code is in function personexpedition() which calls get_person_chronology() in troggle/core/views/logbooks.py
- the connection between the two is made in the URL resolver in troggle/urls.py
To be fixed!