nerdland

Thanks, though. If I do have to go with that solution, I’ll at least feel a little better about it. Haha.

Yeah, I do know that’s an option. It just seems like it isn’t quite the right way to do it. But maybe it is, and I’m just thinking about it in a weird way. I’m trying to understand the loop a little better and figure out why, exactly, it behaves that way.

It doesn’t seem logical, in my mind, that a function asking if a page has a post thumbnail should return true on an archive page, when the archive page itself obviously doesn’t.

It occurred to me that this might be causing something, too. Not sure, but I’m trying to be as thorough as possible.

I’m on MediaTemple’s GridService hosting, which, for some reasons I don’t totally understand, gets along weirdly with SSL in WordPress by default. Basically, by default, accessing the site through SSL will cause an endless redirect loop.

They have documentation on how to make it work, which I’ve followed. The article provides 2 methods to fix this, but I’ve tried both on separate installations and the behavior is the same.

This is pretty much Greek to me, but from what I can gather, they’re rewriting HTTP_HOST to SERVER_NAME. Would that cause anything like this?

https://wiki.mediatemple.net/w/(gs):WordPress_SSL_Redirect_Loop

Not sure if any of this helps, but I enabled Debug Mode and I get this stuff up top:

SSL: Yes
Diff Host: No
Subdomain: No
Proxy: No
Secure External URLs: [ ]
Unsecure External URLs: [ ]

I’m not sure what all of that is supposed to be saying, but I AM on a subdomain. Is that causing weirdness?

I’m having a problem like this, too. Should this be working at this point?

I’m trying to redirect from https://foo1.example.com/bar1 to https://foo2.example.com/bar2. They’re both on the same SSL certificate, if that makes a difference, and the certificate is for *.example.com.

It’s doing some weird things, though. When I use HTTP, it works like I would expect it to. Even when it’s from HTTP to HTTPS. As long as I start with HTTP, I get to my end URL, no problem.

When I use HTTPS, it takes me to https://foo1.example.com/bar2. It takes the directory from the target URL and tries to open it on the domain from the original.

I’m currently using the Redirection plugin to do this, (https://www.ads-software.com/extend/plugins/redirection/) but the same behavior happens when I hard-code the redirect into my functions file, so I’m pretty sure it isn’t an issue with that plugin.

Any ideas?

iPhones can not upload from the web.

Yeah, it obviously adds an error class or something, so I could just hide it with CSS. Thanks for the suggestion. I’m gonna poke around some SimplePie-related forums to see if anyone has a good solution.

It’s weird because both kelapo.com and coconutoilcooking.com (The blog it’s pulling the feed from) are hosted on a mediatemple (gs) account. ah well.

Seems like I get this error or a similar one pretty often. I’ve been building this site, and it seems like it’ll pop up at least once a day. When it does, it goes away as soon as I reload, but it’s still super annoying and rather unsightly when it rears its head.

Here’s the website:
https://www.kelapo.com

And here’s a screenshot:
https://gyazo.com/754ff7f751f33970a467935e85770b48.png

I’m using it for the YouTube feed on the left of that, too, but that one doesn’t seem to break as often. I’ve only noticed it once.

I know this doesn’t directly have anything to do with HungryFeed, but do you have ANY suggestions on how I might remedy this? Is there a way I can tell SimplePie to just fallback on the most recent cached version rather than display the error? If it were a serious enough error, I’d notice after it didn’t update for a few days. (Not just the occasional timeout, which I’d honestly rather not know about)

Yeah, I know what you’re saying, although I guess I feel like if a serious error were occurring, I’d probably notice it on my own if the feed didn’t update itself within a reasonable amount of time.

When I got that error, it actually updated properly as soon as I reloaded it, so I don’t know what happened that one odd time — it probably just couldn’t connect to the server. But in those cases, it would be really nice if it would just fall back on the cached version. Then no one needs to know that an error even happened.

Obviously, you’d want to see what errors are happening if they’re preventing the feed from updating at all, but maybe that could be an optional debugging parameter built into the shortcode, so that you could just toggle it when you need it.

Anyway, sounds like you have very little control over it anyway. It was mostly wishful thinking. Overall, though, thanks for building a great plugin!

Thanks so much! That worked, but I don’t totally understand what the “https://search.yahoo.com/mrss/” is all about, or where that’s coming from. What IS that all about?

Hey there. Excited about the possibilities of HungryFeed. I was trying this out, though, and kinda ran into a brick wall. I tried it out with the Apple RSS feed, just to try to get a grasp on how it works, and wasn’t having any luck. I don’t know if Apple has changed their fields in the 2 weeks since this was posted, but the field I found in the RSS feeds was albumPrice, not 'price'. I tried replacing that, but it still didn’t display anything.

The feed I actually need to use is YouTube’s, but I was hoping I could figure it out if I could figure out the iTunes example. I know I can dig down with CSS with your tutorial, but this seems like it would be simpler if I could get it to work with the provided fields.

An example feed URL is:
https://gdata.youtube.com/feeds/api/users/youtube/uploads

As you can see, they provide a ‘thumbnail’ field. It’s used multiple times for different thumbnail sizes, but when I add show_data="1", I can see they’re given numbers. (0, 1, 2, 3)

I’m just not sure how to target that. Since I couldn’t even get the example working, I don’t really know how to hack it.