Hi, As with any software and following the methods outlined by drupal for updating, always backup the original data. Create an environment for testing and do the updates there firstly. Never work on live or production environment, only deploy to production. It's going to require more effort but you can't avoid it. No matter how perfect your site is if it is not backed up it doesn't exist. On 31 Oct 2014 09:54, "Drupal" drupal@afan.net wrote:
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/ ]
--
*Anthony Stefan Maciejowski*
*http://about.me/TonyMac http://www.about.me/TonyMac*
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]