change default configuration settings for a stable branch. Developers who need previous configuration settings can modify them in their local configuration

git cherry-pick 39d3c6883b181317205b2b3e31c20baf116ac3b2

1 files changed, 4 insertions, 4 deletions

diff --git a/include/config_default.inc.php b/include/config_default.inc.php
index f66dab486..91d620edb 100644
--- a/include/config_default.inc.php
+++ b/include/config_default.inc.php
@@ -121,7 +121,7 @@ $conf['paginate_pages_around'] = 2;
 
 // show_version : shall the version of Piwigo be displayed at the
 // bottom of each page ?
-$conf['show_version'] = true;
+$conf['show_version'] = false;
 
 // meta_ref to reference multiple sets of incorporated pages or elements
 // Set it false to avoid referencing in google, and other search engines.
@@ -238,7 +238,7 @@ $conf['available_permission_levels'] = array(0,1,2,4,8);
 //
 // This configuration parameter is set to true in BSF branch and to false
 // elsewhere.
-$conf['check_upgrade_feed'] = true;
+$conf['check_upgrade_feed'] = false;
 
 // rate_items: available rates for a picture
 $conf['rate_items'] = array(0,1,2,3,4,5);
@@ -430,7 +430,7 @@ $conf['session_use_ip_address'] = true;
 $conf['show_queries'] = false;
 
 // show_gt : display generation time at the bottom of each page
-$conf['show_gt'] = true;
+$conf['show_gt'] = false;
 
 // debug_l10n : display a warning message each time an unset language key is
 // accessed
@@ -443,7 +443,7 @@ $conf['debug_template'] = false;
 $conf['debug_mail'] = false;
 
 // die_on_sql_error: if an SQL query fails, should everything stop?
-$conf['die_on_sql_error'] = true;
+$conf['die_on_sql_error'] = false;
 
 // if true, some language strings are replaced during template compilation
 // (instead of template output). this results in better performance. however