Postponed
Project:
Plugin Manager
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Nov 2008 at 19:51 UTC
Updated:
2 Sep 2010 at 18:40 UTC
Jump to comment: Most recent
Comments
Comment #1
Antinoo commented+1
Comment #2
Anonymous (not verified) commentedAt the moment, that would make me feel quite nervous. A mistake could take out an entire installation.
Comment #3
Anonymous (not verified) commentedComment #4
Antinoo commentedJoshuaRogers: "use at your own risk", "please BACKUP files and db before using this", and so on ;-)
However, I'll respect your choice.
About 20 days ago I tried to code it in my own, but I did get permission errors using the ftp_* functions and then I did suspended the work.
I'm going to take a look at plugin_manager source code, to retry to complete it.
If it works, I'll send the source code to you. :-)
Giovanni
Comment #5
Anonymous (not verified) commentedSounds good. If you get a patch worked up, I'm willing to commit it. Granted, I'll probably append the world's largest WARNING in front of it... :P
Comment #6
dave reidYes, this would be something definately looking into accomplishing if we really wanted to push this module into core itself.
Comment #7
bserem commented+10
I was just discussing this here: http://drupal.org/node/360656
I'm positive to drupal-core being updated from inside itself, and I don't mind you placing 2 pages of warnings! :)
it is a great module the one you are trying to implement, keep up
Comment #8
Anonymous (not verified) commentedI can tell you that this is definitely on my wish list. For what it's worth, it won't stay on "postponed" forever. Only until plugin_manager's stability gets to the point that I would trust it with a full Drupal install. That will probably be another few releases yet.
Comment #9
summit commentedSubscribing, interesting in this a lot also!
Greetings, Martijn
Comment #10
DrewMathers commentedI think some kind of rollback mechanism would be essential. In case of unrecoverable errors it should automatically roll back within two cron runs unless cancelled. For my own updates, I implement a manual rollback mechanism by installing the new core files in a new directory, then re-point my domain docroot.
Comment #11
espirates commentedWordpress I believe is setup to auto upgrade and does it very well so why shouldn't Drupal have this capability, can't be too difficult if WP can do it.
Comment #12
DrewMathers commentedFor details of how WordPress does this, see:
http://wordpress.org/extend/plugins/wordpress-automatic-upgrade
Two hightlights of the process are backing up the old installation and disabling/re-enabling contrib modules. Backup could be accomplished with the Backup And Migrate module, and the Contrib_Toggle module can manage the dependencies for disabling contrib modules.
http://drupal.org/project/backup_migrate
http://drupal.org/project/contrib_toggle
Comment #13
alfthecat commented+1
I'd like this too, although it would also be a bit spooky (like Einstein's 'spooky action at a distance') so the rollback mechanism should be very reliable in case of catastrophe resulting from an update.
D7 has a similar feature implemented in core, right? And perhaps the Backup & Migrate + Backup & Migrate Files could offer assistance in the rollback feature....
Anyway, thanks for this module!
Comment #14
DrewMathers commentedA core update feature is planned for the new Update Manager module, but the feature has been postponed until D8. You can follow progress at #606592: Allow updating core with the update manager
This may present an opportunity to fill this void either in D7 Plugin Manager or a separate Core Update Manager module.