Skip to content
This repository

Showing 1 changed file with 22 additions and 21 deletions. Show diff stats Hide diff stats

  1. 43  docs/en/installation/upgrading.md
43  docs/en/installation/upgrading.md
Source Rendered
... ...
@@ -1,40 +1,41 @@
1 1
 # Upgrading
2 2
 
3  
-Usually an update or upgrade your SilverStripe installation just means overwriting files and updating your
4  
-database-schema. Please see your [upgrade notes and changelogs](/changelogs).
  3
+Usually an update or upgrade your SilverStripe installation just means 
  4
+overwriting files and updating your database-schema. 
5 5
 
6  
-## Process
  6
+See our [upgrade notes and changelogs](/changelogs) for release-specific information.
7 7
 
8  
-Never update a website on the live server without trying it on a development copy first.
  8
+## Process
9 9
 
10 10
 *  Check if any modules (e.g. blog or forum) in your installation are compatible and need to be upgraded as well
11  
-*  Backup your database
12  
-*  Backup your website
  11
+*  Backup your database content
  12
+*  Backup your webroot files
13 13
 *  Download the new release and uncompress it to a temporary folder
14 14
 *  Leave custom folders like *mysite* or *themes* in place.
15  
-*  Identify system folders in your webroot (`cms`, `framework` and any additional modules). 
16  
-* Delete existing system folders (or move them outside of your webroot)
17  
-* Extract and replace system folders from your download (Deleting instead of "copying over" existing folders
18  
-ensures that files removed from the new SilverStripe release are not persisting in your installation)
  15
+*  Identify system folders in your webroot (`cms`, `framework`, `sapphire` and any additional modules). 
  16
+*  Delete existing system folders (or move them outside of your webroot)
  17
+*  Extract and replace system folders from your download (Deleting instead of "copying over" existing folders ensures that files removed from the new SilverStripe release are not persisting in your installation)
  18
+*  Visit http://yoursite.com/dev/build/?flush=1 to rebuild the website database
  19
+*  Check if you need to adapt your code to changed PHP APIs
  20
+*  Check if you have overwritten any core templates or styles which might need an update
  21
+*  See [common-problems](common-problems) for a list of likely mistakes that could happen during an upgrade.
19 22
 
20  
-*  Visit http://yoursite.com/dev/build/?flush=1 to rebuild the website Database
21  
-*  Check if you need to adapt your code to changed APIs
22  
-*  Check if you need to adapt your code to changed CSS/HTML/JS
  23
+<div class="warning" markdown="1">
  24
+	Never update a website on the live server without trying it on a development copy first.
  25
+</div>
23 26
 
24  
-* See [common-problems](common-problems) for a list of likely mistakes that could happen during an upgrade.
25 27
 
26 28
 ##  Decision Helpers
27 29
 
28  
-How easy will it be to update my project? It's a fair question, and sometimes a difficult one to answer.  This page is
29  
-intended to help you work out how hard it will be to upgrade your site.
  30
+How easy will it be to update my project? It's a fair question, and sometimes a difficult one to answer. 
30 31
 
31  
-*  If you've made custom branches of the core, or of a module, it's going to be harder to upgrade.
32  
-*  The more custom features you have, the harder it will be to upgrade.  You will have to re-test all of those features
33  
-and some of them may have broken.
34  
-*  Customisations of a well defined type - such as custom page types or custom blog widgets - are going to be easier to
35  
-upgrade than customisations that use sneaky tricks, such as the subsites module.
  32
+*  "Micro" releases (x.y.z) are explicitly backwards compatible, "minor" and "major" releases can deprecate features and change APIs (see our [/misc/release-process](release process) for details)
  33
+*  If you've made custom branches of SilverStripe core, or any thirdparty module, it's going to be harder to upgrade.
  34
+*  The more custom features you have, the harder it will be to upgrade.  You will have to re-test all of those features, and adapt to API changes in core.
  35
+*  Customisations of a well defined type - such as custom page types or custom blog widgets - are going to be easier to upgrade than customisations that modify deep system internals like rewriting SQL queries.
36 36
 
37 37
 ## Related
38 38
 
39 39
 *  [Release Announcements](http://groups.google.com/group/silverstripe-announce/)
40 40
 *  [Blog posts about releases on silverstripe.org](http://silverstripe.org/blog/tag/release)
  41
+* [/misc/release-process](Release Process)

0 notes on commit 56a3777

Please sign in to comment.
Something went wrong with that request. Please try again.