Closed fraz3alpha closed 1 year ago
We had two emails from users this morning who were unable to save their home parkrun on the options page because it couldn't fetch the data - I think it was likely the technical event information that was the problem, as I saw that error on my own page, but it could have been the geo data too.
I've also seen a couple of failures today - failing to load the technical event info page seemed to be the source of the problem.
I'm going to close this, and keep it simple with how it is now. It'll sometimes fail I guess, but it's a lot of overhead maintaining something else
As it stands the extension loads two static files from the parkrun website - the geo.xml file (containing the 5k parkrun locations and country/region information), and the event technical information wiki page which tells us whether an event has started yet. If we want to add in the junior parkrun events, this is another page, and it is already getting a bit busy here. In order to load things more reliably, and to not put extra strain on the parkrun website, we can proxy these files on our static site, and do the relevant parsing in advance.
For example:
We have had a few bugs reported when the wiki isn't working well (presumably during busy times), and it stops people getting going with the extension - therefore it would be useful to take any extra load off it. It also means if the data moves, we can update our code centrally without every user having to update their extension.