Manual:Upgrading to 1.14

 SVG was to version 1.1 in 2011. There are two SVG Profiles,' SVG Tiny and SVG Basic, meant for with reduced computational and display. Scalable Vector Graphics 2becae a on 15 2016. SVG 2 several new features in addition to those of SVG 1.1 and page regards the process of a wiki to

Overview
First.

As with all upgrades, the basic premise is the same:


 * 1) Check the requirements
 * 2) Read the release notes
 * 3) Back up existing files and the database
 * 4) Unpack the new files
 * 5) Run the update script to check the database
 * 6) Upgrade extensions
 * 7) Test the update

Check requirements
MediaWiki 1.14 requires:

PHP

 * PHP 5.0.x or later
 * We recommend using PHP 5.1.x or 5.2.x.
 * Note that PHP 5.0.x under certain 64-bit platforms contains bugs which cause fundamental problems with MediaWiki. If running on an x86_64 (AMD64, EMT64) or other affected 64-bit platform, PHP 5.1.x or 5.2.x is required..


 * MySQL 4.0.x or later
 * Version 3.x has not been supported since 1.6.0

or


 * 8.1 or later
 * You will also require the and  modules, if running  8.1 or 8.2
 * see also

Read the release notes
Within the distribution, or within the files checked out/exported from SVN, there are a number of files with capitalised filenames, one of which contains the. Now's the time to open it up and find out what's You can also read them at.

. Before proceeding to update the database sch of the wiki, including both the database and the files:


 * the content, from the database. It may be a good idea to create an XML dump in addition to the SQL database dump.
 * MySQL:
 * text dump:
 * dump:
 * output for pg_restore:
 * images and other media files (the contents of the  directory)
 * configuration files, i.e.  and   files, including all skins and extensions, especially if you modified them.
 * configuration files, i.e.  and   files, including all skins and extensions, especially if you modified them.

See for instructions.

Using a package
If using a, decompress the file on the server where the old version of is running. When a package normally a new directory for the new wiki version will be created and you will have to copy the new files and directories to your current wiki directory. To instead replace the existing files while decompressing and do this in one go:

$ tar mediawiki-1.14.0.tar.gz /path/to/your/wiki/ =1

On older Linux distributions (f.e. / 4.x) use:

$ tar mediawiki-1.14.0.tar.gz /path/to/your/wiki/ =1

For those using an old version of tar (eg. GNU tar 1.13.x) which do not have or flags can uncompress the archive without the option and thereafter recursively copy the contents of the latest package into the previous wiki directory structure, as follows:

$ tar mediawiki-1.14.0.tar.gz $ mediawiki-1.14.0/* /path/to/your/wiki/

(Open)Solaris users should use, or:

$ mediawiki-1.14.0.tar.gz | tar xf -

Using Subversion
If using, export the files into a clean location. Replace all existing files with the new versions from 1.14, preserving the directory structure. The core code is now up to date.

Run the update script
Note: Make sure there's an file in the wiki root, and it contains up to date information. The user needs full permissions (shell access) on the database.

The preferred method of performing the update is using the maintenance script, although it is also possible to the web-based installer.

Shell
From the command line, or an SSH shell or similar, change to the  directory and execute the update script

$ update.php ../AdminSettings.php

(Note for simple installations on Windows (e. g. with ): You can run the update.php by executing it when your . are associated with the PHP.exe (if not, update.php, select Open With and browse to PHP.exe). Ensure that your (e. g. Apache) and your database (e. g. MySQL) are running).

will inspect the existing schema and update it to work with the new code, adding tables and columns as needed.

What to do in case of "No superuser credentials" error
In case the the script aborts with a message:

"No superuser credentials could be found. Please provide the details of a user with appropriate permissions to update the database. See AdminSettings.sample for more details"

This means that you should check that you have defined $wgDBadminuser and $wgDBadminpassword in your LocalSettings.php file (in the main directory). These are the user and password needed by this script in order to access to the database. See the example in the AdminSettings.sample file; you can copy that snippet in the LocalSettings.php file and change the user/password for your own database.

Alternative 1: phpShell
If full permissions/shell access is not available, look at options such as phpShell, which emulates a command prompt using PHP functions. This might not work on some locked-down hosting setups.

When using such a solution, it is often desirable to skip the countdown period at the start of the script. Pass the  option to the update script to do so:

$ php update.php --quick

You may have to use "php5" instead of "php" if different versions are installed. For phpshell, the commandLine.inc and LocalSettings.php files may have to be edited so the script doesn't quit because phpshell is a run from the web server. It may instead be possible to sidestep this problem by running:

$ unset REQUEST_METHOD; php update.php --quick

This unsets the REQUEST_METHOD environment variable, the existence of which causes the script to quit, and then executes the script.

Alternative 2: Re-run the installer
An alternative to running the update script from the shell is to re-run the web installer. To do this:


 * 1) Rename   to
 * 2) Make the   directory writable by the web server
 * 3) Make sure the database user has full rights to the database
 * 4) Browse to the wiki and start the installer
 * Fill in the form fields with the same values as was done during the previous version's installation.
 * When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema.
 * When this is complete, a new  will be generated.
 * 1) Delete the new configuration file
 * 2) Rename   back to
 * 3) Restore permissions on the   directory

Upgrade extensions
Certain extensions have been updated in order to work with MediaWiki 1.14. Be sure to upgrade to the latest versions of such extensions. You might need to perform manual updates to custom extensions.

Test the update
Once the upgrade has completed, browse to the wiki and check basics such as viewing and editing pages to ensure things still work as expected.

Visit and check that the version shown is correct.