Voting starts in March for the Drupal Association Board election.
We are running a multi site setup on Drupal 6.22. We had been running on Drupal 6.20 and recently updated to 6.22. Several years ago, we created a RSS feed and block on each of the subdomain sites to pull into the subdomain site and put in a block on the front page specific content we created on the main domain site that had a certain taxonomy term. This was how we maintained an ''announcements'' feature on the subdomain sites.
On each subdomain site we enabled the block created by the feed and assigned it a space on our theme in the left sidebar. It worked great. The block appeared when we had a fresh announcement; it disappeared when the aggregator limit had been reached -- 3 days but the block REMAINED enabled and assigned to the right space. And when we posted a new piece on the main domain site with the correct taxonomy term it would appear, like clockwork, on the subdomain sites. Swell.
Now, we have updated to 6.22. We do not know whether the update is related, but what we do know is that the feed aggregator block that we set up does not stay visible -- it disappears after several hours AND the block itself becomes disabled and is no longer assigned to a region on the theme. We manually re-enable the block and it will reappear again, but only for a few hours.
We thought that perhaps the feed we set up had become flawed; we created a new one, same behavior -- disappeared from the sidebar AND from the enabled block list within a few hours.
We thought it might be related to the cron running on the server, but we don't think so. Timing is not right. We run cron only once a day. We have asked our server folks to look to see if there is anything in cron that could be doing this but they say no, doesn't appear so.
We are operating poormanscron. Could this be a problem? If so, why would this all of a sudden be a problem. We've always run poormanscron.
Is it possible that with the Drupal update, the aggregator module behaves differently with a feed coming from the main domain?
I apologize that this support request is a bit vague. Frankly, I don't know how you can replicate this unless you have a multisite setup. And I have searched high and low in the issues, forums and groups to see if I could find any reference to this or anything like it. The only thing I saw that was related was that some folks lost all or many of their blocks upon updating Drupal, but that does not seem to be the problem here. And what makes this difficult is that it was working; now it isn't.
Any help -- suggestions on how we could trouble shoot this -- would be most appreciated. And if anyone has ever run into this, please offer some ideas to us on how we can fix this.
Thanks so much.