I would like to help with this plugin

Same here… well mostly point 2 and changing a few things here and there. Unfortunately, the plugin doesn’t have any license information, but since it’s published on here, I’m going to assume that it is licensed under the GPL and go ahead and fork it for my private purposes.

All software that you’ll find on www.ads-software.com in the Plugins Directory and the Themes Directory must be licensed under the GPL v. 2, or a compatible license. This ensures that all software on www.ads-software.com is free as in speech and free as in beer.

Jon, if you care, I can set up a new repo and I’ll give you access to it.

Never mind, the readme does have a license statement and explicitly states GPLv2 or later.

Did either of you end up porting and bringing this plugin up to speed?

Thanks!

Yes, I have. I also requested and got svn access for the fork, but I’ve not committed any code yet. Currently it’s on github.

But I’ll try and commit the code today. (Thanks for the reminder ;))

@kwisatz Awesome, thanks!

The plugin is now also in wordpress svn and available from https://www.ads-software.com/plugins/ge-rss-reader/

Thanks! Do you have any plans to include the post excerpt? That’d make it essentially gold to me.

Adam, not sure what you mean. There’s already a possibility to display and shorten item descriptions.

@kwisatz Sorry for being unclear. I think I might have confused this plugin with another—you know how it goes when you’re interviewing several for a job. I’ll look at it again today and get back to you if I do, after all, have an actual request. ??

@kwisatz On install, I get an invalid header error. ??

Adam, can you open an issue on https://www.ads-software.com/support/plugin/ge-rss-reader and provide any details such as

* the WP version you’re using,
* the PHP version, and
* any info you get when you set WP_DEBUG to true in your wp-config.php and then try activating it again?

I’ll need that information in order to attempt to reproduce the issue. On my development setup it activated without a hitch.

Okay, not sure what changed, but it appears to be working fine now. If I get another error, I’ll log it in the Support area for the plugin. Thanks for your responsiveness!