Help w/ Drush

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
zachatharsis's picture

So from the discussions in the EduBoF @ Drupalcon, I came back and began playing with Drush. My first attempt was successful and easy to implement. I was able to perform updates on 3 seperate drupal installs (Drupal6, Drupal7, and OpenAtrium) running on my Ubuntu laptop.

However, I decided I would then begin playing with Drush on my development Intranet site (running CentOS). Well, somehow after getting Drush to run (I had to change some php.ini settings), I jacked up my site. I've tried poking around the web looking for some direction but haven't gotten anywhere as of yet.

I'm looking for some help on how I might be able to "undo" the Drush changes so I can get the Intranet back and usable and also tips and best practices for getting Drush setup and being able to test it before doing an upgrade.

Any help would be greatly appreciated. Thank you.

Comments

I don't imagine it's Drush

markwk's picture

I don't imagine it's Drush that's making trouble since Drush is just a script, it's the changes you made. What exactly did you do?

Do you have a backup to revert to?

No drupal changes

zachatharsis's picture

Essentially I didn't do any changes to Drupal itself or my site. I installed Drush 3.3 and then had to edit a line in my /etc/php.ini file to get it to run. Once I got that happy, I ran drush up.

I do fear that I did NOT run drush sql-dump and thus don't have a drush dump of my sql db.

I do have msql dumps and rsync's of my stuff but was curious as to what if any backup drush may have created and if there was an easy way to just undo it. I haven't actually ever had to do a complete restore from sql dumps and files before (still mostly a noob) but am familiar with the concept.

Mainly I was looking for the easy and quick way back to base.

Also if it's open atrium, you

markwk's picture

Also if it's open atrium, you should be able to revert your features either via the web interface or via drush
1. drush fl /// this will show what features you have and which have been overridden
2. drush fr // will revert to version in code.

Hope that helps.

Not open atrium

zachatharsis's picture

Drush did work fine on my test box running open atrium however, this Intranet was build w/o using OA. Just drupal core and modules from the ground up.

I'd recommend you roll it

markwk's picture

I'd recommend you roll it back to your previous dump.

I am not entirely sure what versions of drush I use on my two drupal servers but since I use Aegir with Drush & Drush_Make, my setup isn't entirely the same. I am not sure if you use non-Drupal sites and other control panesl, but I personally am a stronger believer in Aegir project. It automates the process and makes rolling back super simple.