Many of us (myself included), update core along with everything else, so mostly I fire drush up. I would not advise limiting those to modules that don’t update
the database, but rather would advise getting a site clone up and running on a dev box and running though drush up in a test environment and getting yourself current.
Hopefully you’ve updated core by now… 7.32 - anything less is dangerous.
Dave
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org]
On Behalf Of Drupal
Sent: Friday, October 31, 2014 6:47 AM
To: support@drupal.org
Subject: Re: [support] Drush, list of modules to be updated, no db update
Nothing?
:(
On Oct 27, 2014, at 8:20 PM, Drupal <drupal@afan.net> wrote:
Oh! I’m sorry. My bad.
My name is Afan.
:)
On Oct 27, 2014, at 4:31 PM, Tony <tony@tony-mac.com> wrote:
What is your name ?
On Mon, Oct 27, 2014 at 2:10 PM, Drupal <drupal@afan.net> wrote:
Also, I took over a website with tons of modules to be updated. Even the core is 6-7 updates behind.
Anybody with the similar experience? Suggestions?
Thanks
On Oct 27, 2014, at 4:03 PM, Drupal <drupal@afan.net> wrote:
> Hi to all,
> I need the command to list (in Drush) of all modules should be updated but no db update needed.
>
> Tried drush up —no-core —check-updatedb but didn’t get what I need.
>
> Any idea?
>
> Thanks
>
>
>
>
--
[ Drupal support list | http://lists.drupal.org/ ]
--
--
[ Drupal support list | http://lists.drupal.org/ ]
--
[ Drupal support list | http://lists.drupal.org/ ]