diff options
author | ctrlaltca@gmail.com <> | 2011-06-20 14:58:24 +0000 |
---|---|---|
committer | ctrlaltca@gmail.com <> | 2011-06-20 14:58:24 +0000 |
commit | e1221aca75d8f843c77fe7271bc5132c33b14cd9 (patch) | |
tree | 5a0446c35755335c23892b403f95364cacfe2746 /UPGRADE | |
parent | 5bad64509635a863e5fc952d54fabe711df2b7e2 (diff) |
docs updates
Diffstat (limited to 'UPGRADE')
-rw-r--r-- | UPGRADE | 19 |
1 files changed, 19 insertions, 0 deletions
@@ -9,6 +9,25 @@ if you want to upgrade from version A to version C and there is version B between A and C, you need to following the instructions for both A and B. +Upgrading from v3.1.x +--------------------- +- Prado 3.2 requires PHP >= 5.2 + +Upgrading from v3.1.8 +--------------------- +- An new "TranslateDefaultCulture" option has been added to TGlobalization that lets you choose if Prado + have to translate the default culture (default up to 3.1.7) or not (changed in 3.1.8). This option is + enabled by default, in fact restoring the pre-3.1.8 behaviour of translating also the default culture. + You want this option to be enabled if: + - you write pseudo translation tags in your code like <%[page_title_welcome]%> and need Prado to insert + the proper translation for every language (i.e. the base text is not written in a real language); + - your default culture is different from the culture used in your project (eg. your DefaultCulture is + "fr", but text in your pages is written in english to ensure other team members will understand it); + You want this option to be disabled if: + - you write code in your DefaultCulture language like <%[Welcome to my website]%>. For users viewing + your pages in that same Culture, Prado won't even try to translate these strings. Translation will + occur normally for every other culture. + Upgrading from v3.1.7 --------------------- - behavior of THttpRequest::getBaseUrl() and THttpRequest::getAbsoluteApplicationUrl() changed: |