Problem/Motivation

I tested the d7 to d8 upgrade path on my local dev system, and I failed to complete the process.

Steps to Reproduce:

  1. `drush dl drupal` (drupal 7.22)
  2. `drush si --db-url....` (standard install profile)
  3. Added two nodes, one basic page, one article with tags and an image. Each node with link in menu.
  4. Deleted all files outside sites directory
  5. `wget http://ftp.drupal.org/files/projects/drupal-8.x-dev.zip` last updated April 8, 2013
  6. Copied all files except sites directory into drupal root directory
  7. Visited example.com/update.php
  8. Was redirected to example.com/core/update.php
  9. WSOD
  10. Visited example.com and got this error message: `Fatal error: Call to a member function get() on a non-object in \path\to\drupal\core\lib\Drupal.php on line 212`

My system:

  • Windows Vista 64bit
  • Xampp 1.8.1
  • PHP 5.4.7
  • Apache 2.4.3

I expected the update to run without errors, instead of the white screen of death. I'm having trouble tracking down an error related to update.php in my error log, but I'm definitely seeing a 500 status code in my access log.

Proposed Resolution

Discover whether the problem is my system or patch/commit drupal-8.x branch.

Comments

wusel’s picture

My hint:
Please look at http://drupal.org/node/1965402#comment-7312822

Good luck!

Wusel

rupl’s picture

This also happens on a fresh install on Linux 3.2.0-40-virtual #64-Ubuntu SMP x86_64 running PHP 5.3.10

wusel’s picture

@rupl (#2):

Please write a notice on #1948390: [Meta] Upgrade to D8 from D7: regular testing needed on various OSs with different versions of php and other unique situations too!

Thank you very much!

Wusel

Added:
Did you make the settings.php file writeable in front of changing to D8 / running update.php?

rupl’s picture

rupl’s picture

and yes I had settings.php set to 777

wusel’s picture

Thank you very much for this informations.

Wusel

wusel’s picture

Issue summary: View changes

Updated the issue summary with a link to a related issue.

marcingy’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

Updates are now via migrate