SAK Selector link
-
@Whoey said:
The current version (which we inherited from the sakselector creator) is a CGI script which pulls data from a CSV file. I have an XLS version of the CSV for updates, as it's a massive PITA to go back and forth due to the amount of data. We had hoped to rebuild it in PHP with a MYSQL database and some further sort of easier to update interface, but alas there's always 50 other things that need taking care of first. Updates would be great, the data in the file is pretty extensive with 120 options per SAK model with approximately 310 models included, with obviously some gaps in the data, and it's far out of date (it was never updated by us since we inherited it).If you have some corrections/additions etc let me know and I'll make an effort to integrate them.
If you're happy to send the files over I'll see if I can produce updated versions. Or maybe provide a subset to show what is needed? Alternatively, I can try and describe the changes in a way that you can apply.
Any reason the data files can't be on the Wiki so that everyone can at least propose changes, and some be given permission to edit? Then copy / paste to selector app?
Would it benefit from putting the data into an Excel structure where VLOOKUP() and the like can be used to create a consistent data set, then a bit of VBA to squirt out refreshed CSV files to move to the web server?
EDIT - Thinks / lightbulb: Which is pretty much what I have for the SAK Wiki tables we've been refining, so maybe it's just another output from that... But we ought to have a shared database which can be maintained by multiple folk.
-
Some things are in motion, lets see how this goes, we may actually update the entire thing to be easier to edit/add new items.
So rather than get ahead of ourselves we'll see if this works out, then get into updating the data.
-
Whatever happend to updating the SAK selector? It's broken now, it doesn't display anything. There's no submit button visible, and no knives are ever displayed.
Charles.
-
It does work on the computer I'm working at. Configuration: Macos El Capitan, using Chrome.
And this is the link http://www.swissarmyknights.com/sak-selectorTried emptying the cache/cookies, if you're on a computer?
-
OK, latest SW, that is:
- MacBook, macOS 11.2.3 (20D91) Big Sur,
- Chrome Version 89.0.4389.128 (Official Build) (x86_64) (or any other browser)
- cache cleared, etc... the iframe doesn't load:
https://www.swissarmyknights.com/sak-selector

Same on Win10 64-bit...
It's the page not us... -
Remove the www. then it works: https://swissarmyknights.com/sak-selector
Or this, open the .cgi directly: https://swissarmyknights.com/cgi-bin/sak_selector.cgi -
@Reinier said:
Remove the www. then it works: https://swissarmyknights.com/sak-selector
Or this, open the .cgi directly: https://swissarmyknights.com/cgi-bin/sak_selector.cgiThanks! Has anyone contacted them regarding this bug?
-
@tritrek said:
Thanks! Has anyone contacted them regarding this bug?I know I haven't. But Whoey may read this thread.
Technically it's not a bug, it's just a security feature in all modern browsers, but it is something that should be fixed server-side. My suggestion: force all traffic to the non-www URL. In that case, including the SAK Selector page in an iframe like it is now should work and it's also better from a SEO point of view. Because currently all content on swissarmyknights.com is available on at least 2 different URLs.
Alternatively the iframe source could just be the relative URL /cgi-bin/sak_selector.cgi (so, no protocol, no domain name). That should work as well.
-
@Reinier said:
I know I haven't. But Whoey may read this thread.Technically it's not a bug, it's just a security feature in all modern browsers, but it is something that should be fixed server-side. My suggestion: force all traffic to the non-www URL. In that case, including the SAK Selector page in an iframe like it is now should work and it's also better from a SEO point of view. Because currently all content on swissarmyknights.com is available on at least 2 different URLs.
Alternatively the iframe source could just be the relative URL /cgi-bin/sak_selector.cgi (so, no protocol, no domain name). That should work as well.
Right... and that's a coding bug :) Loose coding... nothing lethal just causing headaches to us and basically crippling their own page...
-
I posted a link for Whoey, hopefully it will be fixed soon
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login