expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 00:42:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix capitalisation of slugs

Browse Source
This commit is contained in:
Philip Sargent 2023-09-26 18:53:09 +03:00
parent 6c6b3f8ab1
commit f2ded31332
5 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cave_data/1623-JUTTAHOEHLE.html → cave_data/1623-Juttahoehle.html
View File

@ -17,7 +17,7 @@ the form documented at
<cave>
<non_public>False</non_public><!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
<caveslug>1623-JUTTAHOEHLE</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<caveslug>1623-Juttahoehle</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<official_name></official_name><!-- Name of the cave (normally in German) Use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<area>1623</area><!-- the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
@ -39,7 +39,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>Juttahoehle</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
<entrance>
<entranceslug>1623-JUTTAHOEHLE</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<entranceslug>1623-Juttahoehle</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
</entrance>

4
cave_data/1626-LOUTOTIHOEHLE.html → cave_data/1626-Loutotihoehle.html
View File

@ -17,7 +17,7 @@ the form documented at
<cave>
<non_public>False</non_public><!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
<caveslug>1626-LOUTOTIHOEHLE</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<caveslug>1626-Loutotihoehle</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<official_name></official_name><!-- Name of the cave (normally in German) Use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<area>1626</area><!-- the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
@ -39,7 +39,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>Loutotihoehle</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
<entrance>
<entranceslug>1626-LOUTOTIHOEHLE</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<entranceslug>1626-Loutotihoehle</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
</entrance>

2
entrance_data/1623-JUTTAHOEHLE.html → entrance_data/1623-Juttahoehle.html
View File

@ -19,7 +19,7 @@ though, you do not need to do a data import as it happens automatically -->
<br>
<entrance>
<non_public>False</non_public>
<slug>1623-JUTTAHOEHLE</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1623-Juttahoehle</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>

2
entrance_data/1626-LOUTOTIHOEHLE.html → entrance_data/1626-Loutotihoehle.html
View File

@ -19,7 +19,7 @@ though, you do not need to do a data import as it happens automatically -->
<br>
<entrance>
<non_public>False</non_public>
<slug>1626-LOUTOTIHOEHLE</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1626-Loutotihoehle</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>

8
years/2023/logbook.html
View File

@ -113,11 +113,13 @@ RRPC/DUSA/CUCC/FCCC</div>
<hr />
<div class="tripdate" id="2023-06-25a">2023-06-25</div>
<div class="trippeople"></div>
<div class="trippeople"><u>Adam B</u></div>
<div class="triptitle">Expo - UK Caving Blog post: my first expedition</div>
<!-- Content parsed from UK Caving Blog -->
Blog Author: Adam 63<div class="bbWrapper">A little something on preparing for my first expedition,<br>
<br>
[Author has to be an on-expedition member, and we don't know which of the two adams this is who are new this year, so guessed.]
<br>
CUCC Austrian Expo 2023 will be my first expedition I’ve written this short piece sums up my preparation. Getting ready for my first expedition is an exciting but also quite daunting task. With the amount of new gear needed and the dangers and of the expedition itself it has proven a somewhat intimidating experience, however slowly I’m getting my shit together. A big help has been meeting with the other first time Expo cavers in Leeds, starting a group chat and meeting up to group order and discuss gear and insurance and generally about the expedition.<br>
<br>
To be honest the biggest task has been just buying all the gear. One of the great parts of Expo is its affordability in terms of accommodation with travelling out making up most of the cost. Although for the first time going with not owning much gear for UK sport trips let alone the extra gear for alpine expeditions, getting the extra gear has somewhat affected my bank balance. However, aside from a few expensive items (a harness and over suit) there is plenty of general gear such as layers and dry bags that scrounging deals and charity shops, borrowing and gear exchange hasn’t been too hard to source.<br>
@ -1374,9 +1376,11 @@ entrance. Good opportunity for Tom to have more practice on book (paperless).
<hr />
<div class="tripdate" id="2023-07-20c">2023-07-20</div>
<div class="trippeople"></div>
<div class="trippeople"><u>Bier Tent</u></div>
<div class="triptitle">I’m very happy that Homecoming is being revisited</div>
<!-- Content parsed from UK Caving Blog -->
[Author has to be an on-expo member, but "Samouse1" (whoever that is) is not on expo this year. So the author is given as the Bier Tent to prevent annoying reminder messages.]
<br />
Blog Author: Samouse1<div class="bbWrapper">I’m very happy that Homecoming is being revisited, I pushed that back in 2018 when it was discovered, and named a lot of the bits you can read about above.<br />
<br />
One thing to note is that in German it’s Heimkommen, not Heimkehr! The second was found to be a propaganda film related to a certain political party in the 30s and 40s. The original exploration logs from 2018 have it as Heimkommen. <br />