Hello all,
I’m a non techie getting to grips with the basics of drupal and am fairly confident using/enabling/configuring modules etc on Drupal 7 (Thanks to it being SO user-friendly) . I’m also familiar with accessing the folders in the web hosts file manager, extracting them/moving them etc…but not with linux commands!
I need to update from 7.10 to 7.14 but am stumped by the instructions here: http://drupal.org/node/1223018 (half way down section on minor upgrades)
- On step 3 it says to keep the install.php file but I seem to have two! How do I know which to keep?
- Then on step 4 it says to put the folders somewhere (I guess other than public.html). Supposing I make a folder called upgrade – will the linux command that follows that step work or do I need to change it to take account of my chosen folder name?
- Plus I’ve no idea how to go about step 5: “Re-apply any modifications to files such as .htaccess or robots.txt”
I’d like to learn how to do all these things in due course but if there is an easier way to do a minor upgrade then I’d be very grateful to know how!
Hope you can help,
Elly
Comments
No it doesn't. Read it again.
No it doesn't. Read it again. settings.php
Put it where you like. Sure you need to change the command /path/to/your/installation to the real path, e.g. /home/yoursite/public_html
or /var/www/domain/htdocs or wherever it is. To find the path go into the folder where your Drupal site lives and issue command
pwd
.If you edited your .htaccess to redirect from www to a non-www form of your URL for example, by updating core and hence overwritting your .htaccess with a new copy of .htaccess, that modification you made will be reverted to the default, so you have to do it again.
The easy way is to install and learn to use drush. http://drupal.org/project/drush You can update in a few seconds that way. Sometimes it is possible on shared hosting, and should be easy to install if you have root access. You still have to re-apply changes,. e.g. to .htaccess.
To be safe, all updates should be run on a test site. But if you can tolerate a bit of down time and have a backup, you can always risk running them live on a site which is not mission critical.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
Still confused about which to keep
Thank you for your reply. I can't see where it says to keep "settings.php" in the instructions.
I was looking at the bit below, which says to remove all core files except for the sites and the original install profile in the profiles directory:
"3.Remove all old core files and directories, except for the 'sites' directory, the original install profile in the 'profiles' directory and any custom files you added elsewhere. "
In my profile directory I only have "minimal", "standard" and "testing". No install profile.
I do, however, have various "install" files in the "includes" directory. These include install.mysql install.pgsql install.php (x2) instal.sqlite and install.txt. Do I need to keep any of these? I'm guessing not as they are clearly not in the profiles directory.
'pwd' sounds very useful. Also, I'll have a look at drush - this is a good time to learn, while there is not much to lose!
I think you are over
I think you are over complicating things.
Here is a simple method to update core without drush. Check there are no modules or themes in modules or themes folder other than core ones (sometimes people put contrib modules and themes there by mistake, but they should be in sites/). Rename sites/ to sites_bak/ and .htaccess to .htaccess_bak. Grab the new Drupal code and drop it into the root folder so as to overwrite the old code. Delete your new sites/ and .htaccess, and rename sites_bak back to sites/ and .htaccess_bak to .htaccess, so you get to keep your old copies of sites/ and .htaccess and everything else is new. Run database updates. That's it.
If you are likely to get traffic, it is safest to put the whole site into maintenance mode for the entire process, and take it out of maintenance mode when you have finished.
But always it is safest to take a backup of the database before you start because occasionally updates fail and break the site. If that happens, you should debug really, but at least you have the option of putting back the old version of Drupal code and the old database, so as to roll back to where you were before you started the update in the rare case where you hit a major problem after update. This is why on a mission critical site you do the whole thing on a test copy of the site first, but if it is a site which can risk a little downtime you might feel that is just too much work.
It is true that if you built your site with an install profile or built it on Drupal Gardens rather than a bog standard copy of Drupal, you need to worry about profiles. But it sounds like you have plain vanilla Drupal, so you need not worry about profiles, and that makes updates easier.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
That sounds much easier!
I'll try updating it this way. Yes, I have ordinary Drupal as I gather it's better to install the proper thing than to have headaches later on. So far so good, this has been the first real hurdle.
Thank you again and I'll let you know how it goes :-)
Thanks John_B
I have been searching all over this evening trying to figure out that same "Profiles" line
"...except for the 'sites' directory, the original install profile in the 'profiles' directory and..."
I didn't know whether everything in the profiles folder was the "original install profile" or some portion of the contents and, if the latter which portion.
Since this is my first ever update I'm very hesitant about doing the wrong thing so I was stopped cold until you rescued this Drupal newbie's butt with your clear instructions.
Thank you
Bill Hanson