Problem/Motivation

The test bot can do upgrade tests but manual upgrade tests more OSes , PHP versions, special circumstances and who knows what else. Update is extremely finicky.

The bot is useful and the tests are very good keeping it mostly sane.
The testbot can't test rewriting settings.php. Note: this is being fixed.

Proposed resolution

Get people to regularly test the upgrade.

Before you begin testing, be sure your system meets the requirements.

Drupal 8 requires PHP 5.3.10 PHP 5.4 or later, with the CURL extension.

OS

  • Windows
    • Windows 8: 2013-03-29 (#30 (fail), #50 (success, same user))
    • Windows 7: 2013-04-05/2013-04-17 [ok] (#35)
    • Windows Vista: 2013-04-17 [broken] (#39, #42)
  • Linux
    • Archlinux: 2013-03-23 (#7)
    • Ubuntu 10.04: 2013-03-24 (#9, #13, #15)
    • CentOS: 2013-03-28 [ok](#29)
    • Debian: 2013-05-06/2013-05-12 [ok](#49, #51)
  • Mac
    • Mac OS 10.8.3: 2013-04-07 [ok] (#36)
    • Mac OS 10.8.3 (MAMP): 2013-03-26 (#24) [PHP Fatal error: Call to a member function get() on a non-object in /drupal/core/includes/bootstrap.inc on line 2471]
    • Mac OS X 10.6.8 (MAMP 2.1.3): 2013-05-24 [ok] (#52)
  • (list others)

PHP version

  • 5.3.23 -- 2013-03-28 [ok] (#29)
  • 5.3.10 -- 2013-03-24 (#9, #13, #15)
  • 5.3.18 -- 2013-04-17 [broken](#42
  • 5.3.x -- ?
  • 5.4.13 -- 2013-03-23 (#7)
  • 5.4.3 -- 2013-03-29 (#30 (fail), #50 (success, same user))
  • 5.4.10 -- 2013-04-07 [ok] (#36)
  • 5.4.7 (e.g. XAMPP 1.8.1) -- 2013-04-05/2013-04-17 [ok] (#35) / 2013-04-08 [broken] (#39)
  • 5.4.x--?

Remaining tasks

  • (ongoing) test, make a comment retest once every two weeks or so. make a comment on this issue saying "I tested on X OS, with php version A.B.C and the result is: [it worked|it blew up with Z error]." (Why? Making a comment saying it was tested helps us know testing is being done and stuff is working ok.)
  • (ongoing) update summary update the issue summary near the OS saying: Y-M-D [ok|broken] #XX, for example near Windows: 2013-03-10 [ok] #11. (Why? That way we know more info is in comment #11 about that test. And people can easily see what has been the longest since it was tested.)
  • (ongoing) create follow-up issues File individual issues for problems found, and link them from here. Tag them with: D8 upgrade path (Why? because this would get overloaded if we fixed the problems here.) Assign the issue to: chx. Docs on making good issues: Issue summary: http://drupal.org/node/1427826 and Steps to reproduce http://drupal.org/node/1468198

Steps to test

  1. Install d7.
  2. Create a node or two.
  3. Put the d7-site into maintenance mode (to avoid running of cron, which makes the settings.php file readonly).
  4. Make the settings.php file writeable.
  5. Upgrade to d8.

Related

See also for perspective:
http://drupal.org/project/issues/search/drupal?issue_tags=D7+upgrade+path

Check if you can install a clean d8 (not an upgrade). If you have trouble getting a clean 8.x to install, check http://drupal.org/project/issues/search/drupal?issue_tags=d8%20dev%20env... and/or open an issue with the d8 dev environment tag.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

YesCT’s picture

fixing tags.

xjm’s picture

There are lots of database dumps included with the test suite for testing the upgrade path. In particular, I'd suggest installing the database found in:

core/modules/system/tests/upgrade/drupal-7.filled.standard_all.database.php.gz

Someone could extract that and check which point release of D7 it was created with. Then it would just be a matter of setting up a D7 site pointing at that database and upgrading to D8. Someone could try that manual process now and document any issues they had with it or things that didn't work. :)

Then, if that works, the relevant supplemental DB dumps in that directory could be installed on top of it.

xjm’s picture

Issue summary: View changes

updated with placehold for last tested

YesCT’s picture

Status: Active » Postponed

#1948650: Update is broken is an example, and has the database dumps.

chx will turn the php dumps into sql and put them here so they can be used. But also note that actually testing the same dumps as the bot tests is of limited utility. Ad hoc and real life databases are much better.

This issue will be updated when that is fixed. Postponed on that issue (that means we dont need manual testers to test until that known issue is fixed)

Also related #1949724: Allow simpletest child sites to additionally load a test-specific settings.php to allow testing anonymous and configless updates

YesCT’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

Status: Postponed » Active

Active. Since #1948650: Update is broken is fixed.
Go manual testers.

jackmc’s picture

I'm keen to help out with testing, but am struggling to get the upgrade to work. I think I'm doing everything sensibly, but it seems to error out before I can get started. See error log. I'm following these instructions.

This is a pretty standard ubuntu box, running PHP 5.3.2-1ubuntu4.19.

This will (hopefully) be my first contribution to Drupal if I can get it working :)

tim.plunkett’s picture

As of this past week or so, you will need PHP 5.3.10. Thanks for helping!

farhadhf’s picture

I tested on Archlinux, with PHP version 5.4.13 and it worked - I didn't see any problems in the upgraded site.
There were just a few

Debug:
'Missing handler: node created sort'
in views_get_handler() (line 929 of core/modules/views/views.module).

debug outputs when the upgrade is finished (in update.php?op=results).

xjm’s picture

Issue summary: View changes

added related issues and clarified why it was postponed

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Issue summary: View changes

Updated issue summary.

jackmc’s picture

Retested using Ubuntu 10.04, running PHP 5.3.10-1ubuntu2ppa6~lucid.

On visiting /core/update.php, I see the following error in the log, and frontend returns blank white screen.

PHP Fatal error:  Call to a member function get() on a non-object in /var/www/core/includes/theme.maintenance.inc on line 59
PHP Stack trace:
PHP   1. _drupal_exception_handler() /var/www/core/includes/bootstrap.inc:0
PHP   2. _drupal_log_error() /var/www/core/includes/bootstrap.inc:2266
PHP   3. drupal_maintenance_theme() /var/www/core/includes/errors.inc:185
PHP   4. _drupal_maintenance_theme() /var/www/core/includes/bootstrap.inc:2648
xjm’s picture

@jackmc How recent is your copy of Drupal 8? Did you fetch the latest commits as of when you tested? That is the error from #1948650: Update is broken which was fixed two days ago, so if you haven't updated D8 since then, that's why.

jackmc’s picture

I took it from http://drupal.org/node/572834. I can get it from Git if that is the correct method, will test that a bit later today.

Apologies, I'm new to this..

xjm’s picture

Thanks @jackmc! Yeah, git is best for testing D8, since it changes so rapidly. Hopefully it doesn't show the same error after updating or we have a really big problem. :) (If it does though--that's important to know!)

jackmc’s picture

No worries, I'm happy to (try to) help!

Again with Ubuntu 10.04, running PHP 5.3.10-1ubuntu2ppa6~lucid, and Drupal from Git this time, I get this error when I hit /core/update.php

PHP Fatal error:  Call to a member function get() on a non-object in /var/www/core/includes/bootstrap.inc on line 2471
PHP Stack trace:
PHP   1. {main}() /var/www/core/update.php:0
PHP   2. update_prepare_d8_bootstrap() /var/www/core/update.php:410
PHP   3. drupal_install_config_directories() /var/www/core/includes/update.inc:112
PHP   4. drupal_rewrite_settings() /var/www/core/includes/install.inc:464
PHP   5. file_put_contents() /var/www/core/includes/install.inc:310
PHP   6. _drupal_error_handler() /var/www/core/includes/install.inc:310
PHP   7. _drupal_error_handler_real() /var/www/core/includes/bootstrap.inc:2248
PHP   8. _drupal_log_error() /var/www/core/includes/errors.inc:77
PHP   9. watchdog() /var/www/core/includes/errors.inc:212
PHP  10. module_implements() /var/www/core/includes/bootstrap.inc:1795

I hope I'm not doing anything wrong while trying to test it, I'm going to try again from scratch after work today.

jackmc’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

Issue summary: View changes

added links to comment numbers.

YesCT’s picture

updated issue summary with links to comment numbers. (It's ok for folks to do that when they comment. :) )
[edit: btw, doing that is a lot easier with the dreditor Firefox or Chrome extension. just type # and then the comment number and hit tab, and it autocompletes the html for the link for you.]

jackmc’s picture

I tried again from the start, and got the same result (Ubuntu). Could be related to #1908310: Drupal without DB but with site config throws uninformative error.

Otherwise, there may be an issue in UPGRADE.TXT, or with me :)

I'm going to hold off for a bit, would be great if someone else can try it (Ubuntu 10.04, running PHP 5.3.10-1ubuntu2ppa6~lucid) to see if I'm making a mistake.

jackmc’s picture

Issue summary: View changes

oh, those were two different test environments. fixing links to comment numbers.

jackmc’s picture

Issue summary: View changes

Added references to my comment

disasm’s picture

jackmc: just want to confirm, when you say start to finish, you mean:

  1. wiped the db
  2. checkout 7.x
  3. install 7.x
  4. verified d7 was working
  5. switched to 8.x branch
  6. ran update.php script
webchick’s picture

And don't forget 1b) rm -rf sites/default/files/php

jackmc’s picture

@disasm - yes, that is the process I followed.

After installing 7, I added a few posts, clicked around to make sure it was a successful install.

I then

  • deleted everything outside the sites directory
  • copied files across from d8, except the sites dir
  • updated settings file to d8 version, with old DB connection

If I go to /install.php, it starts working, and eventually sees that the DB isn't empty. If I click the link to /update.php, I get blank white screen, and errors logged.

@webchick, I wasn't aware of that step, is it documented? It could be that the doc I am following is out of date, and the process will always fail..

I'm testing within a Vagrant virtual machine, but can't see that causing an issue. I didn't get a chance to do a clean test last night, will try to do it tonight.

x7ian’s picture

Hello guys,
On this issue we are talking about testing the upgrading of D7 to D8, just with a simple instalation of Drupal 7 without any contrib modules?
I guess that for contrib modules each contrib module team has the responsability for upgrading issues.
However, since some modules are going into core for D8, like views, im asking if this any of this should be conssidered on this issue?
:-)

xjm’s picture

The Views upgrade path will be created later in contrib (this summer if all goes as planned), so for now, just core. :)

wusel’s picture

Win7-64bit german - XAMPP 1.7.7 (with PHP = 5.3.8)

This is my normal dev-environment, because Drupal 7 and it's module have problems with XAMPP 1.8.1 (with PHP 5.4.7), please look at http://www.apachefriends.org/en/xampp-windows.html ! XAMPP 1.7.7 is the last XAMPP with a PHP = 5.3.x.

I have installed "Spark (spark-8.x-1.0-alpha7+32-dev)" some time ago (on Wed, 03/06/2013) at XAMPP 1.7.7 with NO problems.

But now after upgrading from D7.21 to "D8.x-dev - March 26, 2013 - 14:48" when I start "update.php", I get an error message on a white screen:

Your PHP installation is too old. Drupal requires at least PHP 5.3.10. See the system requirements page for more information.

That is very bad! The old Drupal 7 cannot run on XAMPP 1.8.1, Drupal 8 cannot run on XAMPP 1.7.7.

Something is wrong.

Wusel

amateescu’s picture

@wusel, I have XAMPP 1.8.0 with PHP 5.4.4, and I have no problems running Drupal 7 core and a lot of contrib modules. What exactly doesn't work for you?

Maybe you tried sometime in the past and got a lot of notices/warnings? If so, a lot of those problems were fixed already, and if you still find some, please open issues for them so they can be fixed for everyone :)

wusel’s picture

[ Created on March 26, 2013 at 8:16pm ]

@amateescu:
that may be right, my last test was in 08/2012.

I will test with XAMPP 1.8.1 within the next days, but are ALL on d.o contributed modules and themes from D7 PHP-save? I have read some issues that this isn't.

@all:
The question to the drupal-coders is:
Is it realy necessary to use PHP 5.3.10 for D8?

I don't know, but I know that this will make much trouble on many (cheap) hosting platforms. And I don't know, whether this is good for Drupal.

Please keep this in mind. Thank you all very much!

Drupal is very good! I like it.

Wusel

[ Edit on April 3, 2013 ]
In the last days I have taken a little vacation, having no internet access.
I hope to report results this week or during the next weekend.

Wusel
[ /Edit on April 3, 2013 ]

Ignigena’s picture

I tested on Mac OS (MAMP), with PHP version 5.4.10 and received the following PHP error when trying to load update.php

PHP Fatal error: Call to a member function get() on a non-object in /drupal/core/includes/bootstrap.inc on line 2471

This is from a fresh D7 install with a couple nodes added. Using the most recent version checked out via GIT.

xjm’s picture

I will test with XAMPP 1.8.1 within the next days, but are ALL on d.o contributed modules and themes from D7 PHP-save? I have read some issues that this isn't.

I'm not quite sure what you're asking here, but D7 modules are not relevant to this discussion. :) This is about D8 only.

xjm’s picture

I'm going to add a point to the summary that PHP 5.3.10 is a requirement, since lots of people seem to miss this.

xjm’s picture

Issue summary: View changes

Update is no longer broken

xjm’s picture

Also, see #1800122: Bump minimum version of php required to 5.3.10 for more information on why the version requirement was bumped to 5.3.10.

amateescu’s picture

I'm not quite sure what you're asking here, but D7 modules are not relevant to this discussion. :) This is about D8 only.

I think the problem is that he has to change/update his entire dev environment to test this upgrade, and I guess just wanting to know if it's really worth the trouble (these kind of updates can be quite a hassle).

And to answer his question: no one can really know if *all* modules are safe to use on PHP 5.4, all I can attest is that the situation has improved considerably in the last few months, at least I know that I provided some patches for that.

So if you decide to go ahead with this, please open issues for contrib modules where you encounter problems and it will be much appreciated :)

x7ian’s picture

Tested in my hostgator shared hosting account.
Uses Linux CentOS
PHP Version 5.3.23

Follow steps on UPGRADE.txt
!! It Worked like a charm !! :-)

Only had to add on .htaccess:

magic_quotes_gpc = Off
magic_quotes_runtime = Off
magic_quotes_sybase = Off

to disable magic quotes not supported.

x7ian’s picture

Issue summary: View changes

Updated issue summary.

ergophobe’s picture

Issue summary: View changes

Added info about test on CentOS comment #29

ergophobe’s picture

Since Windows hasn't been tested, I started there. Will eventually do Ubuntu and CentOS too.

OS: Win 8
PHP: 5.4.3.
Apache: 2.4.2
MySQL: 5.5.24

I did an initial upgrade that appeared to work. Turned on a bunch of modules and it died. So I did a git reset --hard, copied over the D7 settings.php and uploaded the D7 clean DB that I had used for the first upgrade and I consistently get

Uncaught PHP Exception Drupal\Core\Database\DatabaseExceptionWrapper: "SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbname.users_data' doesn't exist: SELECT ud.*
FROM
{users_data} ud
WHERE (module = :db_condition_placeholder_0) AND (uid = :db_condition_placeholder_1) AND (name = :db_condition_placeholder_2) ; Array
(
[:db_condition_placeholder_0] => overlay
[:db_condition_placeholder_1] => 0
[:db_condition_placeholder_2] => enabled
)
" at D:\path\to\public_html\core\lib\Drupal\Core\Database\Connection.php line 554

That error may have been the result of not being logged in as User 1 (not sure), but I tried again, making sure I was logged in and I ended up with the error

Fatal error: Call to undefined function _system_default_theme_features() in .... public_html\includes\theme.inc on line 1405

So after beginner's luck with the first try, no luck with the other. I do know that D8 from a fresh install runs fine on this system.

YesCT’s picture

re: #24 @Ignigena hmm. lets get someone to confirm that. Go ahead and edit the issue summary to enter items for your OS. something like, noting the version of the OS, date [error] #commentnumber:
Mac OS 10.?: 2013-03-26 [PHP Fatal error: Call to a member function get() on a non-object in /drupal/core/includes/bootstrap.inc on line 2471] (#24)

@x7ian thanks for the testing on CentOS and for updating the issue summary.
We are using a pattern with noting the date of the testing, so we can tell when repeating an OS test might be a good idea.
So instead of "CentOS with PHP 5.3.23" use "CentOS: 2013-03-28 [ok]"
And then you could add an item in the php version section of the issue summary like: "5.3.23 -- 2013-03-28 [ok] (#29)

@ergophobe ok. thanks for the testing and good job on updating the issue summary. Please open an issue for for the failure on windows with the modules enabled. Please be sure to include precise steps to reproduce (see contributor task doc: http://drupal.org/node/1468198) and use the issue summary template (see contributor task http://drupal.org/node/1427826) Be sure to link that issue to this, and this issue to that one you make. :)

ergophobe’s picture

EDIT: In order to keep this thread on target, the description to which YesCT refers in the next message now lives in its own issue at #1958006: WSOD with Drupal 7 to Drupal 8 upgrade on Win 8/PHP 5.4 and Ubuntu 12/PHP 5.3

YesCT’s picture

@ergophobe that's a great description, very detailed. Open an issue with the same settings as this one. Don't worry about getting it just right; we can edit the new issue you open. It's good to just open one, and then together we can add information and such.

YesCT’s picture

Issue summary: View changes

Added Win 8 and PHP 5.4.3

ergophobe’s picture

Done: #1958006: WSOD with Drupal 7 to Drupal 8 upgrade on Win 8/PHP 5.4 and Ubuntu 12/PHP 5.3

Actually having the same problem with Ubuntu. Frustrating that it worked once and has failed with several different messages, but now with this totally minimal test case, the errors are the same over repeated attempts.

I should have kept better records, but I believe that when I got the "Call to a member function get() on a non-object" it was when I was repeating tests and neglected to change settings.php back to writeable. Could be wrong about that, but I'll throw that out there for other reporters to test if they see that error.

ergophobe’s picture

Issue summary: View changes

Added Mac OS testing results.

wusel’s picture

Issue tags: -d8 dev environment

[Start] Comment created on April 5, 2013 at 7:22pm [/Start]

Win7-64bit german client - XAMPP 1.8.1

My steps:

  1. I have made a fresh install of D7.22, profile standard.
  2. Then I put the site into maintenance mode.
  3. Then I delete all files outside the 'sites' directory.
  4. Then I copied all files from Drupal 8.x-dev - Last updated: April 5, 2013 - 14:52 in the root directory.
  5. [Added on April 17, 2013] Then I make the settings.php file writeable. [/Added on on April 17, 2013]
  6. Then I started http://www.example.com/update.php, which calls http://www.example.com/core/update.php.
  7. Then I get a white screen.
  8. When I go to http://www.example.com, I get the error message:
    Fatal error: Call to a member function get() on a non-object in ...\core\includes\config.inc on line 106

  9. [Added on April 17, 2013] The upgrade is successful![/Added on April 17, 2013]

I have found in C:\xampp\apache\logs\access.log:
127.0.0.1 - - [05/Apr/2013:xx:xx:xx +0200] "GET /d7tod8/core/update.php HTTP/1.1" 500 - "-" "xxxxxxxxxxxx"
I don't know, why this error appears.

Something is wrong or I have done something in a wrong way.

Can someone write e.g. a page like http://drupal.org/node/570162 ('Upgrade process from Drupal 6 to 7') with the correct steps (first: only main steps) to Upgrade from D7 to D8?
In the file 'UPGRADE.txt' from D8 there are many links to D7-articles on d.o. but not to D8-articles.

I dont't know, what are the correct steps.

Hint:
A fresh install of Drupal 8.x-dev - Last updated: April 5, 2013 - 14:52 was successful.

[Added on April 17, 2013] Please look at http://drupal.org/node/1965402#comment-7312822 and http://drupal.org/node/1965402#comment-7313378 [/Added on April 17, 2013]

Wusel

wusel’s picture

Issue summary: View changes

I have found my error

xmacinfo’s picture

Here is my test on
OS: Mac OS 10.8.3
PHP: 5.4.10
MySQL: 5.5.29

Drupal 7.x branch to 8.x branch

In D7, created 2 nodes: one node basic page, one article. One node using a image, the other node a menu entry.

Ran the upgrade successfully and no error reported to the screen.

Result
Checked the two pages. They appear correctly, including the image and the menu. Awesome!

xmacinfo’s picture

Issue summary: View changes

Fixed oganization of information for PHP version and Cento OS test resolts on commet #29 in this issue

xmacinfo’s picture

Issue summary: View changes

Mac test 2013-04-07

realityloop’s picture

realityloop’s picture

YesCT’s picture

Issue tags: +d8 dev environment

@xmacinfo thanks! I added a link to your comment in the mac section too. http://drupal.org/node/1948390/revisions/view/2637816/2638232

@realityloop super. I hope someone posts a ubuntu d8 dev environment post too also.

YesCT’s picture

Issue summary: View changes

added link to mac #36 [ok]

YesCT’s picture

Issue summary: View changes

updated instructions to match the pattern that has been working and that people are using for updating the issue summary

brycefisherfleig’s picture

Issue summary: View changes

added info about d8 dev env

brycefisherfleig’s picture

Issue summary: View changes

Added recent test reults to issue summary

brycefisherfleig’s picture

My system:

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

Steps:

  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. EDIT: 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`

I'm having trouble tracking down my error log for some reason, but I'm definitely seeing a 500 status code in my access log.

Note: Running `drush dl drupal-8.x` gave error:

md5_file(C:/Users/Owner/AppData/Local/Temp/drush_tmp_1365432768_5162d9c0a21a6\dr
upal-8.x-dev.tar.gz?date=1365425419): [warning]
failed to open stream: No error drush.inc:792
File drupal-8.x-dev.tar.gz?date=1365425419 is corrupt (wrong md5 [error]
checksum).

EDIT: Tried this at step 5 above. Not sure if I should open this as a separate issue...

EDIT: Opened a new issue for my failed upgrade.

brycefisherfleig’s picture

Issue summary: View changes

Windows 7: I add: 2013-04-05 [broken] #comment-7262404 = #35

wusel’s picture

Issue summary: View changes

I add "2013-04-05 [broken] (#35)" at PHP version

YesCT’s picture

@brycefisherfleig Thanks for opening that issue.

I added that one and one from an earlier comment .. #32 to the issue summary.

We can use in any comment in a d.o issue the pattern [#NNNN] where NNN is the node/issue number and it makes those nicely formatted links to issues.

YesCT’s picture

Issue summary: View changes

added the follow-up issues that people have identified.

MathieuSpil’s picture

I tested on OS X version 10.8.2, with php version 5.4.4 and the result is: [it worked].

wusel’s picture

Issue summary: View changes
johnv’s picture

Issue tags: +d8 dev environment

I did an upgrade from D7.16 to D8.x-dev (April 17, 2013 - 13:01)
- Windows Vista,
- Acquia Dev Desktop with PHP 5.3.18
And got a WSOD : #1973144: WSOD when updating from D7.16 to D8.x-dev ( April 17, 2013 - 13:01) on MS Vista with PHP 5.3.18

Additional uncaught exception thrown while handling exception.

Original

Drupal\Core\Config\StorageException: Missing configuration file: system.filter in Drupal\Core\Config\InstallStorage->getFilePath() (line 54 of C:\damp\Sites\hunkemoller.nl_v15upgradev8\core\lib\Drupal\Core\Config\InstallStorage.php).

Additional

Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: The service definition "request" does not exist. in Symfony\Component\DependencyInjection\ContainerBuilder->getDefinition() (line 799 of C:\damp\Sites\hunkemoller.nl_v15upgradev8\core\vendor\symfony\dependency-injection\Symfony\Component\DependencyInjection\ContainerBuilder.php).

KarstenS’s picture

I've did a test turn.

OS: Android 4.2
Webserver: lighttpd/1.4.31 for KSWEB
PHP: 5.4.13
MySQL: 5.1.62
Drupal 7.22

Did everything exactly as described in the UPGRADE.TXT and used the most actual D8 I've downloaded right before with TortoiseGit.

Upgrade not successfull.

Here the Serverlog from running the update.php serval times:


2013-04-20 15:50:47: (log.c.166) server started
2013-04-20 15:59:01: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Call to undefined function _update_8000_entity_get_display() in /mnt/sdcard/ksweb/htdocs/datastore/core/modules/user/user.install on line 757

2013-04-20 16:02:02: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Cannot redeclare entity_delete_multiple() (previously declared in /mnt/sdcard/ksweb/htdocs/datastore/core/includes/entity.inc:331) in /mnt/sdcard/ksweb/htdocs/datastore/sites/all/modules/entity/entity.module on line 243

2013-04-20 16:03:52: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Call to undefined function _update_8000_entity_get_display() in /mnt/sdcard/ksweb/htdocs/datastore/core/modules/field/field.install on line 288

2013-04-20 16:05:08: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Call to undefined function _update_8000_entity_get_display() in /mnt/sdcard/ksweb/htdocs/datastore/core/modules/field/field.install on line 288

2013-04-20 16:06:44: (mod_fastcgi.c.2676) FastCGI-stderr: Uncaught PHP Exception Drupal\Core\Database\DatabaseExceptionWrapper: "SQLSTATE[42S02]: Base table or view not found: 1146 Table 'lapurd.users_data' doesn't exist: SELECT ud.*
FROM
{users_data} ud
WHERE (module = :db_condition_placeholder_0) AND (uid = :db_condition_placeholder_1) AND (name = :db_condition_placeholder_2) ; Array
(
[:db_condition_placeholder_0] => overlay
[:db_condition_placeholder_1] => 1
[:db_condition_placeholder_2] => enabled
)
" at /mnt/sdcard/ksweb/htdocs/datastore/core/lib/Drupal/Core/Database/Connection.php line 554

2013-04-20 16:07:29: (log.c.166) server started
2013-04-20 16:08:06: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Call to undefined function _update_8000_entity_get_display() in /mnt/sdcard/ksweb/htdocs/datastore/core/modules/field/field.install on line 288

2013-04-20 16:10:23: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: Call to undefined function _update_8000_entity_get_display() in /mnt/sdcard/ksweb/htdocs/datastore/core/modules/field/field.install on line 288

webchick’s picture

Updating on Android. Damn! Nice work. :)

KarstenS’s picture

Arg. I've missed to read the "Steps to test". I've used a mirror of my actual running server instead of the fresh install with one or two nodes.

I'll test this later.

Or is it ok to use a copy of my productive system for testing?

rupl’s picture

Fresh D8 install (no upgrade) on Linux 3.2.0-40-virtual #64-Ubuntu SMP x86_64 running PHP 5.3.10 produces very similar errors to some of these reports. May not be related to upgrade.

Error:

Fatal error: Call to a member function get() on a non-object in .../core/lib/Drupal.php on line 212
KarstenS’s picture

New try. This time with fresh installed D7.22 and after that created an article and one basic ... thing.

OS: Android 4.2
Webserver: lighttpd/1.4.31 for KSWEB
PHP: 5.4.13
MySQL: 5.1.62
Drupal 7.22

Did all steps like in UPGRADE.TXT described.

One thing, that happened with my mirrored server too when loading update.php firts times: I get Internal Server Error. Even if I restart the server or not, I have to wait some time (one minute or so) and then update.php loads.

Result: Update went till the end but with one Error left:

The following updates returned messages

file module

Update #8001
Failed: Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes: ALTER TABLE {file_usage} CHANGE `id` `id` VARCHAR(64) NOT NULL DEFAULT '' COMMENT 'The primary key of the object using the file.'; Array ( ) in Drupal\Core\Database\Connection->query() (line 554 of /mnt/sdcard/ksweb/htdocs/drupal/core/lib/Drupal/Core/Database/Connection.php).

After that I can only load the frontpage. With everything else I get 404.

#1976110: D8 upgrade path: file module; Update #8001

KarstenS’s picture

Issue summary: View changes

updated summary according to #42

YesCT’s picture

@KarstenS Thanks for using your actual site. That is great to do in addition to the "just a few nodes" testing, because it is more real life. So doing both is superb!

about the 404 on every page:
I was helping someone new to d8 contrib the other day, they had a .. linux virtual machine iirc and they saw that same thing with just installing d8 (not upgrading). Do you get that with just installing d8 from scratch?

Related, is the community doc page: http://drupal.org/node/228462 "Page Not Found" Errors on every page except homepage.

the person I was helping checked the things on that doc page, and made sure the apache mods were correct... they were. After restarting the webserver, then the 404s went away and things were better. Does restarting help you?

Please add a new item in the issue summary (anyone can edit issue summaries) for OS Android and add your details in there too. :) This is so cool.

[edit:] Oh, and please add the issue you made to the issue summary, in the "Related" section. Use a pattern similar to the other ones like: (from #47) [#NNNNNN]

If you have questions about editing the issue summary or anything, post back here or ask in #drupal-contribute in IRC http://drupal.org/irc

mrP’s picture

OS: Debian Squeeze
PHP: 5.3.24
MySQL: 5.5.30
Drupal: 7.22

Result: Success

I ran this as a multi-site style upgrade (as of http://drupalcode.org/project/drupal.git/commit/cb4782ea137a86c5744f4bd8...).

wusel’s picture

I have tested an D7-distribution #1992832: Upgrade from an D7-distribution to D8 - Win7, XAMPP 1.8.1.

I get an ugly error message:

Notice: Undefined index: name in system_requirements() (line 42 of core\modules\system\system.install).
Notice: Undefined index: version in system_requirements() (line 44 of core\modules\system\system.install).

Note:
Many D7-sites use a distribution. I think, this errors should be solved, before D8 comes to be an official release.

Something is wrong or I have done something in a wrong way.

Wusel

mrP’s picture

OS: Debian Wheezy
PHP: 5.3.25
MySQL: 5.5.30
Drupal: 7.22

Result: Success

I ran this as a multi-site style upgrade (as of http://drupalcode.org/project/drupal.git/commit/a858b3473cdedc8ef2d87f03...).

John Bickar’s picture

MAMP 2.1.3
PHP: 5.3.20
MySQL: 5.5.29
Drupal: 7.22

Test site had two nodes: one page node, and one article node with an attached image.

Result: success. Important to follow the instructions in core/UPGRADE.txt :)

John Bickar’s picture

Issue summary: View changes

Updated issue summary.

YesCT’s picture

I had some trouble earlier today trying to do just an simple d7 to d8 upgrade. It might have just been me, but it seems like it only worked when, in the end I went to /core/update.php (and not upgrade.php).

http://screencast.com/t/7zQEUqZ4gNs

Here are the steps.

(from 8.x branch in git)
  514  git pull --rebase
  515  git status
  516  git pull --rebase
  517  git checkout 7.x
  518  drush -y si --account-pass=admin --db-url="mysql://root:root@localhost/d8-patch" --site-name=7.x
(login in browser)
  519  ls
  520  ls ~/foo
  521  sudo rm -r ~/foo/sites
  522  ls
  523  mv sites ~/foo
  524  git checkout 8.x
  525  ls
  526  sudo rm -r sites
  527  ls
  528  mv ~/foo/sites .
  529  chmod a+w sites/default/settings.php 
(url in browser: /core/update.php)
  530  history
ergophobe’s picture

Issue summary: View changes

Updated issue summary. Tested on MAMP.

ergophobe’s picture

Update to #30 - successful upgrade D6 -> D7 -> D8. The D6-> D7 part was a hassle, but D7 -> D8 was a breeze

- Windows 8
- PHP 5.4.3
- Apache 2.4.2
- MySQL 5.5.24

I did quickly run into #1991298: Fatal error when installing Drupal on servers that don't have the cURL extension, but this was solved by enabling php_curl in php.ini.

Of course, that just concerns getting update.php to run. I've never successfully upgraded a site, even the simplest, from one major version to another using the in-built upgrade routines and this is no exception - there are so many notices, errors, left over cruft from previous versions and so forth that it's really unusable. So though it ran without crashing on Windows, that should in now way be interpreted to mean that the result was a functional website.

ergophobe’s picture

Issue summary: View changes

Adding Win 8 test in #54

naveenvalecha’s picture

subscribe

naveenvalecha’s picture

Issue summary: View changes

added a bug report for a d7 with other languages

wusel’s picture

Issue summary: View changes

Put the d7-site into maintenance mode

Sree’s picture

subscribe ...

surendramohan’s picture

Subscribing. Will be testing on Windows XP, Windows 7 and Windows 8, MAC with different combinations of Apache, PHP and MySQL and would update my results here.

surendramohan’s picture

Test details:

OS:

Windows XP (Professional) Version 2002 SP2

Apache:

2.4.3 (Win32)

PHP:

5.4.7

MySQL:

5.0.10

D7 version:

7.23

D8 version:

8.0-alpha3

Browser:

Google Chrome:

29.0.1547.76 m

Steps followed:

https://drupal.org/node/570162

Result:

Upgrade failed.

Please find the screenshot of the error message in the attached PNG file (1948390_UpgradeFailedErrorMessage.PNG).

xmacinfo’s picture

By the way, I would not like having to use Migrate (there is talk to make Migrate the official way to upgrade from Drupal 7 to Drupal 8) every time time I need to upgrade a D7 installation to D8.

Let's make sure we can upgrade to Drupal 8 using the regular update.php (as well as the regular upgrade steps).

xmacinfo’s picture

Issue summary: View changes

added Debian successes

wusel’s picture

Issue summary: View changes

@https://drupal.org/requirements/php:
Drupal 8 requires version PHP 5.4 or later, with the CURL extension.

wusel’s picture

Issue summary: View changes

I fix some html-errors in this page (may be from the d.o.-update to D7 ?)

wusel’s picture

Issue summary: View changes

I add a link to the PHP 5.4 policy ("[policy, no patch] Require PHP 5.4")

webchick’s picture

Status: Active » Postponed
Issue tags: +revisit before beta

Actually, AFAIK we can close this one, since we no longer have a D8 upgrade path.

Or maybe "postponed" is a better value, because when we eventually have D8 => D8 upgrades (~beta/rc) we *will* need testing for those. Trying that out.

KarstenS’s picture

That means, it will be not possible to upgrade from D7 to D8, when it will go prod?

webchick’s picture

No, it will, just it will not use an upgrade path but rather a migration path. See https://www.acquia.com/d8migrate for more details.

catch’s picture

Status: Postponed » Closed (duplicate)
Issue tags: -revisit before beta

We're going to need migrate testing, but I don't think there's anything in this issue that can be carried over to that one. Going to go ahead and close it.