RSS Factory and other news feeds not working - help!

I am having a new problem since Saturday. I noticed that on two of my websites the import of news items from my own blogs on these pages into the Home page were not working anymore. The RSS Factory stack from Doobox is used there. I had not changed anything. An error message says that the newsfeed can’t be imported.

Yesterday I purchased two similar stacks, in order to use them instead: Reblog (Joe Workman) and News Grid from Rapid Ideas.

Reblog JS is working on my test site (but imports the news in total), but not on my major site! (Error message “Sorry this feed could not be loaded”). Both the normal and the JS version of Reblog are not loading.

News Grid (which has the desired functionality of truncating the text) only shows on my simple test site the headlines but no text or images. On my big website there is the same error message as with the Reblog stack (“Sorry this feed could not be loaded”).

What the heck is going on? I know that I also have serious troubles with PlusKit, but I deleted PlusKit from the test project and it is a simple thing and nothing complicated.

I have RW 7.2.2 running, but also tried 7.1.7. No difference.

Any helpful hints are welcome! Thanks.


PS: I have revised the text several times by now, after testing. This is the most precise description of the issue.

1 Like

I’ve got exactly the same problem, stopped working last week for no reason - not traced it down yet!

I noticed that the developer for Social Stream updated their stack and in the update notes it said that the RSS API key was being moved to Yahoo as Google had discontinued theirs. That could be the issue for other stacks. Just a guess…

I’ve got the same problem with the RSS Factory stack from Doobox not working anymore. I’m guessing that stack is now retired because it hasn’t been on the Doobox website for a while.

I think it’s to do with Google feeds API shutting down. Barz Stacks has tweeted about it:

Found an alternative rss feed that works great by Will Woodgate:

Been testing it and it’s a good replacement just wish there was an option to turn the slider aspect of it off so it’s static with the most recent feed at the top.

I noticed there was an update to News Grid yesterday, and in the release notes it mentions that the stack is now using the Yahoo API.

I downloaded the version 1.5.1 about 24 hours ago… I can’t find any other version… But thank your for your info.

We also updated ours too from Google API > Yahoo today

And took this opportunity to add in a better, more modern layout and some nice new options:


  • Completely new design! Gorgeous masonry responsive layout
  • New options for opening links in new window, date formatting, colours, description (snippet length) and as many posts as you want
  • Support for SSL feeds
  • Now powered by Yahoo (since Google closed their RSS API)

1 Like

Meanwhile I got a development version of the stack from the developer and it works - great! Thank you, Richardet Design Support Team!

On the other hand, nothing back from the support team of Doobox concerning the non-functioning RSS Factory, even after writing to them several times.


Thank you, Michael, for the info on this stack.


‌Denn das ganze Gesetz ist erfüllt, wenn ihr das eine Gebot haltet: „Liebe deinen Nächsten wie dich selbst!“‌ Galater 5,14
Franz Rathmair | Mobil: +43 650 53 46 175 | Web:‌‌

1 Like

Managed to get the Blogger feed working across all browsers on 2 of my sites with Stacks4Stacks Feedslider but found it doesn’t work with Chrome Canary (not a major problem as Canary is a daily build development browser).

I wouldn’t expect instant support for a stack like RSS Factory which hasn’t been sold by Doobox or featured on their website for at least a year (maybe longer).

The fact that it doesn’t work anymore is because Google shut down their rss API so it’s not the developers fault. Barz Stacks has the same problem so his Monster RSS stack is also discontinued.

1 Like

Well said @Jamie1 - thanks for your understanding from a developer’s eyes :slight_smile:

Seriously, @yuzool? You are defending Doobox’ abandoning their customers to the point of ignoring requests for help? If they are simply shrugging their shoulders and leaving us to it, they should at least have the decency to say so.

(I should note that you did the right thing by fixing your own stack promptly and with good communication. So surprising you’re defending this lack of communication from Doobox.)

1 Like

Thanks @Nick

I didn’t really defend anyone per se, just was please with @Jamie1 mature and realistic answer. "Google shut down their rss API so it’s not the developers fault" I’m not speaking on behalf of @Doobox but I’m sure they have their reasons for their own pace of updates and so on, they’re only human and a small team afterall!

