Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
drupal-3174996
Manage
Activity
Members
Labels
Plan
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Issue forks
drupal-3174996
Commits
cb9a2e2a
Commit
cb9a2e2a
authored
18 years ago
by
Dries Buytaert
Browse files
Options
Downloads
Patches
Plain Diff
- Patch
#102011
by mfer et al: UPGRADE.txt improvements. Made some changes of my own.
parent
ce2088e8
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
UPGRADE.txt
+32
-35
32 additions, 35 deletions
UPGRADE.txt
with
32 additions
and
35 deletions
UPGRADE.txt
+
32
−
35
View file @
cb9a2e2a
...
...
@@ -4,65 +4,65 @@ UPGRADING
---------
1. Backup your database and Drupal directory - especially your
sites
-
directory which contains your configuration file and
added modules and themes, any contributed modules
in your
modules
-
directory, and your files
-
directory which
contains
uploaded files.
"
sites
"
directory which contains your configuration file and
added modules and themes, any contributed modules
in your
"
modules
"
directory, and your
"
files
"
directory which
contains
uploaded files.
Note:
F
or a single site setup the configuration file is the
Note:
f
or a single site setup the configuration file is the
"settings.php" file located at sites/default/settings.php.
For multisite configuration the configuration file is
located in a structure like the following:
sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.site3/settings.php
For multisite configuration the configuration file is located
in a structure like the following:
sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.path/settings.php
More information on multisite configuration is located in
the INSTALL.txt file.
2. Disable contributed modules and switch to a core theme
(
b
luemarine or
g
arland).
(
B
luemarine or
G
arland).
3. Log on as the user with user ID 1.
(
User ID 1 is the first
account created and the main administrator account.
)
User
3. Log on as the user with user ID 1. User ID 1 is the first
account created and the main administrator account. User
ID 1 needs to be logged in so that you can access update.php
file
(step 8) which can only be run by user ID 1. Do not
close
your browser until step 9 is complete.
(step 8) which can only be run by user ID 1. Do not
close
your browser until step 9 is complete.
4. Remove all of the old files and directories from the
Drupal
installation directory.
4. Remove all of the old files and directories from the
Drupal
installation directory.
5. Unpack the new Drupal files and directories into the Drupal
installation directory.
6. Copy the backed up files
-directory
and sites
-
directories to the
6. Copy the backed up
"
files
"
and
"
sites
"
directories to the
Drupal installation directory. If the original .htaccess or
robots.txt files have been modified, copy the backed up
versions of these files to the installation directory
directory as
well.
versions of these files to the installation directory
as
well.
7. Verify the new configuration file to make sure it has the
latest and correct information.
8.
(Optional)
Re-install contributed modules.
8. Re-install contributed modules.
Note:
M
ake sure the version of a module matches your
Note:
m
ake sure the version of a module matches your
version of Drupal. Modules from previous versions may
not be compatible with the current version. Check
http://drupal.org/project/Modules for the version of a
module to match your version of Drupal.
9. Run update.php by visiting http://www.example.com/update.php
(replace www.example.com with your drupal installations
domain
name
). This step will update the database to
the new Drupal
installation.
(replace www.example.com with your drupal installation
'
s
domain name and path
). This step will update the database to
the new Drupal
installation.
Note:
I
f you are unable to access update.php
as user ID 1
do the
following:
Note:
i
f you are unable to access update.php
do the
following:
- With a text editor find the update.php file on your system.
It should be in the main Drupal directory that you installed
all the files into.
- Open update.php with a text editor.
- There is a line near top of update.php that says
$access_check = TRUE;. Change it to $access_check = FALSE;.
...
...
@@ -70,8 +70,5 @@ UPGRADING
- As soon as the script is done, you must change the update.php
script back to its original form to $access_check = TRUE;.
Note: Upgrading sequentially is recommended, one release at a time.
It is possible to skip releases, but is not advised.
For more information on upgrading visit the Drupal handbook at
http://drupal.org/upgrade
\ No newline at end of file
http://drupal.org/upgrade
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment