By drriley on

Has anyone considered a module, or written one of their own, that will, similar to the way Firefox does for extensions, check for updates to modules (either at a predefined interval or upon admin activation)?

It really is a pain, particularly when using many modules, to conduct periodic manual searches for updates to modules, followed by manually download and installation of those updates.

I can't be the only person who would love to see this functionality.

⋅ Categories: Drupal 4.6.x

Comments

kae’s picture

kae commented

what a good idea

Samat Jain’s picture

Samat Jain commented

Most people run Drupal on a UNIX system, in the common Apache virtual host setup. This and the UNIX security model makes it difficult to do what you want: automatic downloading and installation.

It's not that much different for Firefox on UNIX systems either. That is, a user cannot update a system's Firefox installation, it has to be done by the superuser.
__
Personal home page | Rhombic Networks: Drupal-friendly web hosting

SeanK’s picture

SeanK commented

You might want to look at this thread:
http://drupal.org/node/52330

satori1984’s picture

satori1984 commented

...but in the meanwhile we could all use some alternatives to ease the pain :)

(as mentioned in the handbook)

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

displays info on updates,

http://drupal.org/node/48602

satori1984’s picture

satori1984 commented

On 4.6.x it gives a
Fatal error: Call to undefined function drupal_get_form() in /modules/systeminfo/systeminfo.module on line 235

According to Drupal API, drupal_get_form() doesn't exist in 4.6.
I guess I'll check for updates by hand for a little while longer :)

sepeck’s picture

sepeck commented

Chicken and egg syndrome. Had to design and then build the back end infrastructure before you could get the client stuff to work.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide