tour "privacy": remove very advanced (and dangerous) last step about configuring $conf[available_permission_levels]

git-svn-id: http://piwigo.org/svn/trunk@29455 68402e56-0260-453c-a942-63ccdbb3a9ee

1 files changed, 0 insertions, 2 deletions

diff --git a/plugins/TakeATour/language/en_UK/plugin.lang.php b/plugins/TakeATour/language/en_UK/plugin.lang.php
index a2aa7e8dd..b2b00335d 100644
--- a/plugins/TakeATour/language/en_UK/plugin.lang.php
+++ b/plugins/TakeATour/language/en_UK/plugin.lang.php
@@ -171,8 +171,6 @@ $lang['privacy_title21'] = 'Public photos';
 $lang['privacy_stp21'] = 'Solutions are:<ul><li>put a watermark, at least on medium and high def photos.</li><li>and disable XL and XXL sizes.</li><li>and disable the High Definition (download and display of the original photo) for the concerned users.';
 $lang['privacy_title22'] = 'Local Config: Original protection';
 $lang['privacy_stp22'] = '<em>For Advanced Users</em><br><br>In Piwigo, you can protect the original photos using your local configuration. Use the variable $conf[\'original_url_protection\']: by default empty, you set the value to "images" to protect only the photos or "all" to protect also all type of media, which can be ressource consumming or might simply don\'t work on your server.<br><br>This option works for public and private content. This option currently requires you to deny the acces to the folders /upload and /galleries, by using an .htaccess file (usually a text file with "Deny from all" for content) or the server configurations.<br><br>Please note that filenames of photos uploaded using other method than FTP are <b>randomized</b>, so they are impossible to guess: that filename and so the path to the original photo can be known only if the visitor has access to a resized version of that photo, like the thumbnail. $conf[\'original_url_protection\'] and denying access to the folders /upload and /galleries are meant to avoid that case.';
-$lang['privacy_title23'] = 'Local Config: Privacy Level';
-$lang['privacy_stp23'] = '<em>For Advanced Users</em><br><br>Curently Privacy Levels are hard coded in the local configuration variable $conf[\'available_permission_levels\']. You can add a new level, by adding an intermediate number, but removing a level is highly inadvisable. You may want to translate your new level: use $lang[\'Level X\'] where X is your new number.';
 $lang['privacy_title24'] = 'It\'s been a great time';
 $lang['privacy_stp24'] = 'This tour is over.<p style="text-align:center">Enjoy your Piwigo!</p>If you like Piwigo and want to support us, you can contribute by helping for translations, donating, etc. <a href="http://piwigo.org/basics/contribute" target="_blank">Click here to support us</a>. Thanks!';