It would be nice if an RSS feed could be created so that when a module it is updated it will be listed on the RSS feed.

This will make it really easy to monitor many sites.

Comments

dww’s picture

do you mean an RSS feed generated by this module for specific sites that are out of date, or do you mean an RSS feed of new release nodes directly from drupal.org? if you're talking about the later, see http://drupal.org/node/94138. if you're talking about the former, seems kind of scary to make an RSS feed available for when your site is out of date, no? ;) i guess it'd have to be a feed that requires authentication and all of that. sounds like kind of a hassle. personally, seems like it be a lot easier to just do the email notification stuff folks are talking about in http://drupal.org/node/124715.

can you please clarify exactly what you have in mind?

thanks,
-derek

gordon’s picture

The RSS feed that I am suggesting would be a list of all the modules that are out of date on a site.

This way you would get notified when a module on a site is out of date.

mfer’s picture

+1 I would love to have this feature, too.

How would security be handled on this feed? I don't want to broadcast to the world what out of date and security holes I have in my site. Like many, i don't update immediately all the time. Any thoughts?

I was thinking 2 possibilities. One would be the feed being password protected. While that's great it won't work in some feed readers. Or, having something like /admin/log/updatestatus/feed/somefeedkey.

In any case I think the feed should be optional and maybe configurable to which choice of the two above. Oh, and it would be nice to track subscriptions on this feed.

gordon’s picture

I see it working based upon the user security now, and using something like httpauth http://drupal.org/project/httpauth to provide access to secured feeds

merlinofchaos’s picture

Hmm. An RSS feed *would* make for a convenient way to see the status of several sites at once. I'll consider patches. Access to the RSS feed will be the same as access to the admin page, but adding httpauth module will help people out.

dww’s picture

Title: RSS Feed for the admin/logs/updates » RSS Feed for the admin/reports/updates
Project: Update Status » Drupal core
Version: 5.x-1.0 » 7.x-dev
Component: Code » update.module

I'm not adding new features to D5 update_status in contrib. The next best chance to see this feature is in D7 core, if someone wants to work on it before the code freeze...

dave reid’s picture

Version: 7.x-dev » 8.x-dev

Bumping to 8.x

brianV’s picture

+1 on this. However, we would need some kind of 'external' hash that maps to a user account so that access to this feed could be managed on a per-user basis.

Maybe hash the password hash, and store it as an 'external hash in the user table? Then, given a url like node/reports/updates/feed/, you could fetch the related user account based on the external hash, check if the user has the appropriate permission to view the hash, and return a feed.

Would appreciate any further feedback / input.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

Wonder if this is still a valid request for D10? Know you can receive emails about outdated modules

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

There hasn't been a response in the past two years or so to indicate that the community is interested in this.

The proposal doesn't met the Criteria for evaluating proposed changes. In this case, there is not demonstrated demand and support for the change.

If there is interest in this re-open the issue and add a comment. Or open a new issue and reference this one.

dww’s picture

Yeah, I don’t think we’re ever going to add this. 😅

dww’s picture

Status: Closed (works as designed) » Closed (won't fix)

More accurate status