This is a project I created many years ago, and haven't touched in about 13 to 16 years. It's mainly here for posterity, but if you still find it useful (and if it still works) then by all means feel free to make use of it. Any references to "6 times 9" are because that is the retired website where I was previously hosting things like this.
Galsing (short for 'Gallery Single') is a PHP script for creating single page photo archives (where 'single page' means that the script is a single file, not that all the photos are shown together on one page).
It was created for an old website that was a gallery of photos of our cat at the time, Tigger (1997-2008). It was originally based on "Gehazi", a similar script created by Tim Packer and Thomas Thurman. Gehazi didn't support multiple pages; pages had to be done manually using distinct files. As my Tigger photos were rapidly increasing in number, I decided to create a Gehazi that would automatically condense a long list of photos into multiple pages. I called it "Galsing".
Initially, as with its predecessor, it used local files - with a separate file for the thumbnail - and presented them as a gallery. Eventually the number of photos I wanted to display became annoying to maintain, so I rewrote it from scratch to use Flickr's API; this was also useful as the previous code was getting quite bloated from layers and layers of added features. The rewrite was a good opportunity to tidy it up. This was, unsurprisingly, the point it was renamed "Galsing Flickr".
Currently I have no live websites using Galsing to use as a demonstration. The Photography section here employs a similar principle, however it doesn't use Galsing and was written from scratch as I didn't need anything as elaborate as this script since I just wanted links to the albums on Flickr, rather than a means of displaying the photos on richardwinskill.uk.
Before using Galsing Flickr you will need to apply for an API Key (an API Key is what will allow the script to communicate with Flickr).
Why do I need my own?
It's damage control. If someone really hammers the Flickr servers then the API Key they're using will be blocked. If everyone else is using this Key too, then they'll all be blocked as well. I doubled checked this with Flickr, and they came back with:
You'll definitely want your users to use their own API Key. If not, and the application is widely used, there is a good chance it will end up being disabled once the Key limits are hit. There are a couple of applications that have gone through this in the past.
Flickr Support, 2008, by email
To be honest, I don't know if you do, or really ever did; I'm just going by what Flickr's customer support told me 15 years ago. Regardless, the downloadable file doesn't have one because of what they said, so either you need one because of the explnation above, or because there isn't an API key in the file and there needs to be...
How do I get one?
You can apply for an API Key by filling out Flickr's "Apply for your API Key" form.
Most of the form should be pretty straightforward. For "About the application", something along the lines of "I want to use Galsing Flickr from http://richardwinskill.uk/code/galsing.php on my website, and I have to apply for my own Key" should be fine.
Once you have the Key, you need to copy it to the
$apikey=''; line near the top of galsingflickr.php (e.g.
Since the processing of the photos is the same in each case, the 'engine' is a single file that's referenced by each page that needs it. The referencing page is also where the options are set.
Once galsingflickr.php is uploaded to your server, implementing it should be as simple as adding the following (adjusted as appropriate) to each page that requires a gallery:
"Young Tigger" => "1337764",
"Tigger" => "1317783",
"Tigger Lite" => "72157594238328599",
To download the Galsing Flickr script just right-click and choose "Save As" (or the equivalent for your device/web browser).
To download the Galsing Flickr CSS just right-click and choose "Save As" (or the equivalent for your device/web browser).