SmugMug – download full-sized images

Did they ask you to provide them with the album information etc.? It is fairly easy to verify from there that the ArchivedURI is blank.

If you go to the actual album on SmugMug, the download link is there and it does work successfully.

If you go to the actual album on SmugMug, the download link is there and it does work successfully.

True, but SmugMug’s front-end is not the same as its API.

Sorry. I misunderstood your question. They did not ask me to provide any information. They seemed more interested in putting blame elsewhere than problem solving.

No worries.

Let me provide you with an example.

1. Access my album list via the SmugMug API: https://api.smugmug.com/api/v2/user/sayontan!albums. You can replace my name sayontan with your login name
2. Now open an album from my list of albums, say “Sydney” (https://api.smugmug.com/api/v2/album/gPxCw4)
3. Go to the link that says “AlbumImages” (https://api.smugmug.com/api/v2/album/gPxCw4!images)
4. Pick an image, say the one that says “Captain James Cook @ Hyde Park” (https://api.smugmug.com/api/v2/album/gPxCw4/image/g9LSpwR-0). You can see the ArchivedUri over there (the 6th field). There is also an additional link that says “ImageDownload”, which yields the same link

You can try repeating these steps for one of your photos – this information doesn’t show up. Try providing this information to them.

I did try a workaround in your case, by basically going directly to the ImageDownload link for one of your photos (essentially by swapping out my image id with yours in my ImageDownload link). Surprisingly enough, it shows the download URL (not the original image) – something that I can use to link to the download button. However, the challenge is that SmugMug is not providing me with the ImageDownload link in the output for your album. The absence of this link means that I have to go through each returned image and fetch the download URL individually – this incurs a cost of one API call per image, and for a typical album of yours you are looking at a few hundred extra API calls easily. That will degrade performance to a point of unusability.

If, however, you are able to see the ImageDownload link, or the ArchivedUri, something else might be at play, primarily authentication. In such a case I would suggest getting an API key and enabling back-end authentication.

Thank you very much for this info. This is a big help. I didn’t realize that I could access images this way. I will see what I can find out.

Brilliant!

Okay. So this probably isn’t what you are expecting but when I chose an image via the API, the ArchiveUri was not blank. I checked multiple images and indeed, they all had ArchiveUri values. And when I clicked on the link for the ArchiveUri, it did indeed start the download process. So it does appear that things are okay at SmugMugs end of things.

Could the problem be with the lightbox I’ve chosen?

For your reference: https://api.smugmug.com/api/v2/album/mpczWd/image/XKwTXS2-0

Please refer to the last bit in my previous post about authentication.

Basically when I view the links in your album, I don’t see the URLs. As you can see here, there is no ArchivedUri:

Similarly, there is no “ImageDownload” link:

This leads me to think that there is some SmugMug setting at your end that is preventing links from showing up to unauthenticated users. I don’t have explicit authorization to view your albums, and though you recently removed password protection, probably your photos were individually protected when you loaded them up and that protection is overriding the removal of the password-protection.

So, it is likely that if you perform the authentication in Photonic things will start working.

Okay. That is making sense. Because I’m logged into the SmugMug account all that info is there. From what I can see. I do have authentication set up in Phototonic. I have values in place for:
SmugMug API key
SmugMug API Secret
Access Token
Access Token Secret

Am I missing something else?

At this point I am almost out of ideas. The only thing I can think of is that somehow the authentication is not working, but that is a tall ask to troubleshoot even in a full-fledged development environment, let alone a restricted client-facing environment.

You can try redoing the authentication, but if that doesn’t work, I am afraid this will remain unresolved.

Okay. Will try redoing the authentication