Module Upgrade within Quickstart [#1669462]

I have just started using Quickstart 1. Being a Linux novice, it has been a treat to see this get up and running. There are really no issues yet, except this one, and I hope that it is just needing an explanation. D7's module upgrade has been a great improvement, but using it inside of quickstart triggers an authorization request for an FTP connection that requires a user name and password. It seems to be an obvious problem as everything is local. Would someone please share their solution with me? Maybe a Drush work around? I'm obviously new to Drush as well, so I will most likely need a detailed description. Any help is really appreciated. It would be a shame to have to go back to manual procedures. Thanks

Bob

I can't seem to edit the typo in the title, oh well.

Comments

Comment #1

MichaelCole CreditAttribution: MichaelCole commented 11 July 2012 at 16:36

Status:

Active

» Closed (fixed)

Hi Robatk,

Thanks for the great feedback!

This situation has to do with the Drupal Upgrade feature. Search for that and you'll be well on your way!

Mike

Comment #2

robatk CreditAttribution: robatk commented 14 July 2012 at 05:39

Mike, you're welcome. You are doing a great job and there is tremendous potential to make Drupal much more available to the average user, but your answer is a little too vague to be of much help. Presently, my working solution is to upgrade the staging install, then download the new module and DB backup, and then update the database on the localhost. Not very efficient, but it works. The Drupal work around isn't practical because most modules are not implemented. Your use of the term 'features' is open to interpretation, did you mean that generically or were you referring to the features module?

If you, or for that matter, if anyone wants to give this project a great big push and really enable a lot of very rapid development, I think that the hard part is already done. What we (I) need is the functional documentation on how to install distributions under Quickstart to easily expose the various "features" that have already been developed. Someone made an attempt at http://drupal.org/node/1529574, but I have not been able to make it work. If this one step was adequately documented so that nb's can use the "features module" to import them into their own site, that would open up all kinds possibilities. Right now though, I'm stuck and I really need someone to take a minute to help me. By the way, the "features module" really needs to have a name change.

Comment #3

robatk CreditAttribution: robatk commented 14 July 2012 at 09:34

Mike,

It looks like I need to back up a bit and take another look. I have been using QS ver.1 because the desktop was a more natural fit, but I tried the distribution install mentioned above and it work fine in QS ver.2 I haven't isolated the cause, and probably won't, but what I see now is that the distro's have to support the drush's make process to get it to work. So the burden is really on the distro developers. I suppose that one could create them one at a time, but that defeats the whole purpose, doesn't it? What I'm looking for would have to be implemented at the 'best practice' level, so I guess that I'll have to move on to a different approach. Too bad. Maybe someone created a list of supported distros?

Comment #4

liquidcms CreditAttribution: liquidcms commented 15 November 2012 at 16:44

Status:

Closed (fixed)

» Active

i agree, a little more of a clue would be useful.

i am also getting this. i have been using Drush to update modules and when i try with a certain project i get it asking for my quickstart password. after entering that, drush just hangs.

only obvious difference is that the site which i can't update is D6; the ones that have worked have been D7.

Comment #5

firfin CreditAttribution: firfin commented 28 December 2012 at 01:24

Title:	Module Upgrade within Quictstart	» Module Upgrade within Quickstart
Status:	Active	» Postponed (maintainer needs more info)

The original post was about requiring a ftp username and password. You seem to be having difficulty with drush up ? I don't see this as being the same issue. This might be resolved quicker as a new and seperate issue. Have you read Tips for making a good issue report ?

That being said, I have experienced similar issues with drush to update modules. Those problems were alleviated with the tip in the documentation