Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By guitarscape on
It seems poeple are having problems upgrading to 4.7.
I wonder if these people represents the majority or just unlucky ones...should i wait until 4.7.1 just like i waited until sp1 to install winxp?
Comments
Do a test
I tested the upgrade before I upgrading my site.
I made a copy of my database and configured 4.7 to connect to the copied database and upgraded then I upgraded the modules.
That way you should know more or less what type of problems you might encounter.
could you please kindly post
could you please kindly post a sample mysql commands to make a copy of the database (or dump and restore)? this sounds like a fail-proof approach. thanks so much.
Copying databases
I actually used phpMyAdmin. I didn't have much of a choice really.
Nevertheless I'll list several methods. I assume that you know how to configure drupal as well as adding user privlages to a database.
phpMyAdmin:
1. Create a new database. If needed add a user to the database
2. Select current drupal database from the drop-down list
3. Use export to create .sql file (make sure you select save as file at the bottom of the page)
4. Select the new database you created
5. Import the .sql file
6. Install Drupal as per instructions. Since you will not be logged in as admin edit update.php to allow access.
phpMyAdmin (alternative):
1. Select current Drupal database
2. Click in the Operations tab
3. Under "Copy database to:" enter the name of your new database and press go. (This will create & duplicate the database) again add a user to the database if needed
4. Install Drupal as per instructions. Since you will not be logged in as admin edit update.php to allow access.
Command Line:
Add user to database if required and configure drupal
You should do what is right
You should do what is right for you. Don;t worry about anyone else. I have been using the RC's quite successfully for several sites. Put up a test site and start playing. My guess is that we hear far more from people having issue's then successes. Even so, most issue's seem to be specific to the individuals setup so far and not a global Drupal 4.7 issue.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
New to drupal
I'm new to drupal and a week in am having some learning issues here and there but i've managed to successfully upgrade from 4.6.6 to the RC's and then 4.7 final without a single issue.
Obviously everyones milage will vary as there are lots of variables to take into account.
I would suggest disabling any third party modules you have installed (that are not part of core) and then replace them after the upgrade with there 4.7 counterparts. Apart from that i found the upgrade quite painless.
As long as you're not dependant on external modules...
you should be fine, though my blocks disappeared... and when I fixed that (I forget how), something else cropped up, and then something else...
Oh, and if you have PHP code doing direct calls to MySQL, wait. Trust me.
I may have to roll back to 4.6.6. just to keep things rolling. I'm generally displeased with this release, and it's not because of the Drupal core. It's because of the module dev side. It's looney.
KnowProSE.com
OpenDepth.com