Jason

the parameter you want to use is

feed_fields=""

(instead of feed_items). that should do it whether or not you are using a template.

One thing to check is that you have spaces before and after the equal sign:

filter_out = “smoking|lottery”

The commas are not necessary for parameters either, though I don’t think they hurt anything.

Lastly verify that you have version 1.4.5 of the plugin. I just did a test on your feed and there were no items with “smoking” in the feed but I did try filtering out other words and it seems to be ok.

No problem. On second thought there are some sites that return RSS from their API, for example YouTube does that.

It seems that now to use pipes you need to visit that page in your browser and then click the link that says “Get as RSS” which will give you a long URL that you can use with HungryFEED.

HungryFEED will not display an API call unless it is in RSS format (XML is not enough, it has to be RSS. RSS is a sub-type of XML). If your API call returns RSS then HungryFEED should be able to display it. However if you suggest that it is an “API” then I would strongly suspect it is not RSS. Usually developers would not refer to RSS feeds as an “API” however there are no rules so it is impossible to say without seeing the url.

The #1 problem for the url parameter getting messed up seems to be copy/pasting the url and WordPress turns it into an HTML link. If you edit the page in HTML mode you should be able to see better exactly what is in the shortcode and fix it if necessary.

Certain HTML characters in the URL can cause problems, in which case there are some debugging parameters which are explained on the HungryFEED page. In particular, check out the “decode_url” parameter.

marking as resolved since there is no more info. please re-open if you can send a url or a way to reproduce

excellent, i have made the same mistake myself and i wrote the plugin!

You can use any format of URL. When the verysimple feed displays that means the URL parameter is messed up. i have seen two reasons why that occurs:

1. You use “fancy” quotes in the shortcode (like those used in wordprocessors, not the straigh up/down quotes)

2. You copy/paste the URL from somewhere and the WordPress editor pastes in actual HTML code for the link instead of just text. You can usually spot this if the URL parameter in your shortcode is underlined like a link. The way to fix this is to go into HTML view and remove any tags, for example if you look at the code you would see something like this:

[hungryfeed url="<a href="https://mysite.wordpress.com/feed/">https://mysite.wordpress.com/feed/</a>"]

you should remove all html code so it looks like this:

[hungryfeed url="https://mysite.wordpress.com/feed/"]

I would say since 1.3 does not solve your original problem and the work-around above does, i would just put the original simplepie library back in place.

One work-around that you can do is use a feed aggregator to deal with the characterset issues, for example:

[hungryfeed url=”https://mix.chimpfeedr.com/91ac3-rss-nrg-co-il-health”%5D

This is using the service https://www.chimpfeedr.com/ as a proxy for the original feed. but it seems to fix the characterset problem for wordpress.

You can also do even more using Yahoo pipes, here is a simple one:

[hungryfeed url=”https://pipes.yahoo.com/pipes/pipe.info?_id=61eb2d31f1c74671d99c9e5b7ea498c6″%5D

Hmm, if you give me the feed url i can see if there is some work-around but unfortunately the source of the error is in SimplePie, the library on which HungryFEED relies, however is not authored by me. It would be great if the simplepie guys would resolve the issue, but as far as I know 1.3-dev is the most recent version of the library.

From previous experience I know that characterset code in PHP can be surprisingly tricky.

I just noticed that the simplepie site seems to be missing the single download package, but I have a copy of simplepie 1.3-dev. I packaged it up to simplify the process of updating WordPress:

https://verysimple.com/2011/06/18/update-wordpress-simplepie-to-1-3-dev/

Please let me know if you are able to do this on your wordpress installation and, if so, let me know if it fixes the characterset issue. I don’t know all of the changes in 1.3 but I do see that it has some new functions regarding charactersets, so I have a feeling it may fix your issue.

Hi Yigaler,

The error seems to be happening with SimplePie – which is the RSS library that is installed with WordPress. It seems to be hardcoded to UTF-8 characterset. HungryFEED uses the RSS functions that are provided by WordPress.

WordPress includes SimplePie 1.2 as a default, but this is outdated and the latest version of SimplePie is 1.3. It may be possible to update that library in your WordPress installation and it might resolve the characterset bugs…? I’m not 100% sure about that but it’s worth a try.

The file in WordPress is located at: includes/class-simplepie.php

Thanks for the message Maria, I have that in development and a new parameter “filter_out” will be in release 1.4.5

Hey Joon, That title is the title for the entire feed. You can disable that by just adding the parameter to your shortcode: feed_items=””

That tells hungryfeed that you don’t want to show the feed title or feed description.