Make WordPress Core


Ignore:
Timestamp:
08/14/2008 06:30:38 AM (16 years ago)
Author:
westi
Message:

phpdoc for wp-admin. See #7496 props santosj.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/wp-admin/includes/update-core.php

    r8600 r8645  
    11<?php
    2 
     2/**
     3 * WordPress core upgrade functionality.
     4 *
     5 * @package WordPress
     6 * @subpackage Administration
     7 * @since 2.7
     8 */
     9
     10/**
     11 * Stores files to be deleted.
     12 *
     13 * @since 2.7
     14 * @global array $_old_files
     15 * @var array
     16 * @name $_old_files
     17 */
    318global $_old_files;
    419
     
    118133);
    119134
     135/**
     136 * Upgrade the core of WordPress.
     137 *
     138 * This will create a .maintenance file at the base of the WordPress directory
     139 * to ensure that people can not access the web site, when the files are being
     140 * copied to their locations.
     141 *
     142 * The files in the {@link $_old_files} list will be removed and the new files
     143 * copied from the zip file after the database is upgraded.
     144 *
     145 * The steps for the upgrader for after the new release is downloaded and
     146 * unzipped is:
     147 *   1. Test unzipped location for select files to ensure that unzipped worked.
     148 *   2. Create the .maintenance file in current WordPress base.
     149 *   3. Copy new WordPress directory over old WordPress files.
     150 *   4. Upgrade WordPress to new version.
     151 *   5. Delete new WordPress directory path.
     152 *   6. Delete .maintenance file.
     153 *   7. Remove old files.
     154 *   8. Delete 'update_core' option.
     155 *
     156 * There are several areas of failure. For instance if PHP times out before step
     157 * 6, then you will not be able to access any portion of your site. Also, since
     158 * the upgrade will not continue where it left off, you will not be able to
     159 * automatically remove old files and remove the 'update_core' option. This
     160 * isn't that bad.
     161 *
     162 * If the copy of the new WordPress over the old fails, then the worse is that
     163 * the new WordPress directory will remain.
     164 *
     165 * If it is assumed that every file will be copied over, including plugins and
     166 * themes, then if you edit the default theme, you should rename it, so that
     167 * your changes remain.
     168 *
     169 * @param string $from New release unzipped path.
     170 * @param string $to Path to old WordPress installation.
     171 * @return WP_Error|null WP_Error on failure, null on success.
     172 */
    120173function update_core($from, $to) {
    121174    global $wp_filesystem, $_old_files;
Note: See TracChangeset for help on using the changeset viewer.