Interesting Problem With RSS Feeds, Custom Domains and IFTTT

chaselton

In order to update my tumblr log with photos, I use smugmug keyword feeds in combination with IFTTT. Basically, if I add the keyword "tumblr" to any of the photos in my gallery, my IFTTT recipe posts the photo to my tumblr log, using the size that I've specified in the feed. I use the api.smugmug.com feed format with RSS specified

This automated process stopped working completely when I configured a custom domain name for my account. It started partially working again when I replaced api.smugmug.com with my custom domain name; IFTTT would post the photo to my tumblr log, but it would ignore the size I specified and use the smallest. I confirmed that the custom domain caused the issue by removing it entirely...which fixed the problem.

I did set up the custom domain correctly the first time. I'd really like to go back to using it again, but I also need to be able to use IFTTT. Has anyone run into a similar issue with custom domains altering the behavior of feeds?

chaselton

Or, has anyone had problems with their feeds behaving oddly after switching to a custom domain?

SamirD

Interesting. You should be able to still access your feeds and images via the generic smugmug domain. If that fixes the problem, you may have found a bug.

chaselton

SamirD wrote: »

Interesting. You should be able to still access your feeds and images via the generic smugmug domain. If that fixes the problem, you may have found a bug.

Not sure if you understand...I can access my feeds, but the photo size I specify is not honored. Instead, the smallest photo is displayed.

Out of desperation, I navigated to the root of the feed url (http://api.smugmug.com) and saw this at the top of the page:
Confluence Enterprise Hosted service expired 15 February 2013. Service will be shut down on 18 March 2013. Migration options are detailed here.

I don't know anything about hosting for the smugmug API...if smugmug manages it or if it's per user/developer so I'm not sure if that message is important or not.

SamirD

chaselton wrote: »

Not sure if you understand...I can access my feeds, but the photo size I specify is not honored. Instead, the smallest photo is displayed.

Out of desperation, I navigated to the root of the feed url (http://api.smugmug.com) and saw this at the top of the page:
Confluence Enterprise Hosted service expired 15 February 2013. Service will be shut down on 18 March 2013. Migration options are detailed here.

I don't know anything about hosting for the smugmug API...if smugmug manages it or if it's per user/developer so I'm not sure if that message is important or not.

What I mean is don't use your custom domain, but smugmug.com instead and see what photo you get. If it's the right size, then it's a bug related to the custom domain. If it's still small, then it's something else.

I don't think the API message you see means much as the API seems to be working just fine.

chaselton

SamirD wrote: »

What I mean is don't use your custom domain, but smugmug.com instead and see what photo you get. If it's the right size, then it's a bug related to the custom domain. If it's still small, then it's something else.

I don't think the API message you see means much as the API seems to be working just fine.

I did this already. I get the incorrect photo size with the smugmug.com feed as well.

chaselton

Problem solved today.

The "size" parameter in the feed is case sensitive...it has to be "Size." Such a small thing with such a huge impact...

--sent from mobile

mbonocore

chaselton wrote: »

Problem solved today.

The "size" parameter in the feed is case sensitive...it has to be "Size." Such a small thing with such a huge impact...

--sent from mobile

Glad to hear!

Michael

SamirD

chaselton wrote: »

Problem solved today.

The "size" parameter in the feed is case sensitive...it has to be "Size." Such a small thing with such a huge impact...

--sent from mobile

Ahh, good to hear. Most stuff in the computer world is case-sensitive!

chaselton

SamirD wrote: »

Ahh, good to hear. Most stuff in the computer world is case-sensitive!

You'd be surprised at how much isn't...it's about a 50/50 split unless you're working with RHEL

--sent from mobile

SamirD

chaselton wrote: »

You'd be surprised at how much isn't...it's about a 50/50 split unless you're working with RHEL

--sent from mobile

Back in the DOS days, it definitely didn't matter. As soon as the world became UNIX oriented with the rise of TCP/IP and the Internet, all cases have broken loose.