Timeline for How to quickly update/reinstall using Drush 4.x
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 19, 2012 at 13:40 | comment | added | Paul B | Deleted FLAGS from the sites/modules/ DIR, ran Drush cc all in CLI, took sometime and I thought it had hung but then it came up with a green 'success'. So I'm halfway there. Ran Drush up, waiting then 'Done'. I have an option to update now. | |
May 19, 2012 at 13:38 | comment | added | arjan | Troubleshooting this may take some time, but I don't see any reason for the database to be corrupted now. It's only an error in the code. It may even just be a caching problem if you have the new Flag module in place. Or maybe you need to update to a more recent version of Rules as well. So many things to try. | |
May 19, 2012 at 13:33 | comment | added | Paul B | Still get this error, PHP Fatal error: Class 'RulesIdentifiableDataWrapper' not found in /var/www/thesitename/sites/all/modules/flag/flag.rules.inc on line 27 Drush command terminated abnormally due to an unrecoverable error. [error] Error: Class 'RulesIdentifiableDataWrapper' not found in /var/www/thesitename/sites/all/modules/flag/flag.rules.inc, line 27 | |
May 19, 2012 at 13:31 | comment | added | arjan |
So you currently have the current Flag in the modules folder? Try clearing the cache. You can try drush cc all (this may not work due to the error, but try it a couple of times anyway. I've sometimes had it work only after several tries in similar situations). Otherwise you can manually empty cache tables (Truncate), e.g. from phpMyAdmin.
|
|
May 19, 2012 at 13:31 | comment | added | Paul B | Ive been at this since 11.00gmt, and today never made any paper notes. Looking at my Drush log, can't see at the moment what I did but it was nothing more than drush up etc in the site's home. ( I have multiple projects running all separate d7 installs, mostly for forthcoming commercial projects off my own bat. God help us supporting D7 then me thinks!!). As stated else where I'm a newbie upskilling for Drupal projects but off my own bat. I'll try the delete Flag DIR now see if Drush ignores it, would rather fix than trash 6 weeks work prior to last major SQL backup. | |
May 19, 2012 at 13:21 | comment | added | arjan | What Drush commands did you execute? It's possible that while doing these updates the combination of different versions created a problem, or the order in which modules were upgraded in your particular case was problematic. But it doesn't look like the database itself would be corrupted (so you can still do a backup from phpMyAdmin), it's just that Drupal tries to execute all the current code, and the error prevents it from continuing. So try removing the flag module and then putting the current version in there (Drupal expects to find that module). | |
May 19, 2012 at 13:20 | comment | added | Paul B | Alas no joy, neither of your suggestions work. I have read drush.org previously and cannot find a solution. | |
May 19, 2012 at 13:13 | history | edited | arjan | CC BY-SA 3.0 |
some additions / small edits
|
May 19, 2012 at 13:11 | comment | added | Paul B | Thank you for your prompt response Arjan. Indeed DB backups I appreciate are always 100% essential, and did so yesterday, but now I cannot get into the D7 backend due to a frontend white screen. Flag was an older version along with many others including the D7 at v7.0. Being a newbie with some basic knowledge and trying to get upto speed with Drupal upgrade adin, I took the Drush and this morning it corrupted what was even, though an old version, site a working one at that. I could try simply deleting the whole flag DIR on my lampbox, seems nothing left to lose now except recent changes. ))-: | |
May 19, 2012 at 13:07 | history | edited | arjan | CC BY-SA 3.0 |
some additions / small edits
|
May 19, 2012 at 12:59 | history | answered | arjan | CC BY-SA 3.0 |