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
- Linux
- Mac
- (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
- Install d7.
- Create a node or two.
- Put the d7-site into maintenance mode (to avoid running of cron, which makes the
settings.php
file readonly). - Make the
settings.php
file writeable. - Upgrade to d8.
Related
- (from #32) #1958006: WSOD with Drupal 7 to Drupal 8 upgrade on Win 8/PHP 5.4 and Ubuntu 12/PHP 5.3
- (from #35) #1965402: Upgrade from D7.22 to D8 - Win7, XAMPP 1.8.1 - bad error-message
- (from #39) #1964584: Upgrade to D8 Fails on Windows / PHP 5.4.7
- (from #42) #1948390: [Meta] Upgrade to D8 from D7: regular testing needed on various OSs with different versions of php and other unique situations
- #1949724: Allow simpletest child sites to additionally load a test-specific settings.php to allow testing anonymous and configless updates
- #1919002: Upgrade to D8 broken when D7 has more then one language enabled
- #1943726: BootstrapConfigStorageFactory and update
- #252100: Check if basic requirements are met before installing/upgrading without requiring to upload the full package
- #1468340: index.php has syntax error instead of graceful fail for < 5.3
- #1940274: Modules not loaded when they ought to be loaded in \Drupal\Core\Extension\ModuleHandler::buildHookInfo
- #2048379: multilingual first time admin/config exception Field 'uri' doesn't have a default value into {locale_file}
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.
Comment | File | Size | Author |
---|---|---|---|
#58 | 1948390_UpgradeFailedErrorMessage.PNG | 9.16 KB | surendramohan |
Comments
Comment #1
YesCT CreditAttribution: YesCT commentedfixing tags.
Comment #2
xjmThere 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:
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.
Comment #2.0
xjmupdated with placehold for last tested
Comment #3
YesCT CreditAttribution: YesCT commented#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
Comment #3.0
YesCT CreditAttribution: YesCT commentedUpdated issue summary.
Comment #4
YesCT CreditAttribution: YesCT commentedActive. Since #1948650: Update is broken is fixed.
Go manual testers.
Comment #5
jackmc CreditAttribution: jackmc commentedI'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 :)
Comment #6
tim.plunkettAs of this past week or so, you will need PHP 5.3.10. Thanks for helping!
Comment #7
farhadhf CreditAttribution: farhadhf commentedI 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 outputs when the upgrade is finished (in update.php?op=results).
Comment #8
xjmAdding #252100: Check if basic requirements are met before installing/upgrading without requiring to upload the full package and #1468340: index.php has syntax error instead of graceful fail for < 5.3 to the summary for #5. I think #7 is #1940274: Modules not loaded when they ought to be loaded in \Drupal\Core\Extension\ModuleHandler::buildHookInfo so adding that too.
Thanks @jackmc and @farhadhf!
Comment #8.0
xjmadded related issues and clarified why it was postponed
Comment #8.1
xjmUpdated issue summary.
Comment #8.2
xjmUpdated issue summary.
Comment #8.3
xjmUpdated issue summary.
Comment #8.4
xjmUpdated issue summary.
Comment #8.5
xjmUpdated issue summary.
Comment #9
jackmc CreditAttribution: jackmc commentedRetested 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.
Comment #10
xjm@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.
Comment #11
jackmc CreditAttribution: jackmc commentedI 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..
Comment #12
xjmThanks @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!)
Comment #13
jackmc CreditAttribution: jackmc commentedNo 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
I hope I'm not doing anything wrong while trying to test it, I'm going to try again from scratch after work today.
Comment #13.0
jackmc CreditAttribution: jackmc commentedUpdated issue summary.
Comment #13.1
YesCT CreditAttribution: YesCT commentedadded links to comment numbers.
Comment #14
YesCT CreditAttribution: YesCT commentedupdated 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.]
Comment #15
jackmc CreditAttribution: jackmc commentedI 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.
Comment #15.0
jackmc CreditAttribution: jackmc commentedoh, those were two different test environments. fixing links to comment numbers.
Comment #15.1
jackmc CreditAttribution: jackmc commentedAdded references to my comment
Comment #16
disasm CreditAttribution: disasm commentedjackmc: just want to confirm, when you say start to finish, you mean:
Comment #17
webchickAnd don't forget 1b) rm -rf sites/default/files/php
Comment #18
jackmc CreditAttribution: jackmc commented@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
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.
Comment #19
x7ian CreditAttribution: x7ian commentedHello 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?
:-)
Comment #20
xjmThe Views upgrade path will be created later in contrib (this summer if all goes as planned), so for now, just core. :)
Comment #21
wusel CreditAttribution: wusel commentedWin7-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:
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
Comment #22
amateescu CreditAttribution: amateescu commented@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 :)
Comment #23
wusel CreditAttribution: wusel commented[ 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 ]
Comment #24
Ignigena CreditAttribution: Ignigena commentedI 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.
Comment #25
xjmI'm not quite sure what you're asking here, but D7 modules are not relevant to this discussion. :) This is about D8 only.
Comment #26
xjmI'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.
Comment #26.0
xjmUpdate is no longer broken
Comment #27
xjmAlso, 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.
Comment #28
amateescu CreditAttribution: amateescu commentedI 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 :)
Comment #29
x7ian CreditAttribution: x7ian commentedTested 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:
to disable magic quotes not supported.
Comment #29.0
x7ian CreditAttribution: x7ian commentedUpdated issue summary.
Comment #29.1
ergophobe CreditAttribution: ergophobe commentedAdded info about test on CentOS comment #29
Comment #30
ergophobe CreditAttribution: ergophobe commentedSince 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
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
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.
Comment #31
YesCT CreditAttribution: YesCT commentedre: #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. :)
Comment #32
ergophobe CreditAttribution: ergophobe commentedEDIT: 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
Comment #33
YesCT CreditAttribution: YesCT commented@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.
Comment #33.0
YesCT CreditAttribution: YesCT commentedAdded Win 8 and PHP 5.4.3
Comment #34
ergophobe CreditAttribution: ergophobe commentedDone: #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.
Comment #34.0
ergophobe CreditAttribution: ergophobe commentedAdded Mac OS testing results.
Comment #35
wusel CreditAttribution: wusel commented[Start] Comment created on April 5, 2013 at 7:22pm [/Start]
Win7-64bit german client - XAMPP 1.8.1
My steps:
settings.php
file writeable. [/Added on on April 17, 2013]http://www.example.com/update.php
, which callshttp://www.example.com/core/update.php
.Then I get a white screen.When I go to
http://www.example.com
, I get the error message: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
Comment #35.0
wusel CreditAttribution: wusel commentedI have found my error
Comment #36
xmacinfoHere 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!
Comment #36.0
xmacinfoFixed oganization of information for PHP version and Cento OS test resolts on commet #29 in this issue
Comment #36.1
xmacinfoMac test 2013-04-07
Comment #37
realityloopFor windows users:
http://realityloop.com/blog/2013/04/08/making-acquia-dev-desktop-more-su...
Comment #37.0
realityloopMac test https://drupal.org/node/1948390#comment-7269106
Comment #38
YesCT CreditAttribution: YesCT commented@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.
Comment #38.0
YesCT CreditAttribution: YesCT commentedadded link to mac #36 [ok]
Comment #38.1
YesCT CreditAttribution: YesCT commentedupdated instructions to match the pattern that has been working and that people are using for updating the issue summary
Comment #38.2
brycefisherfleig CreditAttribution: brycefisherfleig commentedadded info about d8 dev env
Comment #38.3
brycefisherfleig CreditAttribution: brycefisherfleig commentedAdded recent test reults to issue summary
Comment #39
brycefisherfleig CreditAttribution: brycefisherfleig commentedMy system:
Steps:
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:
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.
Comment #39.0
brycefisherfleig CreditAttribution: brycefisherfleig commentedWindows 7: I add: 2013-04-05 [broken] #comment-7262404 = #35
Comment #39.1
wusel CreditAttribution: wusel commentedI add "2013-04-05 [broken] (#35)" at PHP version
Comment #40
YesCT CreditAttribution: YesCT commented@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.
Comment #40.0
YesCT CreditAttribution: YesCT commentedadded the follow-up issues that people have identified.
Comment #41
MathieuSpil CreditAttribution: MathieuSpil commentedI tested on OS X version 10.8.2, with php version 5.4.4 and the result is: [it worked].
Comment #41.0
wusel CreditAttribution: wusel commentedI ad at Related: http://drupal.org/node/1965402
Comment #42
johnvI 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).
Comment #43
KarstenS CreditAttribution: KarstenS commentedI'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
Comment #44
webchickUpdating on Android. Damn! Nice work. :)
Comment #45
KarstenS CreditAttribution: KarstenS commentedArg. 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?
Comment #46
ruplFresh 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:
Comment #47
KarstenS CreditAttribution: KarstenS commentedNew 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:
After that I can only load the frontpage. With everything else I get 404.
#1976110: D8 upgrade path: file module; Update #8001
Comment #47.0
KarstenS CreditAttribution: KarstenS commentedupdated summary according to #42
Comment #48
YesCT CreditAttribution: YesCT commented@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
Comment #49
mrP CreditAttribution: mrP commentedOS: 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...).
Comment #50
wusel CreditAttribution: wusel commentedI have tested an D7-distribution #1992832: Upgrade from an D7-distribution to D8 - Win7, XAMPP 1.8.1.
I get an ugly error message:
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
Comment #51
mrP CreditAttribution: mrP commentedOS: 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...).
Comment #52
John Bickar CreditAttribution: John Bickar commentedMAMP 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 :)
Comment #52.0
John Bickar CreditAttribution: John Bickar commentedUpdated issue summary.
Comment #53
YesCT CreditAttribution: YesCT commentedI 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.
Comment #53.0
ergophobe CreditAttribution: ergophobe commentedUpdated issue summary. Tested on MAMP.
Comment #54
ergophobe CreditAttribution: ergophobe commentedUpdate 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.
Comment #54.0
ergophobe CreditAttribution: ergophobe commentedAdding Win 8 test in #54
Comment #55
naveenvalechasubscribe
Comment #55.0
naveenvalechaadded a bug report for a d7 with other languages
Comment #55.1
wusel CreditAttribution: wusel commentedPut the d7-site into maintenance mode
Comment #56
Sree CreditAttribution: Sree commentedsubscribe ...
Comment #57
surendramohan CreditAttribution: surendramohan commentedSubscribing. 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.
Comment #58
surendramohan CreditAttribution: surendramohan commentedTest 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).
Comment #59
xmacinfoBy 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).
Comment #59.0
xmacinfoadded Debian successes
Comment #60
wusel CreditAttribution: wusel commented@https://drupal.org/requirements/php:
Drupal 8 requires version PHP 5.4 or later, with the CURL extension.
Comment #61
wusel CreditAttribution: wusel commentedI fix some html-errors in this page (may be from the d.o.-update to D7 ?)
Comment #62
wusel CreditAttribution: wusel commentedI add a link to the PHP 5.4 policy ("[policy, no patch] Require PHP 5.4")
Comment #63
webchickActually, 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.
Comment #64
KarstenS CreditAttribution: KarstenS commentedThat means, it will be not possible to upgrade from D7 to D8, when it will go prod?
Comment #65
webchickNo, it will, just it will not use an upgrade path but rather a migration path. See https://www.acquia.com/d8migrate for more details.
Comment #66
catchWe'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.