Definitely had me wishing for a two-booted non-lubricated mustelid situation instead.
I realised I could prevent this without needing to impact wildcard spotting, so this is now also fixed on SW3
Thank you Andrew!
(BTW: when I corrected one misspelling I saw that I was awarded a “St Patricks something” - for whatever reason. But I do not see it in the DB.)
Hello, I’ve been trying to upload my log for activation of W4V/GC-005 from this past Saturday 22 March but unable to do so. When I click the Verify Log button, it displays this error message “Http failure response for https://api-db2.sota.org.uk/uploads/verify: 403 OK”. Can you please take a look at this? Thank you, Bob W4BTH
Are you logged in? Try logging out and back in again. I’ve noticed that sometimes it looks like you are logged in but another part of the system thinks you aren’t.
Turn off Brave Shields.
St. Patricks Day, March 17th, a celebration of St. Patrick who brought Christianity to Ireland. It’s celebrated in countries with a large Irish diaspora and is allegedly celebrated in more countries than any other national festival. Surely you have heard of it?
Here are you badges from your DB overview page, your St. Patrick’s day badge is there.
Thanks, yes I was logged in, but logged out & back in & also dropped my shields and was able to submit it with no problems. Thank you for quick response & your help
Many Thanks, Bob
Thanks, that worked. I’ve had those shields up in past with no problems, but will remember to turn them off for my next activation. Thanks very much for the quick response
I greatly appreciate your help! Many Thanks, Bob
The shields option is per website so you can leave them down for all SOTA sites and set them however you want for other sites. You don’t need to flip them on and off all the time.
Got it & will do. Thank you!!
Did someone accidentally activate a retired summit without realising it was invalid? (Maybe one that was retired in a recent update?)
Chasers still logged their chases not realising it was an invalid summit.
The answers to your questions are:
Maybe.
One was retired 15.5 years back
Yes.
People make mistakes, so it just needs things like this to ensure we get edge conditions handled in the software.
Thanks Andy, you are totally right.
Since this badge had popped up during the most recent DB save process, I expected it to be one of the latest badges.
And of course: The St. Patricks Day was celebrated even here in Funchal.
It can be confusing because new badges (St. Patrick’s Day is a newly released badge) will appear at differing places in peoples roll of badges as badges are displayed by the order you earned them. So my St. Patrick’s Day badge was for Mar 17th 2007 and appears early on in my badges.
There were three different activations within the past week or so. And indeed possibly more but I haven’t gone that far back in the logs.
I don’t know why that might be the case but I would expect chasers just log what they hear. And when it doesn’t work, they try again ![]()
So a simple typo in the reference would have (or actually has) caused this issue?
That sounds like a very obvious thing to happen.
Especially with the statement: ‘You log what you hear’
Yeah, but it would clear quickly before we noticed. What’s unique here is the three in a week which meant there was no opportunity to clear during the EU or NA days (it would clear during APAC hours)
There are rumours that some people use old paper printouts that the carry along on hikes to get reference. So I am not surprised that inactive summits get activate.
And there are apps like “Sota Finder” that are not automatically updating and have a 4 year old summit info. So many options for people to make mistakes.
I don’t think it happens all that often - people will call out wrong summits pretty quickly if they see it. It’s perhaps more likely in Europe because of the large updates to early Associations like DM, DL, I and the EAs. It’s just unusual to get one in EA, one in DM and one in DL in the space of 7 days.