If you view their site ( the Stack in question is no longer for sale and maybe not for over a year as Jamie pointed out also, and doesn’t exist on the Community site anymore ( so why should they have to keep supporting something that doesn’t exist anymore? Can you think of any software that no longer exists that is still supported?

I don’t think for a second that Doobox would abandon their customers and has been a stalwart of this community for as long as I can remember.

Ours still exists and is available, so we are developing it, supporting it and making it better / bug fixing when necessary!

I don’t really want to get into a debate about anything but was just wanting to give praise to Jamie for his smart comment, tell everyone ours is updated and working and FREE to update, and hoping to then go outside and enjoy the day… :sunny:


it’s not the developers fault

I ask that you consider this from a customer’s perspective for a moment. When we buy stacks and put them on our sites, we are to a degree entrusting our livelihood to you. The front-facing site of my own organization had a big error message on it all of a sudden, and before I realized it was there and did emergency repairs, it made me and my group look unprofessional.

In situations like this, communication is critical. Is this stack kaputt and I need to look for a different solution? Is a new update coming and I just need to wait a few days? Is this perhaps a bug due to a RW upgrade and there’s already a workaround? Once I know the situation, I can move forward. Instead, I write to Doobox and get silence in return. It would have helped if Doobox had even told us “Sorry, we don’t support this any more - you’re on your own”, because then it would have been clear what to do.

Look for example at @joeworkman’s response to his Tumblr issue a few months back - he immediately posted a message here on this forum to tell people what was up, allowing people to either wait out the problem or look for another solution.

I don’t think for a second that Doobox would abandon their customers

And yet that is exactly what they have done - I and others have sent in support tickets about this issue, and to my knowledge nobody has received any reply.

There are different forms of support. I get that it’s not possible to fix every bug. But simply leaving people with no information at all is really, really poor form.


I have to say I agree with Nick - if I spend good money on a stack, then I want to know when it is discontinued, when support is going to end, if there are no updates coming, etc. If a developer can easily take our details and money when we buy a stack, then they should just as easily be able to inform us when that stack is no longer viable. That si the nature of a client relationship - some people do it well, others don’t


A quick comment from an uninvolved bystander: if the stack is discontinued, the developer should send a notice to all his customers telling them of the fact and announcing an equivalent product’s development timeline. Alternatively, he could place that announcement on his website for everybody to see. A quiet removal from the store is deceptive and unethical. Just my 2¢…


I’m not disagreeing with any of you (@Rovertek @dudeneyge @Nick)…

There are two ways I think a developer should go about it:

  1. Fix it and communicate well what’s going on - e.g as we did with Feed here:
    Feed stack - Yuzool
    People are happy with that


  1. As all 3 of you said, communicate that “it’s no longer working, won’t be fixed, here’s the deadline to get something else in place and here are some alternatives x y z.”

As @joeworkman did with Tumblr, but also as @Doobox did with his RSS Factory.

I recall he sent out a newsletter shot around the time the news broke of Google announcing that their API would be discontinued (about 1 year ago). I don’t recall the exact wording but I’m sure he offered some alternatives and gave a 1 year runway to make changes. Joe was less fortunate and had to give 30 days, but a lead time is better than nothing so I don’t believe Doobox left anyone high and dry and did communicate the changes coming. Sorry you see it that way.

Can we just be positive and believe that nobody would want another’s work to suffer or lose face with a site going down and would work like the clappers to get something fixed if they could. That’s what we do we our addons and I know all developers have pride in their work and wouldn’t want anything different.

I’m sorry this situation happened to some of you and I’m sure it’s just a misunderstanding and mis-communication situation.

I hope everyone’s RSS feeds are now displaying well - if anyone wants help with it, just reach out to the community and someone will help.

Peace out :pray:



since I posted this in the beginning, just a few facts:

I discovered the RSS Factory stack in June 2016 (either it was part of the mega deal I purchased a year before or I downloaded it at that time, I can’t remember).

Anyway, I was in e-mail contact with Doobox support twice because of it - once in June and once in October 2016. I got swift response within a day.

But I never was informed that the stack would become defunct because of Google’s changes. At least I can’t remember nor find anything in my e-mail archives.

I am still a bit puzzled that I did not get anything back from Doobox since I wrote to them with an inquiry why the stack is not working anymore.

Well - I have found another stack that does the job, so for me the issue is solved. To have received a response from Doobox would have been nice, indeed, and I expected it. But somehow - maybe with their (new?) system of customer feedback (I was asked to sign-up etc.) there was a communication breakdown somewhere in the pipeline…


Yes, my situation is exactly the same as @Franz - bought in July, never heard anything about pending termination of the stack, got no response to the ticket I sent in one week ago other than an automated message saying “One of us will get back to you real soon.”

But it’s all water under the bridge at this point. @Franz, which RSS stack did you go with in the end?