this is where wordpress has gone in the most recent iteration, and so as a result all wp module devs have begun to enable one-click upgrading - shouldn't drupal be there too??

this module sounds like exactly the right first step in this direction and feels an awful lot like something that should be in core - just as 'status' updates are in there now...

thoughts?

Comments

alliax’s picture

Yes of course it should, although I kind of miss the time not so long ago when we'd still have to fill in the database structure by ourselves, no easy install script.
I understand easy is better to gain larger audience and that's why Mambo/Joomla has attracted a larger audience in the same time. So yes this should be in core for modules. But for me I'm fine with the way it is :-)

kbahey’s picture

Yes, it should be in core.

But before that, it has to be polished and bug free as a contrib module first, proving it is robust enough.

Only then can it be considered for core.

So, testing is welcome.

pasqualle’s picture

Title: if perfected, this should be in CORE drupal - right? » port to D7
Version: 6.x-1.1 » 6.x-1.x-dev

the required first step to include Plugin Manager in Drupal core is to have a D7 release..

kbahey’s picture

Title: port to D7 » Plugin Manager should be in Drupal core

It needs to be feature complete and bug free in D6 before porting to D7 can start. Right now it is in flux with previously working features broken, while new features are being put in.

It also needs automated tests, since nothing makes it to core now unless it has tests.

I am also concerned that D7's API has not been cast in stone yet (code freeze).

Anonymous’s picture

Status: Active » Postponed

As much as I would love that, kbahey has a great point. Fair sized chunks of code are being added or replaced on a near daily basis. There are several features which have probably only experienced a minimal amount of testing from the community. Eventually I would love to see it as a part of core. Right now, however, I think all available effort needs to go into testing, so that the current feature set can prove itself.

darumaki’s picture

I have two concerns about using this module

How will the module know if its an official release or development and also how will it know if its for drupal 5 or drupal 6 ?
Is this all automated ?

pasqualle’s picture

@darumaki: your question is off topic (it is not even related to this module), you should create a new support issue..
short answer: yes it is automated. the functionality was developed with the http://drupal.org/project/update_status module..

jabapyth’s picture

the plugin install process is automated just enough to make your life easier, without surrendering your control over the install. You can select which version of a module you want to install. Also, versions are automatically checked for compatability with your drupal installation.
long story short: try it out. install it, and see for yourself how it works.

giorgio79’s picture