OpenPublish 3-alpha3
Drupal 7.10
drush 4.5
PHP 5.3.10
After drush up I got an error
Warning: include(/var/www/openpublish.loc/html/profiles/openpublish/themes/omega/omega/templates/region.tpl.php): failed to open stream: No such file or directory in theme_render_template() (line 1382 of /var/www/openpublish.loc/html/includes/theme.inc).
Directory profiles/openpublish lost. In the directory drush-backups only empty /modules.
Well, it was just a test site.
Part of the log:
$drush -v up
... skipped...
Code updates will be made to drupal core.
WARNING: Updating core will discard any modifications made to Drupal core files, most noteworthy among these are .htaccess and robots.txt. If you have made any modifications to these files, please back them up before updating so that you can re-create your modifications in the updated version of the file.
Note: Updating core can potentially break your site. It is NOT recommended to update production sites without prior testing.
Do you really want to continue? (y/n): y
Executing: mkdir '/var/www/openpublish.loc/html/drupal-7.12'
Executing: svn info '/var/www/openpublish.loc/html/drupal-7.12'
Executing: bzr root '/var/www/openpublish.loc/html/drupal-7.12'
Executing: wget -P . 'http://ftp.drupal.org/files/projects/drupal-7.12.tar.gz'
Downloading drupal-7.12.tar.gz was successful. [notice]
Md5 checksum of drupal-7.12.tar.gz verified. [notice]
Executing: tar -C '/var/www/openpublish.loc/html' -xzf 'drupal-7.12.tar.gz'
Executing: tar -tf 'drupal-7.12.tar.gz'
Project drupal was updated successfully. Installed version is now 7.12.
Backups were saved into the directory /var/www/drush-backups/openpublish/20120207101718/drupal. [ok]
Rolling back update of Drupal core code ... [notice]
Executing: svn info 'drupal-7.12'
Executing: bzr root 'drupal-7.12'
Backups were restored successfully. [ok]
Rolling back update of Views Boxes code ... [notice]
...skipped...
Executing: svn info 'profiles/openpublish/modules/custom/apps'
Executing: bzr root 'profiles/openpublish/modules/custom/apps'
Backups were restored successfully. [ok]
Command dispatch complete [notice]Repeatedly:
$drush -v up
Initialized Drupal 7.10 root directory at /var/www/openpublish.loc/html [notice]
Initialized Drupal site default at sites/default [notice]
require_once(/var/www/openpublish.loc/html/profiles/openpublish/modules/contrib/entitycache/entitycache.module): failed to open stream: No such file or directory bootstrap.inc:3004 [warning]
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: require_once(): Failed opening required '/var/www/openpublish.loc/html/profiles/openpublish/modules/contrib/entitycache/entitycache.module'
(include_path='.:/usr/share/pear:/usr/share/php') in /var/www/openpublish.loc/html/includes/bootstrap.inc, line 3004
ob_end_clean(): failed to delete buffer. No buffer to delete drush.php:184 [notice]
Drush was not able to start (bootstrap) Drupal. [error]
Hint: This error can only occur once the database connection has already been successfully initiated, therefore this error generally points to a site configuration issue, and not a problem
connecting to the database.
Drush was attempting to connect to :
Drupal version : 7.10
Site URI : http://default
Database driver : mysql
Database hostname : localhost
Database username : openpublish
Database name : openpublish
Database : Connected
Default theme : frame
Administration theme: rubik
PHP configuration : /etc/php.ini
Drush version : 4.5
Drush configuration:
Drush alias files :
Drupal root : /var/www/openpublish.loc/html
Site path : sites/default
Modules path : sites/all/modules
Themes path : sites/all/themes
File directory path: sites/default/files
%paths : Array
You can select another site with a working database setup by specifying the URI to use with the --uri parameter on the command line or $options['uri'] in your drushrc.php file.
Comments
Comment #1
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to
closed (duplicate).Please ask support questions on Drupal Answers.