But what I am planning to do is make errors invisible / hidden in the next version, so if there is a temporary problem it does not affect the site.
When our site has had the so called feed issue it can last for a long time and hiding the problem will only mean we have server monitoring modules on the site not showing accurate info.
This issue never used to be a problem in the older versions of LGSL so something must have changed. I'm not qualified to point out where this problem stems from but hiding the problem doesn't seem to be the correct solution.
I might try going back to older an version of LGSL just to test. If it's not the feed, the same website hasn't moved hosting then maybe its LGSL current version.
Edit: I now have LGSL v5.1 running on a testsite...
On our website we have 3 LGSL modules on the home page and on the test site I only have one LGSL module. Since setting up the older version on the test site I've had the feed problem on our website with three LGSL modules but the single LGSL on the test site was working fine.
I then thought maybe this issue could have something to do with running multiple LGSL modules more than it being a feed issue. I'm now only running 1 module on both sites and both have been working OK.
Out of curiosity how many of you guys having these feed issues are running more than one LGSL module?