Doc update for #587

3 files changed, 9 insertions, 1 deletions

diff --git a/HISTORY b/HISTORY
index 3679f27f..e6fb420a 100644
--- a/HISTORY
+++ b/HISTORY
@@ -15,6 +15,7 @@ BUG: TJuiDialog: avoid "cannot call methods on dialog prior to initialization" e
 BUG: Fix callback update of TActiveCheckBoxList when initially empty (LCSKJ)
 ENH: Issue #562 - Added TClientStyleSheet::PradoStyles (ctrlaltca)
 ENH: Issue #569 - Improved TJavascriptLogger / browser console logging of errors (ctrlaltca)
+ENH: Issue #587 - Misc foxed for PHP7 compatibility (emkael)
 ENH: Applied some misc optimizations to class serialization (ctrlaltca)
 ENH: Intercept fatal errors using register_shutdown_function (ctrlaltca)
 ENH: Activecontrols: avoid updating client side if the value didn't change (ctrlaltca)
diff --git a/UPGRADE b/UPGRADE
index e445c329..1230a15b 100644
--- a/UPGRADE
+++ b/UPGRADE
@@ -9,6 +9,13 @@ 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.3.0
+---------------------
+- The long-time deprecated 'MySQL' translation source has been removed.
+  The 'Database' source can be used instead, specifying a valid ConnectionID
+  in the source parameter:
+  <translation type="Database" source="db1" autosave="true" cache="false" />
+
 Upgrading from v3.2.x
 ---------------------
 - Since PRADO 3.3.0, jQuery is the javascript framework of choice. All the existing PRADO controls have
diff --git a/demos/quickstart/protected/pages/Advanced/Samples/I18N/Home.page b/demos/quickstart/protected/pages/Advanced/Samples/I18N/Home.page
index 9f66bad8..a7e743c7 100755
--- a/demos/quickstart/protected/pages/Advanced/Samples/I18N/Home.page
+++ b/demos/quickstart/protected/pages/Advanced/Samples/I18N/Home.page
@@ -14,7 +14,7 @@ Your current culture is <%= $this->Page->CurrentCulture %>.
 </p>

 

 <p>

-	In addition to culture aware template. Text can be localized using many different translation sources. PRADO provides gettext, XML, SQLite, and MySQL container for storing message translations. The example in the following link demonstrates how text can be localized using the TTranslate component.

+	In addition to culture aware template. Text can be localized using many different translation sources. PRADO provides gettext, XML, SQLite, and Database container for storing message translations. The example in the following link demonstrates how text can be localized using the TTranslate component.

 </p>

 <hr />

 <h2>Introduction</h2>