tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-06-28 23:49:26 +02:00
Code Issues Projects Releases Wiki Activity

Consistent upgrading crosslinks in changelogs

Browse Source
This commit is contained in:
Ingo Schommer 2018-06-26 11:40:46 +12:00
parent 580999b570
commit 1b06be1a64
4 changed files with 15 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/03_Upgrading/index.md
View File

@ -6,10 +6,6 @@ introduction: Upgrade your project SilverStripe 4 and keep it up to date with th
SilverStripe applications should be kept up to date with the latest security releases. Usually an update or upgrade to
your SilverStripe installation means overwriting files, flushing the cache and updating your database schema.
<div class="info" markdown="1">
See our [upgrade notes and changelogs](/changelogs/4.0.0) for 4.0.0 specific information, bugfixes and API changes.
</div>
## Understanding and planning your upgrade {#planning}
How easy will it be to update my project? It's a fair question, and sometimes a difficult one to answer.

9
docs/en/04_Changelogs/4.0.0.md
View File

@ -5,11 +5,10 @@
This version introduces many breaking changes, which in most projects can be managed through a combination
of automatic upgrade processes as well as manual code review. This changelogs described all API changes in detail.
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe 3 project to SilverStripe 4.0
For users upgrading to 4.1.0 please see the specific [4.1.0 changelogs](4.1.0.md).
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe 3 project to SilverStripe 4.
It describes how to use an automated [upgrader tool](https://github.com/silverstripe/silverstripe-upgrader)
to make the job easier.
For users upgrading to later versions, please see the specific [4.1.0](4.1.0) and [4.2.0](4.2.0) changelogs.
## Overview {#overview}

10
docs/en/04_Changelogs/4.1.0.md
View File

@ -7,12 +7,12 @@
## Upgrading
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe project to SilverStripe 4.1
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe 3 project to SilverStripe 4.
It describes how to use an automated [upgrader tool](https://github.com/silverstripe/silverstripe-upgrader)
to make the job easier.
Please also note the [4.0.0](4.0.0) and [4.2.0](4.2.0) changelogs for a complete list of changes.
Note: if you receive an error message about an undefined constant while
upgrading with `composer`, re-running the command should solve the issue.
### Upgrade `public/` folder (optional) {#public-folder}
### Use `public/` folder (optional) {#public-folder}
This release allows the maintenance of a public webroot folder which separates all
web-accessible files from protected project files (like the vendor folder

8
docs/en/04_Changelogs/4.2.0.md
View File

@ -7,7 +7,10 @@
## Upgrading {#upgrading}
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe project to SilverStripe 4.1
[Read _Upgrading to SilverStripe 4_](/upgrading/) for a detailed step-by-step guide on upgrading your SilverStripe 3 project to SilverStripe 4.
It describes how to use an automated [upgrader tool](https://github.com/silverstripe/silverstripe-upgrader)
to make the job easier.
Please also note the [4.0.0](4.0.0) and [4.1.0](4.1.0) changelogs for a complete list of changes.
### App folder name
@ -50,7 +53,8 @@ SilverStripe\Core\Manifest\ModuleManifest:
- Ensure you flush your site with `?flush=all`
Note: In 5.0 the app folder will be fixed to `app` and cannot be soft-coded via `mysite.yml`
Follow our [step-by-step upgrading guide](/upgrading) to perform this change automatically through our `upgrade-code` tool.
In 5.0 the app folder will be fixed to `app` and cannot be soft-coded via `mysite.yml`
### Disable session-based stage setting