diff options
| author | Gareth Rees <gareth@mysociety.org> | 2015-03-26 11:24:33 +0000 |
|---|---|---|
| committer | Gareth Rees <gareth@mysociety.org> | 2015-04-07 16:25:07 +0100 |
| commit | 4bfb1e947e5e8a518f2ad48b9b49e5680fc14e4f (patch) | |
| tree | 6186e411612db57eb8e93f6b11888ad7bdb5ccf8 /docs/running/upgrading.md | |
| parent | d19f011e202341cd0eeb528a1f4620e696347620 (diff) | |
Replace site.baseurl with page.baseurl
Content URLs need page.baseurl to include the current locale
Diffstat (limited to 'docs/running/upgrading.md')
| -rw-r--r-- | docs/running/upgrading.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/running/upgrading.md b/docs/running/upgrading.md index 88aeb7b2d..39c18163c 100644 --- a/docs/running/upgrading.md +++ b/docs/running/upgrading.md @@ -76,7 +76,7 @@ Patch version increases (e.g. 0.1.2.3 → 0.1.2.**4**) should not require any Minor version increases (e.g. 0.1.2.4 → 0.1.**3**.0) will usually require further action. You should read the [`CHANGES.md`](https://github.com/mysociety/alaveteli/blob/master/doc/CHANGES.md) document to see what's changed since your last deployment, paying special attention to anything in the "Upgrade notes" sections. Any upgrade may include new translations strings, that is, new or altered messages -to the user that need translating to your locale. You should visit <a href="{{ site.baseurl }}docs/glossary/#transifex" class="glossary__link">Transifex</a> +to the user that need translating to your locale. You should visit <a href="{{ page.baseurl }}/docs/glossary/#transifex" class="glossary__link">Transifex</a> and try to get your translation up to 100% on each new release. Failure to do so means that any new words added to the Alaveteli source code will appear in your website in English by default. If your translations didn't make it to the |