COM_ADMINTOOLS="Admin Tools"
COM_ADMINTOOLS_CONFIGURATION="Admin Tools: Options"

[common]
COM_ADMINTOOLS_COMMON_LBL_COPY_LABEL="Copy"
COM_ADMINTOOLS_COMMON_LBL_AUTOCLOSEIN3S="This window will close automatically in 3 seconds."

COM_ADMINTOOLS_COMMON_LBL_CONSOLEWARN_TITLE="Warning!"
COM_ADMINTOOLS_COMMON_LBL_CONSOLEWARN_BODY1="This browser feature is aimed to developers only. If you were instructed to copy something here to enable some kind of 'hidden feature', in reality it's an attempt to compromise your account"
COM_ADMINTOOLS_COMMON_LBL_CONSOLEWARN_BODY2="For further info see https://en.wikipedia.org/wiki/Self-XSS"

[cli]
COM_ADMINTOOLS_CLI_COMMON_ERR_NOTFOUND="Can not load record %s"
COM_ADMINTOOLS_CLI_COMMON_MISSING_REQUIRED="Missing required param “%s”"
COM_ADMINTOOLS_CLI_COMMON_LIST_OPT_FORMAT="Output format: table, json, yaml, csv, count."
COM_ADMINTOOLS_CLI_COMMON_OPT_ID="ID of the row"
COM_ADMINTOOLS_CLI_COMMON_REMOVE_ERR_NOTFOUND="Cannot delete row with ID %s; ID not found."
COM_ADMINTOOLS_CLI_COMMON_REMOVE_ERR_FAILED="Cannot delete ID #%s: %s"
COM_ADMINTOOLS_CLI_COMMON_REMOVE_LBL_SUCCESS="ID #%d has been deleted."
COM_ADMINTOOLS_CLI_COMMON_CREATE_ERR_MISSING="Can not create record, required data is missing"
COM_ADMINTOOLS_CLI_COMMON_CREATE_ERR_FAILED="Cannot create record: %s"
COM_ADMINTOOLS_CLI_COMMON_CREATE_LBL_SUCCESS="Created new record with ID %s."
COM_ADMINTOOLS_CLI_COMMON_CREATE_OPT_FORMAT="The format for the response. Use JSON to get a JSON-parseable numeric ID of the new record. Values: text, json"
COM_ADMINTOOLS_CLI_COMMON_MODIFY_ERR_FAILED="Cannot modify record: %s"
COM_ADMINTOOLS_CLI_COMMON_MODIFY_LBL_SUCCESS="Modified record with ID %s."
COM_ADMINTOOLS_CLI_SCAN_HELP="<info>%command.name%</info> will run Admin Tools' PHP File Change Scanner.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_SCAN_DESC="Scan your site's files for security issues with Admin Tools"
COM_ADMINTOOLS_CLI_SCAN_HEAD="Beginning a site scan with the PHP File Change Scanner"
COM_ADMINTOOLS_CLI_ERR_CANNOT_GENERATE_YAML="Cannot generate YAML"
COM_ADMINTOOLS_CLI_ERR_YAML_EXTENSION_NOT_FOUND="Your PHP installation does not have the PHP YAML extension installed or enabled."
COM_ADMINTOOLS_CLI_WAFLIST_DESC="List all WAF rules"
COM_ADMINTOOLS_CLI_WAFLIST_HELP="<info>%command.name%</info> will display Admin Tools' WAF rules.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFGET_OPT_RULE="The name for the rule to get"
COM_ADMINTOOLS_CLI_WAFGET_DESC="Get the value of a WAF configuration option"
COM_ADMINTOOLS_CLI_WAFGET_HELP="<info>%command.name%</info> will get the value of a Admin Tools' WAF configuration option.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFGET_ERR_CANNOT_FIND="Cannot find option “%s”."
COM_ADMINTOOLS_CLI_WAFSET_DESC="Set a specific option of WAF configuration"
COM_ADMINTOOLS_CLI_WAFSET_HELP="<info>%command.name%</info> will set a specific Admin Tools' WAF rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFSET_OPT_KEY="Option name"
COM_ADMINTOOLS_CLI_WAFSET_OPT_VALUE="Option value"
COM_ADMINTOOLS_CLI_WAFSET_ERR_CANNOT_FIND="Cannot find option “%s”."
COM_ADMINTOOLS_CLI_WAFSET_OPT_ADD="Add a value to current list of values (supported keys only)"
COM_ADMINTOOLS_CLI_WAFSET_OPT_DESCRIPTION="Set the description of an item added to the current list of values (supported keys only)"
COM_ADMINTOOLS_CLI_WAFSET_OPT_REMOVE="Remove a value to current list of values (supported keys only)"
COM_ADMINTOOLS_CLI_WAFSET_OPT_EMPTY="Clear all stored values (supported keys only)"
COM_ADMINTOOLS_CLI_WAFSET_ERR_LIST_NOTALLOWED="The --add, --remove and --empty options only apply to configuration keys with multiple values (arrays)."
COM_ADMINTOOLS_CLI_WAFSET_ERR_DESCRIPTION_NOTALLOWED="The --description option can only be applied with the --add option."
COM_ADMINTOOLS_CLI_WAFSET_ERR_MUTUALLY_EXCLUSIVE="The --value, --add, --remove and --empty options are mutually exclusive. You can only use one of them."
COM_ADMINTOOLS_CLI_WAFSET_ERR_NO_ACTION="You must use one of the --value, --add, --remove and --empty options to tell me what to do."
COM_ADMINTOOLS_CLI_WAFSET_LBL_SETTING="The value of the ‘%s’ WAF configuration option has been changed."
COM_ADMINTOOLS_CLI_WAFSET_LBL_UNCHANGED="The value of the ‘%s’ WAF configuration option has remained unchanged."
COM_ADMINTOOLS_CLI_WAFUNBLOCK_HELP="<info>%command.name%</info> will unblock an IP.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFUNBLOCK_DESC="Unblock an IP previously blocked by Admin Tools"
COM_ADMINTOOLS_CLI_WAFUNBLOCK_LBL_IP="IP “%s” has been unblocked"
COM_ADMINTOOLS_CLI_WAFUNBLOCK_OPT_IP="IP that should be unblocked"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONSLIST_DESC="List all Admin Tools' WAF exceptions"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONSLIST_HELP="<info>%command.name%</info> will list all Admin Tools' WAF exceptions.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_REMOVE_DESC="Delete an Admin Tools' WAF Exception rule"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_REMOVE_HELP="<info>%command.name%</info> will delete an Admin Tools' WAF exception rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_ADD_DESC="Create a new Admin Tools' WAF exception"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_ADD_HELP="<info>%command.name%</info> will create a new Admin Tools WAF exception.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_ADD_OPT_COMPONENT="Component that should added to the WAF exception"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_ADD_OPT_VIEW="View name that should added to the WAF exception"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_ADD_OPT_QUERY="Query parameter that should added to the WAF exception"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_MODIFY_DESC="Modify an Admin Tools' WAF exception"
COM_ADMINTOOLS_CLI_WAFEXCEPTIONS_MODIFY_HELP="<info>%command.name%</info> will modify an Admin Tools WAF exception.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFDENY_LIST_DESC="List all Admin Tools' WAF deny rules"
COM_ADMINTOOLS_CLI_WAFDENY_LIST_HELP="<info>%command.name%</info> will list all Admin Tools' WAF deny rules.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFDENY_REMOVE_DESC="Delete an Admin Tools' WAF deny rule"
COM_ADMINTOOLS_CLI_WAFDENY_REMOVE_HELP="<info>%command.name%</info> will delete an Admin Tools' WAF deny rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_DESC="Create a new Admin Tools' WAF deny rule"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_HELP="<info>%command.name%</info> will create a new Admin Tools WAF deny rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_APPLICATION="Application side where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_COMPONENT="Option name where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_VIEW="View name where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_TASK="Task where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_QUERY="Query param where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_QUERY_TYPE="Type of checks that should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_QUERY_CONTENT="Query content that should match the rule"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_VERB="HTTP verb where the rule should be applied"
COM_ADMINTOOLS_CLI_WAFDENY_ADD_OPT_ENABLED="Should the rule be enabled?"
COM_ADMINTOOLS_CLI_WAFDENY_MODIFY_DESC="Modify an Admin Tools' WAF deny rule"
COM_ADMINTOOLS_CLI_WAFDENY_MODIFY_HELP="<info>%command.name%</info> will modify an Admin Tools WAF deny rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPALLOW_LIST_DESC="List Administrator Exclusive Allow IP"
COM_ADMINTOOLS_CLI_IPALLOW_LIST_HELP="<info>%command.name%</info> will list Admin Tools WAF IP exclusive access.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPALLOW_REMOVE_DESC="Remove an entry from the Administrator Exclusive Allow IP list"
COM_ADMINTOOLS_CLI_IPALLOW_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools WAF IP exclusive access.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPALLOW_ADD_DESC="Add a new IP to the Administrator Exclusive Allow List"
COM_ADMINTOOLS_CLI_IPALLOW_ADD_HELP="<info>%command.name%</info> will add a new entry in the Admin Tools Administrator Exclusive Allow IP list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPALLOW_ADD_OPT_IP="IP address"
COM_ADMINTOOLS_CLI_IPALLOW_ADD_OPT_DESCR="Description"
COM_ADMINTOOLS_CLI_IPALLOW_MODIFY_DESC="Modify an IP in the Administrator Exclusive Allow List"
COM_ADMINTOOLS_CLI_IPALLOW_MODIFY_HELP="<info>%command.name%</info> will modify an entry inside Admin Tools WAF IP exclusive access.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPDISALLOW_LIST_DESC="List Site IP Disallow List entries"
COM_ADMINTOOLS_CLI_IPDISALLOW_LIST_HELP="<info>%command.name%</info> will list Admin Tools WAF IP blocked access.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPDISALLOW_REMOVE_DESC="Remove an entry from the Site IP Disallow List"
COM_ADMINTOOLS_CLI_IPDISALLOW_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools WAF IP blocked access.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPDISALLOW_ADD_DESC="Add a new IP to the Site IP Disallow List"
COM_ADMINTOOLS_CLI_IPDISALLOW_ADD_HELP="<info>%command.name%</info> will add a new entry in the Admin Tools Site IP Disallow list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IPDISALLOW_ADD_OPT_IP="IP address"
COM_ADMINTOOLS_CLI_IPDISALLOW_ADD_OPT_DESCR="Description"
COM_ADMINTOOLS_CLI_IPDISALLOW_MODIFY_DESC="Modify an IP in the Site IP Disallow list"
COM_ADMINTOOLS_CLI_IPDISALLOW_MODIFY_HELP="<info>%command.name%</info> will modify an entry inside Admin Tools WAF Site IP Disallow List.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_BADWORDS_LIST_DESC="List Bad Words entries"
COM_ADMINTOOLS_CLI_BADWORDS_LIST_HELP="<info>%command.name%</info> will list Admin Tools WAF bad words.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_BADWORDS_ADD_DESC="Add a new entry to the Bad Words List"
COM_ADMINTOOLS_CLI_BADWORDS_ADD_HELP="<info>%command.name%</info> will add a new entry in the Admin Tools Bad Words list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_BADWORDS_ADD_OPT_WORD="Bad word that should be blocked"
COM_ADMINTOOLS_CLI_BADWORDS_REMOVE_DESC="Remove an entry from the Bad Words list"
COM_ADMINTOOLS_CLI_BADWORDS_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools WAF bad words list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_LOG_LIST_DESC="List entries from Blocked Requests log"
COM_ADMINTOOLS_CLI_LOG_LIST_HELP="<info>%command.name%</info> will list Admin Tools WAF blocked requests.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_LOG_REMOVE_DESC="Remove an entry from Blocked Requests log"
COM_ADMINTOOLS_CLI_LOG_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools blocked requests.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_AUTOBANHISTORY_LIST_DESC="List entries from Automatic IP Blocking History"
COM_ADMINTOOLS_CLI_AUTOBANHISTORY_LIST_HELP="<info>%command.name%</info> will list Admin Tools Automatic IP Blocking History.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_AUTOBANHISTORY_REMOVE_DESC="Remove an entry from Automatic IP Blocking History list"
COM_ADMINTOOLS_CLI_AUTOBANHISTORY_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools Automatic IP Blocking History list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_AUTOBAN_LIST_DESC="List entries from Automatically Blocked IP addresses"
COM_ADMINTOOLS_CLI_AUTOBAN_LIST_HELP="<info>%command.name%</info> will list Admin Tools WAF Automatically Blocked IPs.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_AUTOBAN_REMOVE_DESC="Remove an entry from Automatically Blocked IP list"
COM_ADMINTOOLS_CLI_AUTOBAN_REMOVE_HELP="<info>%command.name%</info> will remove an entry from Admin Tools Automatically Blocked IP list.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_OFFLINE_DESC="Enable or disable Admin Tools' Emergency Offline mode"
COM_ADMINTOOLS_CLI_OFFLINE_HELP="<info>%command.name%</info> will tell Admin Tools to enable or disable the Emergency Offline mode.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_OFFLINE_OPT_ENABLE="Enable the Emergency Offline mode"
COM_ADMINTOOLS_CLI_OFFLINE_OPT_DISABLE="Disable the Emergency Offline mode"
COM_ADMINTOOLS_CLI_OFFLINE_MISSING_MODE="You should either enable or disable the Emergency Offline mode"
COM_ADMINTOOLS_CLI_OFFLINE_RESULT_SUCCESS="Operation successfully completed"
COM_ADMINTOOLS_CLI_OFFLINE_RESULT_FAILURE="An error occurred while changing the mode"
COM_ADMINTOOLS_CLI_EXPORT_DESC="Export Admin Tools configuration"
COM_ADMINTOOLS_CLI_EXPORT_HELP="<info>%command.name%</info> will export Admin Tools configuration.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_EXPORT_OPT_FILE="File to redirect exported data"
COM_ADMINTOOLS_CLI_EXPORT_TOFILE="Configuration data exported to %s"
COM_ADMINTOOLS_CLI_IMPORT_DESC="Import Admin Tools configuration"
COM_ADMINTOOLS_CLI_IMPORT_HELP="<info>%command.name%</info> will import Admin Tools configuration.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_IMPORT_FILE_MISSING="Missing or invalid file '%s'"
COM_ADMINTOOLS_CLI_IMPORT_OPT_FILE="File containing JSON encoded configuration"
COM_ADMINTOOLS_CLI_IMPORT_ERRORS="An error occurred while importing data: %s"
COM_ADMINTOOLS_CLI_IMPORT_SUCCESS="Successfully imported data from %s"
COM_ADMINTOOLS_CLI_SERVERCONFIGGET_DESC="Set a specific option for server configuration file"
COM_ADMINTOOLS_CLI_SERVERCONFIGGET_HELP="info>%command.name%</info> will set a specific Admin Tools' Server Configuration option.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_SERVERCONFIG_OPT_RULE="The name for the rule to get"
COM_ADMINTOOLS_CLI_SERVERCONFIG_ERR_CANNOT_FIND="Cannot find option “%s”."
COM_ADMINTOOLS_CLI_SERVERCONFIGLIST_DESC="List all server configuration rules"
COM_ADMINTOOLS_CLI_SERVERCONFIGLIST_HELP="<info>%command.name%</info> will display Admin Tools' Server Configuration rules.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_ERR_NO_ACTION="You must use one of the --value, --add, --remove and --empty options to tell me what to do."
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_ERR_MUTUALLY_EXCLUSIVE="The --value, --add, --remove and --empty options are mutually exclusive. You can only use one of them."
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_LBL_UNCHANGED="The value of the ‘%s’ WAF configuration option has remained unchanged."
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_LBL_SETTING="The value of the ‘%s’ server configuration option has been changed."
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_OPT_KEY="Option name"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_OPT_VALUE="Option value"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_OPT_ADD="Add a value to current list of values (supported keys only)"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_OPT_REMOVE="Remove a value to current list of values (supported keys only)"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_OPT_EMPTY="Clear all stored values (supported keys only)"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_DESC="Set a specific rule of server configuration"
COM_ADMINTOOLS_CLI_SERVERCONFIGSET_HELP="<info>%command.name%</info> will set a specific Admin Tools' Server Configuration rule.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_DESC="Generates server configuration file accordingly to Admin Tools' rules"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_HELP="<info>%command.name%</info> will create Admin Tools' Server configuration file.\nUsage: <info>php %command.full_name%</info>"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_OPT_PREVIEW="Output the configuration instead of writing it to disk"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_OPT_VERSION="Force Server Engine to a specific version"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_OPT_WRITEKO="An error occurred while writing server configuration file to disk"
COM_ADMINTOOLS_CLI_SERVERCONFIGMAKE_OPT_WRITEOK="Server configuration file correctly written to disk"

[options]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Component Options
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;; File Scanner
COM_ADMINTOOLS_JCONFIG_SCAN_LABEL="File Scanner"
COM_ADMINTOOLS_JCONFIG_SCAN_DESC="Configure how the PHP File Scanner works"

COM_ADMINTOOLS_JCONFIG_LOGLEVEL_LABEL="Log Level"
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_DESC="The verbosity of the PHP File Scanner log, kept in your site's configured log directory. Recommended values: “Warnings” for production sites, “Debug” when you want to request support from us."
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_NONE="None"
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_ERROR="Errors"
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_WARNING="Warnings"
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_INFO="Information"
COM_ADMINTOOLS_JCONFIG_LOGLEVEL_DEBUG="Debug"
COM_ADMINTOOLS_JCONFIG_MINEXEC_LABEL="Minimum Request Time"
COM_ADMINTOOLS_JCONFIG_MINEXEC_DESC="Minimum amount of time each request to the PHP File Change Scanner will take. Increase if your server throws an error because requests are coming in too frequent or you hit CPU / resource limits.<br/><br/>Recommended values: 2.0 to 7.0."
COM_ADMINTOOLS_JCONFIG_MAXEXEC_LABEL="Maximum Work Time"
COM_ADMINTOOLS_JCONFIG_MAXEXEC_DESC="Maximum amount of time consumed scanning your site in each request to the PHP File Change Scanner. Decrease if you hit your server's CPU / resource limits. Set lower than the Minimum Request Time to create a “CPU usage cool down” period, thereby reducing your resource usage during file scanning at the expense of making the scanning slower.<br/><br/>Recommended values: 3.0 to 7.0"
COM_ADMINTOOLS_JCONFIG_RUNTIMEBIAS_LABEL="Work Time Bias"
COM_ADMINTOOLS_JCONFIG_RUNTIMEBIAS_DESC="A value 50 to 100 which affects how aggressively Admin Tools will predict if it's about to hit the Maximum Work Time limit. 50 is most aggressive and will result in scanning taking about half of the Maximum Work Time in each request to the PHP File Change Scanner. 100 is the least aggressive and will result in scanning taking at least and usually more than the Maximum Work Time in each request.<br/><br/>Recommended value: 75.<br/><br/><strong>Tip!</strong> If you have a particularly sensitive server we recommend setting Minimum Request Time 7.0, Maximum Work Time 5.0 and Work Time Bias 50. This means that the scanner works for 2.5 to 5.0 seconds at a time and then your server does nothing for 2.0 to 4.5 seconds. Scanning your site will take about three times longer but it has a better chance of completing."
COM_ADMINTOOLS_JCONFIG_DIRTHRESHOLD_LABEL="Max. number of Folders per batch"
COM_ADMINTOOLS_JCONFIG_DIRTHRESHOLD_DESC="The maximum number of folders to list in a given directory at once. This prevents PHP timing out when listing the contents of <em>really</em> big folders, with hundreds of folders contained directly inside them.<br/><br/>Recommended value: 50<br/><br/>Remember, listing the contents of folders is <strong>exponentially proportional</strong> to the number of files and folders contained in them. This is a limitation of how Operating Systems and their filesystem drivers work. It's nothing us, Joomla! or PHP can do about. You are strongly advised to exclude really big folders and take steps to prevent having folders with thousands of directly contained files and folders. If unsure, nest your folders deeply."
COM_ADMINTOOLS_JCONFIG_FILETHRESHOLD_LABEL="Max. number of Files per batch"
COM_ADMINTOOLS_JCONFIG_FILETHRESHOLD_DESC="The maximum number of files to list in a given directory at once. This prevents PHP timing out when listing the contents of <em>really</em> big folders, with thousands of files contained directly inside them.<br/><br/>Recommended value: 100<br/><br/>Remember, listing the contents of folders is <strong>exponentially proportional</strong> to the number of files and folders contained in them. This is a limitation of how Operating Systems and their filesystem drivers work. It's nothing us, Joomla! or PHP can do about. You are strongly advised to exclude really big folders and take steps to prevent having folders with thousands of directly contained files and folders. If unsure, nest your folders deeply."
COM_ADMINTOOLS_JCONFIG_FEBENABLE_LABEL="Enable frontend scheduling"
COM_ADMINTOOLS_JCONFIG_FEBENABLE_DESC="When enabled it allows you to the PHP File Change Scanner without logging in to the backend."
COM_ADMINTOOLS_JCONFIG_SECRETWORD_LABEL="Secret word"
COM_ADMINTOOLS_JCONFIG_SECRETWORD_DESC="Protects the frontend scheduling feature from DoS attacks by requiring you to pass this secret word in the frontend scheduling URL. Please use long, complex passwords. Consult the documentation for more information."
COM_ADMINTOOLS_JCONFIG_EMAILTIMEZONE_LABEL="Timezone for emails"
COM_ADMINTOOLS_JCONFIG_EMAILTIMEZONE_DESC="All dates and times in the emails sent by Admin Tools to warn you about potential security issues will be expressed in the selected timezone. Default: GMT"
COM_ADMINTOOLS_JCONFIG_EMAILTIMEZONE_DEFAULT="Server Timezone"
COM_ADMINTOOLS_JCONFIG_DIRECTORYFILTERS_LABEL="Excluded Folders"
COM_ADMINTOOLS_JCONFIG_DIRECTORYFILTERS_DESC="Folders to skip when scanning your site.<br/><br/>Folders are given relative to your site's root. Enter one folder per line.<br/><br/>Default: nothing<br/><br/><em>Note</em>: Some folders are automatically excluded without adding them here: your site's log and temporary directory, the frontend and backend cache directories, as well as folders named tmp, log or logs in the frontend or backend of your site. Finally, symbolic links to folders outside of your site's root are not followed (their contents will not be scanned)."
COM_ADMINTOOLS_JCONFIG_FILEFILTERS_LABEL="Excluded Files"
COM_ADMINTOOLS_JCONFIG_FILEFILTERS_DESC="Files to skip when scanning your site.<br/><br/>Files are given relative to your site's root. Enter one file path per line.<br/><br/>Default: nothing<br/><br/>Only use to exclude files which are not really executable, e.g. logs with a .php extension outside Joomla's log folder. DO NOT use to mark safe files; use the Mark As Safe feature in the scan report page instead."
COM_ADMINTOOLS_JCONFIG_SCANEXTENSIONS_LABEL="Extensions to scan"
COM_ADMINTOOLS_JCONFIG_SCANEXTENSIONS_DESC="A comma-separated list of file extensions to scan, without the leading dot.<br/><br/>Default value: php, phps, phtml, php3, inc<br/><br/>Please remember that the PHP File Change Scanner is only designed to reliably scan and evaluate a Threat Score of PHP files. We strongly advise you against adding extensions of source code files of different programming languages, such as JavaScript and Perl, or binary files. If you do not heed this warning you might get a lot of false positives or, worse, false negatives in files which do not contain PHP programming language source code."
COM_ADMINTOOLS_JCONFIG_DOUBLEEXTENSIONS_LABEL="Scan files with double extensions"
COM_ADMINTOOLS_JCONFIG_DOUBLEEXTENSIONS_DESC="Scan files where the extensions to scan appear before other extensions. For example, if you've added <code>php</code> to “Extensions to scan” and enable this option here, the PHP File Change Scanner will scan both <code>example.php</code> and <code>example.php.png</code>."
COM_ADMINTOOLS_JCONFIG_CASEINSENSITIVEEXTENSIONS_LABEL="Case-insensitive extension match"
COM_ADMINTOOLS_JCONFIG_CASEINSENSITIVEEXTENSIONS_DESC="Makes the file extension matching case-insensitive. For example, if you've added <code>php</code> to “Extensions to scan” and enable this option here, the PHP File Change Scanner will scan both <code>example.php</code> and <code>example.PHP</code>"
COM_ADMINTOOLS_JCONFIG_LARGEFILETHRESHOLD_LABEL="Large file threshold"
COM_ADMINTOOLS_JCONFIG_LARGEFILETHRESHOLD_DESC="The PHP File Change Scanner will deliberately pause work and resume it in the next request before scanning files bigger than this many bytes. This prevents an accidental PHP timeout when scanning a big file in the tail end of the allotted Maximum Work Time.<br/><br/>Recommended value: 524288"
COM_ADMINTOOLS_JCONFIG_SCANDIFF_LABEL="Calculate diffs when scanning"
COM_ADMINTOOLS_JCONFIG_SCANDIFF_DESC="When this option is enabled, Admin Tools will calculate a diff (compact form of file differences) for each modified file detected by the PHP File Scanner feature. WARNING: This consumes A LOT of database space, about 20-40Mb for a typical site!"
COM_ADMINTOOLS_JCONFIG_SCANIGNORENONTHREATS_LABEL="Do not report files with a zero Threat Score"
COM_ADMINTOOLS_JCONFIG_SCANIGNORENONTHREATS_DESC="When enabled, any new or modified file with a zero Threat Score will not be reported.<br/><br/>Recommended value: No<br/><br/><strong>WARNING</strong>: We do NOT recommend enabling this option. It is conceivable that maliciously modified files may have a zero Threat Score because their malicious payload is written in a way that is impossible for an automated scanner to distinguish from legitimate, if a bit messy, code. Enabling this option will not alert you of these files, possibly putting your site at risk. This option is here for debugging issues with the Threat Score calculation, NOT as something you should enable on production sites."
COM_ADMINTOOLS_JCONFIG_OVERSIZEFILETHRESHOLD_LABEL="Oversize file threshold"
COM_ADMINTOOLS_JCONFIG_OVERSIZEFILETHRESHOLD_DESC="Files bigger than this many bytes will not have their Threat Score evaluated.<br/><br/>Recommended value: 5242880<br/><br/>A value too small would cause executable files to not be scanned for malicious code which could be a security concern. Setting this too high will probably result in a PHP timeout when scanning a very big file, typically one that's not even executable despite the .php extension (e.g. a log file)."
COM_ADMINTOOLS_JCONFIG_SCANEMAIL_DESC="The scan results will be automatically sent to this email address. If you leave it blank no email will be sent."
COM_ADMINTOOLS_JCONFIG_SCANEMAIL_LABEL="Send results to this email"
COM_ADMINTOOLS_JCONFIG_SCAN_CONDITIONAL_EMAIL_LABEL="Email only on actionable items"
COM_ADMINTOOLS_JCONFIG_SCAN_CONDITIONAL_EMAIL_DESC="When enabled (default) the PHP File Change Scanner will send you an email with the scan results summary <em>only</em> when actionable items (added, modified or suspicious files) are detected."

;; Email sending
COM_ADMINTOOLS_JCONFIG_EMAIL_LABEL="Email Sending"
COM_ADMINTOOLS_JCONFIG_EMAIL_DESC="Options which control how Admin Tools sends emails for blocked requests. These options only apply in the Professional edition."
COM_ADMINTOOLS_JCONFIG_THROTTLE_LABEL="Blocked request email throttling"
COM_ADMINTOOLS_JCONFIG_THROTTLE_DESC="When enabled, Admin Tools will only send up to a certain number of emails over a specific of time. This protects your email from getting flooded when your site is under attack. You need to have blocked request logging enabled for <em>all blocking reasons</em> you are sending emails for. Furthermore, the maximum number of log entries you keep — per the system plugin's configuration – must be <em>equal to or higher</em> then the maximum number of emails configured below. In any other case your security exception emails will NOT be throttled."
COM_ADMINTOOLS_JCONFIG_EMAIL_NUM_LABEL="Maximum number of blocked requests to send emails for"
COM_ADMINTOOLS_JCONFIG_EMAIL_NUM_DESC="The maximum number of blocked requests for which emails may be sent within the period of time defined below. Keep in mind that during a sustained attack more emails than this may be sent depending on how slow your web, database and mail servers respond when your site is under very heavy load. Furthermore, keep in mind that this only affects the blocked requests logged in the database and which with a block reason which is NOT in the configured reasons for which to never send emails."
COM_ADMINTOOLS_JCONFIG_EMAIL_NUMFREQ_LABEL="Period for email throttling"
COM_ADMINTOOLS_JCONFIG_EMAIL_NUMFREQ_DESC="Email throttling works by checking how many blocked requests have been logged in this many seconds, minutes, hours or days. You select the time unit of measurement below."
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_LABEL="Time unit of measurement"
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_DESC="The period above is expressed in the time unit of measurement selected here. Please note that for the purpose of these calculations one minute is 60 seconds, 1 hour is 3600 seconds, 1 day is 86400 seconds. This many be different than wall clock minutes, hours and days on years with leap seconds and on the cusp between Daylight Savings and Standard Time (or vice versa). Timekeeping is a rather convoluted subject."
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_SECONDS="Seconds"
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_MINUTES="Minutes"
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_HOURS="Hours"
COM_ADMINTOOLS_JCONFIG_EMAIL_FREQ_DAYS="Days"

;; Backend options
COM_ADMINTOOLS_JCONFIG_BACKEND_LABEL="Backend"
COM_ADMINTOOLS_JCONFIG_BACKEND_DESC="Options which define how the backend of the component works"
COM_ADMINTOOLS_JCONFIG_SHOWSTATS_LABEL="Show graphs and statistics"
COM_ADMINTOOLS_JCONFIG_SHOWSTATS_DESC="Display graphs and statistics about blocked requests (Professional release only)"
COM_ADMINTOOLS_JCONFIG_REORDERPLUGIN_LABEL="Automatically reorder the plugin"
COM_ADMINTOOLS_JCONFIG_REORDERPLUGIN_DESC="The System - Admin Tools plugin needs to be ordered as the first published plugin to work correctly. When you visit Admin Tools in the backend the plugin is automatically reordered to be the first one. In some rare cases other plugins need to be published first, for example alternative mail handlers such as CMandrill. In this case set this option to No. MAJOR DANGER! IT WILL BE SOLELY UP TO YOU TO REORDER THE PLUGIN. IF A VULNERABLE PLUGIN IS PUBLISHED BEFORE THE SYSTEM - ADMIN TOOLS PLUGIN YOUR SITE CAN BE HACKED. ADMIN TOOLS WILL BE UNABLE TO PROTECT YOU IN THIS CASE SINCE IT WILL NOT BE RUNNING BEFORE THE VULNERABLE CODE, THEREFORE UNABLE TO DETECT THE ATTACK. DO NOT SET THIS OPTION TO “NO” UNLESS YOU ARE AN EXPERT AND UNDERSTAND THE IMPLICATIONS."
COM_ADMINTOOLS_JCONFIG_SERVERCONFIGWARN_LABEL="Warn about manual edits on server configuration files"
COM_ADMINTOOLS_JCONFIG_SERVERCONFIGWARN_DESC="Admin Tools will check if you manually edited a server configuration file (ie .htaccess, nginx.conf or web.config) instead of using the Htaccess, NginX or WebConfig Maker"
COM_ADMINTOOLS_JCONFIG_USAGESTATS_LABEL="Enable anonymous PHP, MySQL and Joomla! version reporting"
COM_ADMINTOOLS_JCONFIG_USAGESTATS_DESC="Help us improve our software by anonymously and automatically reporting your PHP, MySQL and Joomla! versions. This information will help us decide which versions of Joomla!, PHP and MySQL to support in future versions. Note: we do NOT collect your site name, IP address or any other directly or indirectly unique identifying information."

;; Permissions
COM_ADMINTOOLS_ACL_PERMISSION_UTILS_DESC="Allow access to utility features"
COM_ADMINTOOLS_ACL_PERMISSION_UTILS_TITLE="Utility"
COM_ADMINTOOLS_ACL_PERMISSION_SECURITY_TITLE="Security"
COM_ADMINTOOLS_ACL_PERMISSION_SECURITY_DESC="Allow access to security features"
COM_ADMINTOOLS_ACL_PERMISSION_MAINTENANCE_TITLE="Maintenance"
COM_ADMINTOOLS_ACL_PERMISSION_MAINTENANCE_DESC="Allow access to database and permissions maintenance"

[email_templates]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Email templates
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_MAIL_TROUBLESHOOTING_TITLE="Admin Tools: Troubleshooting email"
COM_ADMINTOOLS_MAIL_TROUBLESHOOTING_DESC="Sent whenever you make a change in Admin Tools configuration which could lock you out of your site."
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_SUBJECT="Admin Tools troubleshooting information"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_BODY="Hello {USER},\n\nYou just {ACTION} using the Admin Tools component on your site “{SITENAME}”. This is a generally safe process. In some cases a misunderstanding, an oversight, or a browser or server mangling your settings may result in your site not working properly or becoming inaccessible. This applies to both Joomla itself and its various third party extensions. In this unlikely event please consult the following URLs for troubleshooting instructions:\n\n{TROUBLESHOOTING_URLS}\n\nIf you can not find a solution by yourself and you have an active subscription for Admin Tools please file a support ticket on our site, https://www.akeeba.com and tell us what you did before the issue occurred, what is the issue and which troubleshooting steps you have already tried.\n\nWho sent this email?\n======================================================================\n\nThis email is sent automatically by Admin Tools running on your site to the email address on record on your Joomla user profile every time you take an administrative action which could accidentally lock you out of your site. It is not sent to any other users of your site.\n\nIf you no longer wish to receive these emails please log into your site's administrator backend and go to Components, Admin Tools, Web Application Firewall, Configure WAF and click on the Customisation tab. Find the “Send troubleshooting email on administrative functions” and set it to No."
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_BODY_HTML="<p>Hello {USER},</p><p>You just {ACTION} using the Admin Tools component on your site “{SITENAME}”. This is a generally safe process. In some cases a misunderstanding, an oversight, or a browser or server mangling your settings may result in your site not working properly or becoming inaccessible. This applies to both Joomla itself and its various third party extensions. In this unlikely event please consult the following URLs for troubleshooting instructions:</p>{TROUBLESHOOTING_URLS_HTML}<p>If you can not find a solution by yourself and you have an active subscription for Admin Tools please file a support ticket on our site, https://www.akeeba.com and tell us what you did before the issue occurred, what is the issue and which troubleshooting steps you have already tried.</p><h3>Who sent this email?</h3><p>This email is sent automatically by Admin Tools running on your site to the email address on record on your Joomla user profile every time you take an administrative action which could accidentally lock you out of your site. It is not sent to any other users of your site.</p><p>If you no longer wish to receive these emails please log into your site's administrator backend and go to Components, Admin Tools, Web Application Firewall, Configure WAF and click on the Customisation tab. Find the “Send troubleshooting email on administrative functions” and set it to No.</p>"

COM_ADMINTOOLS_MAIL_CONFIGMONITOR_TITLE="Admin Tools: Configuration Monitoring"
COM_ADMINTOOLS_MAIL_CONFIGMONITOR_DESC="Sent by Admin Tools whenever you make a change in your Global Configuration or a component's configuration options when the “Monitor Global Configuration” and/or “Monitor component configuration” options are enabled in the Web Application Firewall."
COM_ADMINTOOLS_EMAIL_CONFIGMONITOR_SUBJECT="Configuration options for {AREA} modified on {SITENAME}"
COM_ADMINTOOLS_EMAIL_CONFIGMONITOR_BODY="Hello,\n\nWe would like to notify you that the configuration options for {AREA} on your site, {SITENAME}, have been modified by user {USER}. More details about the origin of this change as follows:\n\n\n\nIP Address: {IP} (IP Lookup: {LOOKUP})\nUser Agent: {UA}\n\nIf this change was not made by you or an administrator user you trust please review your site immediately as this would be an indication of hacking activity.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_CONFIGMONITOR_BODY_HTML="<p>Hello,</p><p>We would like to notify you that the configuration options for {AREA} on your site, {SITENAME}, have been modified by user {USER}. More details about the origin of this change as follows:</p><ul><li>IP Address: {IP} (<a href=\"{LOOKUP}\">IP Lookup</a>)</li><li>User Agent: {UA}</li></ul><p>If this change was not made by you or an administrator user you trust please review your site immediately as this would be an indication of hacking activity.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_USERREACTIVATE_TITLE="Admin Tools: User re-activation"
COM_ADMINTOOLS_MAIL_USERREACTIVATE_DESC="Sent by Admin Tools whenever a user account is temporarily deactivated due to too many failed logins."
COM_ADMINTOOLS_EMAIL_USER_REACTIVATE_SUBJECT="User account temporarily blocked on {SITENAME}"
COM_ADMINTOOLS_EMAIL_USER_REACTIVATE_BODY="Hello,\n\nWe have detected several failed attempts to log in with user account {USER} on our site {SITENAME}. As a result, our system has automatically put a temporary block on the user account on {DATE}.\n\nIf you believe that you are getting this message in error, i.e. it was you who accidentally tried logging in with the wrong password, please click on the following link to lift the temporary block from your user account again:\n{ACTIVATE}\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you have a user account in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_USER_REACTIVATE_BODY_HTML="<p>Hello,</p><p>We have detected several failed attempts to log in with user account {USER} on our site {SITENAME}. As a result, our system has automatically put a temporary block on the user account on {DATE}.</p><p>If you believe that you are getting this message in error, i.e. it was you who accidentally tried logging in with the wrong password, please click on the following link to lift the temporary block from your user account again:</p><p><a href=\"{ACTIVATE}\">{ACTIVATE}</a></p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>Note: You are receiving this automatic email message because you have a user account in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_ADMINLOGINFAIL_TITLE="Admin Tools: Failed administrator login"
COM_ADMINTOOLS_MAIL_ADMINLOGINFAIL_DESC="Sent by Admin Tools when a failed backend login attempt occurs, as long as the respective feature is enabled."
COM_ADMINTOOLS_EMAIL_ADMINLOGINFAIL_SUBJECT="Failed administrator login for user {USER} on {SITENAME}"
COM_ADMINTOOLS_EMAIL_ADMINLOGINFAIL_BODY="Hello,\n\nWe would like to notify you that user {USER} did not log in successfully to the administrator back-end area of your site, {SITENAME}. Further information:\n\nUsername: {USER}\nIP address: {IP} ({LOOKUP})\nBrowser User Agent string: {UA}\n\nIf this is expected you do not need to do anything about it. If you suspect a hacking attempt, please log in to your site's back-end immediately and activate Admin Tools' Emergency Off-Line mode at once.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_ADMINLOGINFAIL_BODY_HTML="<p>Hello,</p><p>We would like to notify you that user <strong>{USER}</strong> did <strong>not</strong> log in successfully to the administrator back-end area of your site, {SITENAME}. Further information:</p><p>Username: {USER}<br />IP address: {IP} (<a href=\"{LOOKUP}\">IP Lookup</a>)<br />Browser User Agent string: {UA}</p><p>If this is expected you do not need to do anything about it. If you suspect a hacking attempt, please log in to your site's back-end immediately and activate Admin Tools' Emergency Off-Line mode at once.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_ADMINLOGINSUCCESS_TITLE="Admin Tools: Successful administrator login"
COM_ADMINTOOLS_MAIL_ADMINLOGINSUCCESS_DESC="Sent by Admin Tools when a successful backend login attempt occurs, as long as the respective feature is enabled."
COM_ADMINTOOLS_EMAIL_ADMINLOGINSUCCESS_SUBJECT="User {USER} logged into the administrator area of {SITENAME}"
COM_ADMINTOOLS_EMAIL_ADMINLOGINSUCCESS_BODY="Hello,\n\nWe would like to notify you that user {USER} has just logged into the administrator backend area of your site, {SITENAME}. Further information:\n\nUsername: {USER}\nIP address: {IP} ({LOOKUP})\nBrowser User Agent string: {UA}\n\nIf this is expected you do not need to do anything about it. If you suspect a hacking attempt, please log in to your site's back-end immediately and activate Admin Tools' Emergency Off-Line mode at once.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_ADMINLOGINSUCCESS_BODY_HTML="<p>Hello,</p><p>We would like to notify you that user <strong>{USER}</strong> has just logged into the administrator backend area of your site, {SITENAME}. Further information:</p><p>Username: {USER}<br />IP address: {IP} (<a href=\"{LOOKUP}\">IP Lookup</a>)<br />Browser User Agent string: {UA}</p><p>If this is expected you do not need to do anything about it. If you suspect a hacking attempt, please log in to your site's back-end immediately and activate Admin Tools' Emergency Off-Line mode at once.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_IPAUTOBAN_TITLE="Admin Tools: Automatic IP blocking"
COM_ADMINTOOLS_MAIL_IPAUTOBAN_DESC="Sent by Admin Tools when an IP address is automatically blocked, as long as one or more email addresses have been selected for this feature. This also includes the Rescue Mode instructions; we recommend you "
COM_ADMINTOOLS_EMAIL_IPAUTOBAN_SUBJECT="Automatic IP blocking notification for {IP} on {SITENAME}"
COM_ADMINTOOLS_EMAIL_IPAUTOBAN_BODY="Hello,\n\nWe would like to notify you that the IP address {IP} will be temporarily blocked from accessing your site, {SITENAME}. Please find additional details below.\n\nIP Address: {IP} (IP Lookup: {LOOKUP})\nLast Blocked Request Reason: {REASON}\nBlocked until: {UNTIL}\n\n{RESCUEINFO}\n\nBest regards,\n\nThe {SITENAME} team\n\nYou are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_IPAUTOBAN_BODY_HTML="<p>Hello,</p><p>We would like to notify you that the IP address {IP} will be temporarily blocked from accessing your site, {SITENAME}. Please find additional details below.</p><p>IP Address: {IP} (<a href=\"{LOOKUP}\">IP Lookup</a>)<br />Last Blocked Request Reason: {REASON}<br />Blocked until: {UNTIL}</p><p>{RESCUEINFO}</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_CRITICALFILES_TITLE="Admin Tools: Critical file modified"
COM_ADMINTOOLS_MAIL_CRITICALFILES_DESC="Sent by Admin Tools when a “critical file” has been modified."
COM_ADMINTOOLS_EMAIL_CRITICALFILES_SUBJECT="Critical file modified on {SITENAME}"
COM_ADMINTOOLS_EMAIL_CRITICALFILES_BODY="Hello,\n\nWe would like to notify you that one or more critical files have been modified on your site, {SITENAME}. The list of files modified on your site is as follows:\n\n{INFO}\n\nShould I be worried?\n======================================================================\n\n“Critical files”, in the context of this email message, are the files most usually targeted by hackers upon successful hacking of a site. These files can also be and most frequently are modified for legitimate reasons. For example, they will be modified when you save your site's Global Configuration or when you update Joomla! or one of its templates.\n\nYou should NOT worry if you received this email after you, or another administrator you trust, performed any of the following changes on your site:\n\n* Restored the site's files and/or database contents from a backup\n* Modified the Global Configuration\n* Updated Joomla!\n* Updated a site template\n\nIf this message was NOT sent to you as the result of such a desirable and expected change please review your site immediately as this would be an indication of hacking activity; or an extension or other third party software doing something you were not aware of and which could have adverse impact to your site.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_CRITICALFILES_BODY_HTML="<p>Hello,</p><p>We would like to notify you that one or more critical files have been modified on your site, {SITENAME}. The list of files modified on your site is as follows:</p>{INFO_HTML}<h3>Should I be worried?</h3><p>“Critical files”, in the context of this email message, are the files most usually targeted by hackers upon successful hacking of a site. These files can also be <em>and most frequently are</em> modified for legitimate reasons. For example, they will be modified when you save your site's Global Configuration or when you update Joomla! or one of its templates.</p><p>You should NOT worry if you received this email after you, or another administrator you trust, performed any of the following changes on your site:</p><ul><li>Restored the site's files and/or database contents from a backup</li><li>Modified the Global Configuration</li><li>Updated Joomla!</li><li>Updated a site template</li></ul><p>If this message was NOT sent to you as the result of such a desirable and expected change please review your site immediately as this would be an indication of hacking activity; or an extension or other third party software doing something you were not aware of and which could have adverse impact to your site.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_CRITICALFILES_GLOBAL_TITLE="Admin Tools: Monitored file changed"
COM_ADMINTOOLS_MAIL_CRITICALFILES_GLOBAL_DESC="Sent by Admin Tools when one or more files you chose to monitor for changes have been modified."
COM_ADMINTOOLS_EMAIL_CRITICALFILES_GLOBAL_SUBJECT="Monitored files changed on {SITENAME}"
COM_ADMINTOOLS_EMAIL_CRITICALFILES_GLOBAL_BODY="Hello,\n\nWe would like to notify you that one or more files you asked Admin Tools to monitor for changes have been modified on your site, {SITENAME}. The list of files modified on your site is as follows:\n\n{INFO}\n\nIf this message was not sent to you as the result of such a desirable and expected change please review your site immediately as this would be an indication of hacking activity.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_CRITICALFILES_GLOBAL_BODY_HTML="<p>Hello,</p><p>We would like to notify you that one or more files you asked Admin Tools to monitor for changes have been modified on your site, {SITENAME}. The list of files modified on your site is as follows:</p>{INFO_HTML}<p>If this message was not sent to you as the result of such a desirable and expected change please review your site immediately as this would be an indication of hacking activity.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_SUPERUSERSLIST_TITLE="Admin Tools: Super Users added"
COM_ADMINTOOLS_MAIL_SUPERUSERSLIST_DESC="Sent by Admin Tools when a Super User has been created and the Monitor Super User accounts feature is enabled."
COM_ADMINTOOLS_EMAIL_SUPERUSERSLIST_SUBJECT="Super Users were added to {SITENAME}"
COM_ADMINTOOLS_EMAIL_SUPERUSERSLIST_BODY="Hello,\n\nWe would like to notify you that we detected the suspicious addition of one or more Super User accounts to your site, {SITENAME}. These new Super User accounts do not seem to have been created through the regular means, i.e. Joomla's “Users” page. Therefore they have been blocked. The new Super User accounts detected and blocked are:\n\n{INFO}\n\nDo I need to worry?\n======================================================================\n\nSuper User accounts have full access to your site. They can modify all content, without any restriction. They can also install software which can access or modify every aspect of your site, including arbitrary files, database content and configuration settings. Only grant Super User access to people you trust.\n\nIf you are receiving this email it means that these Super User accounts were created outside Joomla's “Users” page. Typically this means that a hacker found a way to bypass your site's or your server's security and tried to surreptitiously create Super User accounts for themselves. For this reason these accounts were blocked, i.e. they cannot be used to log into your site.\n\nIt is possible, however, that you do receive this email in error: if you or another Super User did intend to create these Super User accounts and used a third party tool to do that. If this is the case then do not worry. Just log in to your site's administrator backend with your own Super User account, go to the Users page, edit the users listed further above in this email and unblock them.\n\nIf you or another Super User did NOT intend to create these Super Users we recommend auditing your site and your server for any other signs of anomalous activity.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_SUPERUSERSLIST_BODY_HTML="<p>Hello,</p><p>We would like to notify you that we detected the suspicious addition of one or more Super User accounts to your site, {SITENAME}. These new Super User accounts do not seem to have been created through the regular means, i.e. Joomla's “Users” page. Therefore they have been blocked. The new Super User accounts detected <strong>and blocked</strong> are:</p>{INFO_HTML}<h3>Do I need to worry?</h3><p>Super User accounts have full access to your site. They can modify all content, without any restriction. They can also install software which can access or modify every aspect of your site, including arbitrary files, database content and configuration settings. Only grant Super User access to people you trust.</p><p>If you are receiving this email it means that these Super User accounts were created outside Joomla's “Users” page. Typically this means that a hacker found a way to bypass your site's or your server's security and tried to surreptitiously create Super User accounts for themselves. For this reason these accounts were blocked, i.e. they cannot be used to log into your site.</p><p>It is possible, however, that you do receive this email in error: if you or another Super User did intend to create these Super User accounts and used a third party tool to do that. If this is the case then do not worry. Just log in to your site's administrator backend with your own Super User account, go to the Users page, edit the users listed further above in this email and unblock them.</p><p>If you or another Super User did NOT intend to create these Super Users we recommend auditing your site and your server for any other signs of anomalous activity.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

COM_ADMINTOOLS_MAIL_RESCUEURL_TITLE="Admin Tools: Rescue URL"
COM_ADMINTOOLS_MAIL_RESCUEURL_DESC="Sent by Admin Tools when a backend user requests a Rescue URL to regain access to the site."
COM_ADMINTOOLS_EMAIL_RESCUEURL_SUBJECT="Rescue URL requested on {SITENAME} for {USER}"
COM_ADMINTOOLS_EMAIL_RESCUEURL_BODY="Hello,\n\nWe would like to notify you that user {USER} has requested a Rescue URL for your site, {SITENAME}. If you made that request yourself please click on the following link, or copy and paste the URL to your browser. This will let you log in to the administrator backend of your site where you can modify unblock yourself and / or change Admin Tools' configuration. The Rescue URL is:\n\n{RESCUEURL}\n\nThe information towards the end of this email lets you know what to do once you are logged into your site's backend.\n\nI have no idea why I'm receiving this email\n======================================================================\n\nLook under \"What is the Rescue URL\" further down. You DO NOT need to take any action and you DO NOT need to worry.\n\nWho requested the Rescue URL?\n======================================================================\n\nUsername: {USER}\nIP Address: {IP} (IP Lookup: {LOOKUP})\nUser Agent: {UA}\n\nWhat is the Rescue URL?\n======================================================================\n\nSometimes an overzealous Admin Tools configuration can result in accidentally blocking you, a Super User from the site. Normally that would require you to rename the file of Admin Tools' system plugin to unblock yourself. This is a bit complicated and susceptible to errors.\n\nThe Rescue URL feature works around that. By accessing a special URL when you are blocked out of the site you are sent this email. The URL in this email is only valid for the same browser and IP address that made the request and only for a limited amount of time. Accessing it will get you to a temporarily unblocked administrator login page. This lets you access the administrator backend of your site to unblock yourself and / or modify Admin Tools settings.\n\nBy default, this feature is enabled on all installations of Admin Tools. Moreover, a message about accessing the Rescue URL is displayed by default when someone gets blocked UNLESS you set up a \"Custom message\" in the Configure WAF page of Admin Tools. If you have no idea why you received this message it's probably because someone saw the default IP blocked message and guessed your Super User email correctly. Don't worry though, what they did is completely useless since they would also need access to your email account and your Super User password to access your site, i.e. they would need to have already hacked you. As it's already documented, we strongly recommend that you change the \"Custom message\" to make it less obvious that your site is protected by Admin Tools. If you do not wish to use the Rescue URL feature -and are OK manually renaming files per the documentation when you get blocked- go to Extensions, Plugins and edit the options of the Admin Tools system plugin. You'll see an option for Rescue URL. Set it to No to disable this feature.\n\nWhat to do after logging in?\n======================================================================\n\nIf your IP is blocked by Admin Tools go to Components, Admin Tools and click the big Unblock My IP button at the top of the page.\n\nIf you keep getting your IP blocked without you doing anything suspicious to the best of your knowledge, the IP blocked is always the same but different than the one reported by http://www.ip-adress.eu/ and https://www.whatismyip.com/ then your site might be behind a CDN or a reverse proxy. In this case, additionally to the instructions above, please go to System, Global Configuration. Set the \"Behind Load Balancer\" option to Yes and save.\n\nIf, however, your real IP address as reported by the two tool listed above keeps getting banned you should troubleshoot the reason of the ban. Go to Components, Admin Tools, Web Application Firewall, Security Exceptions Log and check the Reason and Target URL for the entries which have your IP address in the IP address field. If you are not sure what that means, please file a support ticket remembering to copy the information from the Security Exceptions Log. Kindly note that you need to have an active subscription to receive support.\n\nIf you have forgotten your Administrator Secret URL parameter go to Components, Admin Tools, Web Application Firewall, Configure WAF, click on the Basic Protection Features tab and find the \"Administrator secret URL parameter\" option. Change or remove all of the text in that box to reset or unset, respectively, this feature.\n\nWhat to do if I still cannot log in to my site?\n======================================================================\n\nThere are two cases where the Rescue URL feature, or renaming the Admin Tools system plugin's file, will not help you. These are the two cases where Admin Tools has created a server configuration file, meaning that you are blocked by your server, not Admin Tools.\n\nThe first is the Administrator password protection feature. Please delete the files named .htaccess and .htpasswd from your site's administrator directory.\n\nThe other case is when you've used the .htaccess Maker feature of Admin Tools. In this case there's a .htaccess file in your site's root. You may want to replace its contents with the default Joomla! .htaccess file content.\n\nIn both cases you should not that the files have names beginning with a dot. That makes them hidden. You will need to enable the display of hidden files to edit / delete those files. If you are unsure how to do that please ask your host and tell them that you need to edit/delete hidden files. Usually they will point out an option in their hosting control panel's file manager.\n\nIn any other case your issue is unrelated to Admin Tools. Do you have another security plugin on your site? If you do, check its settings. If not, check with your host. More often than not hosts have their own server security systems which can block you out of your site."
COM_ADMINTOOLS_EMAIL_RESCUEURL_BODY_HTML="<p>Hello,</p><p>We would like to notify you that user {USER} has requested a Rescue URL for your site, {SITENAME}. If you made that request yourself please click on the following link, or copy and paste the URL to your browser. This will let you log in to the administrator backend of your site where you can modify unblock yourself and / or change Admin Tools' configuration. The Rescue URL is:</p><p><a href=\"{RESCUEURL}\" rel=\"alternate\">{RESCUEURL}</a></p><p>The information towards the end of this email lets you know what to do once you are logged into your site's backend.</p><h3>I have no idea why I'm receiving this email</h3><p>Look under \"What is the Rescue URL\" further down. You <strong>DO NOT</strong> need to take any action and you <strong>DO NOT</strong> need to worry.</p><h3>Who requested the Rescue URL?</h3><p>Username: {USER}<br />IP Address: {IP} (<a href=\"{LOOKUP}\">IP Lookup</a>)<br />User Agent: {UA}</p><h3>What is the Rescue URL?</h3><p>Sometimes an overzealous Admin Tools configuration can result in accidentally blocking you, a Super User from the site. Normally that would require you to rename the file of Admin Tools' system plugin to unblock yourself. This is a bit complicated and susceptible to errors.</p><p>The Rescue URL feature works around that. By accessing a special URL when you are blocked out of the site you are sent this email. The URL in this email is only valid for the same browser and IP address that made the request and only for a limited amount of time. Accessing it will get you to a <em>temporarily</em> unblocked administrator login page. This lets you access the administrator backend of your site to unblock yourself and / or modify Admin Tools settings.</p><p>By default, this feature is enabled on all installations of Admin Tools. Moreover, a message about accessing the Rescue URL is displayed by default when someone gets blocked UNLESS you set up a \"Custom message\" in the Configure WAF page of Admin Tools. If you have no idea why you received this message it's probably because someone saw the default IP blocked message and guessed your Super User email correctly. Don't worry though, what they did is completely useless since they would also need access to your email account and your Super User password to access your site, i.e. they would need to have already hacked you. As it's already documented, we strongly recommend that you change the \"Custom message\" to make it less obvious that your site is protected by Admin Tools. If you do not wish to use the Rescue URL feature -and are OK manually renaming files per the documentation when you get blocked- go to Extensions, Plugins and edit the options of the Admin Tools system plugin. You'll see an option for Rescue URL. Set it to No to disable this feature.</p><h3>What to do after logging in?</h3><p>If your IP is blocked by Admin Tools go to Components, Admin Tools and click the big Unblock My IP button at the top of the page.</p><p>If you keep getting your IP blocked without you doing anything suspicious to the best of your knowledge, the IP blocked is always the same but different than the one reported by <a href=\"http://www.ip-adress.eu/\">http://www.ip-adress.eu/ </a><em>and</em> <a href=\"https://www.whatismyip.com/\">https://www.whatismyip.com/</a> then your site might be behind a CDN or a reverse proxy. In this case, additionally to the instructions above, please go to System, Global Configuration. Set the \"Behind Load Balancer\" option to Yes and save.</p><p>If, however, your real IP address as reported by the two tool listed above keeps getting banned you should troubleshoot the reason of the ban. Go to Components, Admin Tools, Web Application Firewall, Security Exceptions Log and check the Reason and Target URL for the entries which have your IP address in the IP address field. If you are not sure what that means, please <a href=\"https://www.akeeba.com/support/admin-tools.html\" rel=\"alternate\">file a support ticket</a> remembering to copy the information from the Security Exceptions Log. Kindly note that you need to have an active subscription to receive support.</p><p>If you have forgotten your Administrator Secret URL parameter go to Components, Admin Tools, Web Application Firewall, Configure WAF, click on the Basic Protection Features tab and find the \"Administrator secret URL parameter\" option. Change or remove all of the text in that box to reset or unset, respectively, this feature.</p><h3>What to do if I still cannot log in to my site?</h3><p>There are two cases where the Rescue URL feature, or renaming the Admin Tools system plugin's file, will not help you. These are the two cases where Admin Tools has created a <em>server</em> configuration file, meaning that you are blocked by <em>your server</em>, not Admin Tools.</p><p>The first is the <strong>Administrator password protection</strong> feature. Please delete the files named <code>.htaccess</code> and <code>.htpasswd</code> from your site's <code>administrator</code> directory. </p><p>The other case is when you've used the <strong>.htaccess Maker</strong> feature of Admin Tools. In this case there's a <code>.htaccess</code> file in your site's root. You may want to replace its contents with the <a href=\"https://raw.githubusercontent.com/joomla/joomla-cms/staging/htaccess.txt\" rel=\"alternate\">default Joomla! .htaccess file content</a>.</p><p>In both cases you should not that the files have names beginning with a dot. That makes them <em>hidden</em>. You will need to enable the display of hidden files to edit / delete those files. If you are unsure how to do that please ask your host and tell them that you need to edit/delete <em>hidden</em> files. Usually they will point out an option in their hosting control panel's file manager. </p><p>In any other case your issue is unrelated to Admin Tools. Do you have another security plugin on your site? If you do, check its settings. If not, check with your host. More often than not hosts have their own server security systems which can block you out of your site.</p>"

COM_ADMINTOOLS_MAIL_BLOCKEDREQUEST_TITLE="Admin Tools: Blocked request"
COM_ADMINTOOLS_MAIL_BLOCKEDREQUEST_DESC="Sent by Admin Tools when a request is blocked by its Web Application Firewall."
COM_ADMINTOOLS_EMAIL_BLOCKEDREQUEST_SUBJECT="Blocked request on {SITENAME}"
COM_ADMINTOOLS_EMAIL_BLOCKEDREQUEST_BODY="Hello,\n\nWe would like to notify you that a security exception was detected on your site, {SITENAME}, with the following details:\n\nIP Address: {IP} (IP Lookup: {LOOKUP})\nReason: {REASON}\n\nIf this kind of security exception repeats itself, please log in to your site's back-end and add this IP address to your Admin Tools's Web Application Firewall feature in order to completely block the misbehaving user.\n\nBest regards,\n\nThe {SITENAME} team\n\nNote: You are receiving this automatic email message because you are an administrator in {SITENAME}. Do not reply to this email, it's sent from an unmonitored email address."
COM_ADMINTOOLS_EMAIL_BLOCKEDREQUEST_BODY_HTML="<p>Hello,</p><p>We would like to notify you that a security exception was detected on your site, {SITENAME}, with the following details:</p><p>IP Address: {IP} (<a href="{LOOKUP}">IP Lookup</a>)<br />Reason: {REASON}</p><p>If this kind of security exception repeats itself, please log in to your site's back-end and add this IP address to your Admin Tools's Web Application Firewall feature in order to completely block the misbehaving user.</p><p>Best regards,</p><p>The {SITENAME} team</p><p><small>You are receiving this automatic email message because you are an administrator in <em>{SITENAME}</em>. Do not reply to this email, it's sent from an unmonitored email address.</small></p>"

[Emailtemplates]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Email templates control panel
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_EMAILTEMPLATES="Email Templates"

COM_ADMINTOOLS_EMAILTEMPLATES_LBL_WHERE_HEAD="Where are the Email Templates?"
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_WHERE_TEXT="Email templates for core and third party extensions, like Admin Tools, are centrally managed by Joomla itself in the System, Mail Templates page. Third party extensions, however, need to implement their own code to install and update the email templates. This is what this page does. If you want to customise the email templates please click the button below to go to Joomla's Mail Templates page."
COM_ADMINTOOLS_EMAILTEMPLATES_BTN_MAILTEMPLATES="Mail Templates"

COM_ADMINTOOLS_EMAILTEMPLATES_LBL_MANAGE_HEAD="Email Template management"
COM_ADMINTOOLS_EMAILTEMPLATES_BTN_UPDATE="Install or Update"
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_UPDATE="Installs new email templates for Admin Tools and updates existing ones if they've changed. The user-modified email templates for Admin Tools are left intact."
COM_ADMINTOOLS_EMAILTEMPLATES_BTN_RESET="Reset"
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_RESET="Resets the email templates. This removes all of the email templates for Admin Tools, <strong>including any user-modified email templates</strong>. Then it installs all of the Admin Tools email templates afresh. Only use this button if you think you've damaged something in your database. Otherwise use the Joomla Email Templates manager to reset each email's subject and body to the default using the buttons provided in Joomla's interface."

COM_ADMINTOOLS_EMAILTEMPLATES_ERR_NOUPDATE="No email templates were checked."
COM_ADMINTOOLS_EMAILTEMPLATES_ERR_RESET="No email templates were reset."

COM_ADMINTOOLS_EMAILTEMPLATES_LBL_N_UPDATED_1="One email template was checked."
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_N_UPDATED="%d email templates were checked"
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_N_RESET_1="One email template was reset."
COM_ADMINTOOLS_EMAILTEMPLATES_LBL_N_RESET="%d email templates were reset."

[troubleshooter_emails]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Troubleshooter emails
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Actions
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_ADMINPASSWORD="applied Administrator Password Protection"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_QUICKSTART="finished setting up Admin Tools using the Quick Setup Wizard"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_HTACCESSMAKER="created a new .htaccess file"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_WEBCONFIGMAKER="created a new web.config file"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_NGINXCONFMAKER="created a new NginX configuration file"
COM_ADMINTOOLS_EMAIL_TROUBLESHOOTING_ACTION_CONFIGUREWAF="saved the Admin Tools' Web Application Configuration"

[Controlpanel]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Control Panel
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_CONTROLPANEL="Control Panel"
COM_ADMINTOOLS_TITLE_DASHBOARD="Admin Tools"
COM_ADMINTOOLS_TITLE_DASHBOARD_CORE="Admin Tools Core"
COM_ADMINTOOLS_TITLE_DASHBOARD_PRO="Admin Tools Professional"

COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_BANNED="The secret word is a known bad password. Please do not dictionary words, movie / series names, the names of your loved ones or pets."
COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_TOOSHORT="The secret word is too short. Use a secret word at least 8 characters long."
COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_TOOSIMPLE="The secret word is too simple. Try using lower and upper case letters, numbers and punctuation."

COM_ADMINTOOLS_CONTROLPANEL_ERR_NOTAUTHORIZED="You are not authorized to use this feature. Please enter the Main Password to access this feature."
COM_ADMINTOOLS_CONTROLPANEL_ERR_INVALIDDOWNLOADID="Invalid Download ID format. Please follow our instructions to get your Download ID. Do not enter your username, e-mail address or password in this box."
COM_ADMINTOOLS_CONTROLPANEL_ERR_JCONFIG="Invalid Joomla Configuration settings detected"
COM_ADMINTOOLS_CONTROLPANEL_ERR_JCONFIG_INVALID_LOGDIR="Invalid or unwritable Joomla log directory. Please fix it inside Joomla Global Configuration before continuing using Admin Tools."
COM_ADMINTOOLS_CONTROLPANEL_ERR_JCONFIG_INVALID_TMPDIR="Invalid or unwritable Joomla temporary directory. Please fix it inside Joomla Global Configuration before continuing using Admin Tools."
COM_ADMINTOOLS_CONTROLPANEL_ERR_JCONFIG_LOGDIR_SITEROOT="Joomla log directory is the same as the site root. Please fix it inside Joomla Global Configuration before continuing using Admin Tools."
COM_ADMINTOOLS_CONTROLPANEL_ERR_JCONFIG_TMPDIR_SITEROOT="Joomla temporary directory is the same as the site root. Please fix it inside Joomla Global Configuration before continuing using Admin Tools."

COM_ADMINTOOLS_CONTROLPANEL_LBL_SECURITY="Security"
COM_ADMINTOOLS_CONTROLPANEL_LBL_TOOLS="Tools"
COM_ADMINTOOLS_CONTROLPANEL_LBL_INFORMATION = "Version Information"
COM_ADMINTOOLS_CONTROLPANEL_LBL_RELEASED_ON="Released on %s"
COM_ADMINTOOLS_CONTROLPANEL_LBL_SCHEDULING="Site maintenance scheduling (via plugin)"

COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_EXCEPTIONS="Blocked Requests Graph"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_EXCEPTSTATS="Blocked requests per type"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_FROMDATE="From"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_RELOADGRAPHS="Load graph"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS="Statistics"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_LAST7DAYS="Last 7 days"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_LASTMONTH="Last month"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_LASTYEAR="Last year"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_NODATA="There have been no blocked requests in the selected time period."
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_THISMONTH="This month"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_THISYEAR="This year"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_TODAY="Today"
COM_ADMINTOOLS_CONTROLPANEL_DASHBOARD_STATS_YESTERDAY="Yesterday"

COM_ADMINTOOLS_CONTROLPANEL_HEADER_QUICKSETUP="Quick Setup"
COM_ADMINTOOLS_CONTROLPANEL_HEADER_QUICKSETUP_HELP="You should only run the Quick Setup Wizard once, when you first install Admin Tools. If you run it again it will override all your settings! If you want to adjust the configuration use the other buttons above."

COM_ADMINTOOLS_CONTROLPANEL_LBL_IP_UNBLOCKED="IP successfully unblocked"
COM_ADMINTOOLS_CONTROLPANEL_LBL_UNBLOCK_ME="Unblock my IP"

COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_HEADER="The frontend PHP File Change Scanner features are disabled"
COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_INTRO="Your <em>Secret Word</em> is insecure and can be easily guessed. In order to protect your site Admin Tools has disabled access to frontend scheduling until you enter a secure Secret Word. The problem detected is:"
COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_WHATTODO_COMMON="Alternatively, click the button below to reset the secret word to the suggested value <code>%s</code> In either case you will need to update your CRON jobs with the new Secret Word."
COM_ADMINTOOLS_CONTROLPANEL_ERR_FESECRETWORD_WHATTODO_JOOMLA="Please click on Options, Frontend and enter a more complex secret word."
COM_ADMINTOOLS_CONTROLPANEL_BTN_FESECRETWORD_RESET="Apply the suggested Secret Word"

COM_ADMINTOOLS_CONTROLPANEL_LBL_DISCLAIMER="DISCLAIMER"
COM_ADMINTOOLS_CONTROLPANEL_LBL_DISTEXT="Security-related components, like Admin Tools, are not designed to offer 100% protection of your site against any attack imaginable. They can and do help you improve the security of your site. You still need to apply common sense and good security habits to maintain a healthy and secure site. At a bare minimum you should update Joomla and its extensions regularly; maintain regular, tested, off-site backups; and keep an eye out for abnormal site behaviour."

COM_ADMINTOOLS_CONTROLPANEL_LBL_EMPTYROOT_HEAD="Empty path as the base directory of your site."
COM_ADMINTOOLS_CONTROLPANEL_LBL_EMPTYROOT_BODY="PHP reports an empty path as the base directory of your site. This is caused by a bug in older versions of PHP. Please tell your host to upgrade the installed PHP version on their server. If you try using the Fix Permissions button it is very possible that you will be locked out of your site."

COM_ADMINTOOLS_CONTROLPANEL_LBL_MAINPASSWORD="Main Password"
COM_ADMINTOOLS_CONTROLPANEL_LBL_MAINPASSWORD_HEAD="Password Protection"
COM_ADMINTOOLS_CONTROLPANEL_LBL_MAINPASSWORD_INTRO="The administrator of this site has locked down some or all features of Admin Tools with a password. Please supply the password in order to be allowed access to them."

COM_ADMINTOOLS_CONTROLPANEL_LBL_MUSTENTERDLID="You need to enter your Download ID"
COM_ADMINTOOLS_CONTROLPANEL_LBL_NEEDSDLID="You must enter your <b>Download ID</b> before you can update Admin Tools Professional. <a href='%s' target='_blank'>If you don't know your download ID, please click here</a>."
COM_ADMINTOOLS_CONTROLPANEL_MSG_WHERETOENTERDLID="Go to Joomla's System menu from the left hand side. Find the Update pane and click on the Update Sites link. Find the “Admin Tools Professional” item and click on it. Alternatively, <a href=\"%s\">click here</a> to go directly to that page. Enter your Download ID — either your Main ID or an add-on Download ID — in the “Download Key” box and click on the Save button."
COM_ADMINTOOLS_CONTROLPANEL_MSG_JOOMLABUGGYUPDATES="<strong>Important:</strong> If Joomla has already determined there are updates for Admin Tools before you entered your Download ID it <em>may not be able to download them</em> even after you have entered your Download ID due to a number of long-standing Joomla bugs. In this case please download the ZIP file of the latest version from our site. Then go to Joomla's System menu, find the Install pane, click on Extensions, click on the Upload Package File tab and install the ZIP file you downloaded <strong>twice</strong> in a row, <strong>without</strong> uninstalling Admin Tools before or in between. The double installation is required to address another long-standing bug in Joomla which sometimes prevents it from copying all of the updated files when installing an extension update."

COM_ADMINTOOLS_CONTROLPANEL_LBL_FESECRETWORD_RESET="The Secret Word has been changed to <code>%s</code>"

COM_ADMINTOOLS_CONTROLPANEL_LBL_RELOADUPDATE="Reload update information"
COM_ADMINTOOLS_CONTROLPANEL_LBL_UPDATE_INFORMATION_RELOADED="The update information has been reloaded from the server"

COM_ADMINTOOLS_CONTROLPANEL_RESCUEMODE_HEAD="Rescue Mode"
COM_ADMINTOOLS_CONTROLPANEL_RESCUEMODE_MESSAGE="Admin Tools is running in Rescue Mode. This is a troubleshooting mode which lets you unblock yourself if you have accidentally locked yourself out of your site. Admin Tools protections are temporarily disabled only for administrator access by your account and only from your browser and IP address. While you see this message Admin Tools keeps protecting your site."
COM_ADMINTOOLS_CONTROLPANEL_RESCUEMODE_BTN_HOWTOUNBLOCK="How do I unblock myself?"
COM_ADMINTOOLS_CONTROLPANEL_RESCUEMODE_BTN_ENDRESCUE="End Rescue Mode"

COM_ADMINTOOLS_CONTROLPANEL_LBL_SERVERCONFIGWARN_HEAD="Your server config file may need to be rebuilt"
COM_ADMINTOOLS_CONTROLPANEL_LBL_SERVERCONFIGWARN="Admin Tools detected that your server configuration file (ie .htaccess, nginx.conf or web.config) has been modified. We strongly suggest you to put any manual edit inside the <strong>Custom rules</strong> fields, so you won't lose them if you ever regenerate the file using Admin Tools"
COM_ADMINTOOLS_CONTROLPANEL_LBL_SERVERCONFIGWARN_REGENERATE="Regenerate"
COM_ADMINTOOLS_CONTROLPANEL_LBL_SERVERCONFIGWARN_IGNORE="Ignore"
COM_ADMINTOOLS_CONTROLPANEL_ERR_SERVERCONFIGWARN_REGENERATE="Could not regenerate the server configuration file."
COM_ADMINTOOLS_CONTROLPANEL_LBL_SERVERCONFIGWARN_REGENERATED="The server configuration file was regenerated."

COM_ADMINTOOLS_CONTROLPANEL_LBL_DONATE="Donate"

[Adminpassword]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Password-protect Administrator
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_ADMINPASSWORD="Password-protect Administrator"

COM_ADMINTOOLS_ADMINPASSWORD_ERR_NOPASSWORD="You must supply a password"
COM_ADMINTOOLS_ADMINPASSWORD_ERR_NOTAPPLIED="Could not apply the password protection. Please enable the FTP layer in your site's Global Configuration."
COM_ADMINTOOLS_ADMINPASSWORD_ERR_NOTUNAPPLIED="Could not remove the password protection. Please enable the FTP layer in your site's Global Configuration."
COM_ADMINTOOLS_ADMINPASSWORD_ERR_NOUSERNAME="You must supply a username"
COM_ADMINTOOLS_ADMINPASSWORD_ERR_PASSWORDNOMATCH="Passwords do not match"

COM_ADMINTOOLS_ADMINPASSWORD_LBL_HOWITWORKS="How does this work?"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_INFO="When apply the password protection your browser will prompt you for a username and password every time the URL of a protected resource in the <code>administrator</code> folder is requested. You will need to enter the username and password you have entered on this page. This username and password is <em>common</em> for everyone managing your site and <em>must be different</em> to your Joomla login. This works at the server level, using a <code>.htaccess</code> file in your site's <code>administrator</code> folder. Your server must support directory password protection with .htaccess files for this feature to have any effect. If you're not sure this is the case please ask your host."
COM_ADMINTOOLS_ADMINPASSWORD_LBL_WARN="Please note that this protection applies even if you disable or uninstall Admin Tools. If your administrator area becomes inaccessible, or need to remove the password protection without having access to this page, you will need to <strong>delete</strong> the <code>.htaccess</code> and <code>.htpasswd</code> files from the <code>administrator</code> directory of your site using FTP, SFTP or your hosting control panel's File Manager feature."

COM_ADMINTOOLS_ADMINPASSWORD_LBL_PASSWORDPROTECTION="Set up the Administrator Password Protection"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_RESETERRORPAGES="Reset custom error pages"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_RESETERRORPAGES_HELP="Resets Apache custom error pages for HTTP 401 and 403 to the default settings. This prevents a 404 Article Not Found error when trying to access the administrator login page after enabling the Administrator Password Protection feature. You are strongly advised to keep this option enabled unless it causes and HTTP 500 Internal Server Error problem."
COM_ADMINTOOLS_ADMINPASSWORD_LBL_MODE="Administrator resources to protect"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_MODE_JOOMLA="Joomla"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_MODE_PHP="All PHP files"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_MODE_EVERYTHING="Everything"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_MODE_HELP="Choose what will be protected with a password. “Joomla” only protects Joomla's index.php (the administrator application entry point). Everything else can be accessed freely, including .php files from third party applications. “All PHP files” protects all PHP files in the <code>administrator</code> folder and its subdirectories. “Everything” works the same as old versions of Admin Tools, disallowing access to any file in the <code>administrator</code> folder and its subdirectories, regardless of its extension."
COM_ADMINTOOLS_ADMINPASSWORD_LBL_USERNAME="Username"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_USERNAME_HELP="You will need to enter this username before seeing the administrator login page."
COM_ADMINTOOLS_ADMINPASSWORD_LBL_PASSWORD="Password"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_PASSWORD_HELP="You will need to enter this password before seeing the administrator login page."
COM_ADMINTOOLS_ADMINPASSWORD_LBL_PASSWORD2="Retype password"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_PASSWORD2_HELP="Please type the password again to verify it."

COM_ADMINTOOLS_ADMINPASSWORD_LBL_PROTECT="Apply password protection"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_UNPROTECT="Remove Password Protection"

COM_ADMINTOOLS_ADMINPASSWORD_LBL_APPLIED="Password protection successfully applied"
COM_ADMINTOOLS_ADMINPASSWORD_LBL_UNAPPLIED="Password protection successfully removed"

[Badwords]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Anti-spam Bad Words
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_BADWORDS="Bad Words"
COM_ADMINTOOLS_TITLE_BADWORD_EDIT="Edit a Bad Word"
COM_ADMINTOOLS_TITLE_BADWORD_ADD="Add a Bad Word"

COM_ADMINTOOLS_BADWORDS_EMPTYSTATE_TITLE="No Bad Words have been defined yet."
COM_ADMINTOOLS_BADWORDS_EMPTYSTATE_CONTENT="Bad Words allow you to block any public frontend request which includes one or more of these words in any request parameter. They can be used ot block blatant spam and foul language from being submitted to your site."
COM_ADMINTOOLS_BADWORDS_EMPTYSTATE_BUTTON_ADD="Add a Bad Word"

COM_ADMINTOOLS_BADWORDS_TABLE_CAPTION="Table of Bad Words."

COM_ADMINTOOLS_BADWORDS_ERR_NEEDS_WORD="You have to specify a word to block"

COM_ADMINTOOLS_BADWORDS_LBL_WORD="Word"
COM_ADMINTOOLS_BADWORDS_LBL_WORD_DESC="The Bad Word you want blocked. It's case-insensitive, i.e. <code>test</code>, <code>TEST</code> and <code>TesT</code> are considered as the same word."

COM_ADMINTOOLS_BADWORDS_N_ITEMS_COPIED="%d Bad Words were copied."
COM_ADMINTOOLS_BADWORDS_N_ITEMS_COPIED_1="The Bad Word was copied."
COM_ADMINTOOLS_BADWORDS_N_ITEMS_DELETED="%d Bad Words were deleted."
COM_ADMINTOOLS_BADWORDS_N_ITEMS_DELETED_1="The Bad Word was deleted."

COM_ADMINTOOLS_BADWORD_SAVED="The Bad Word was saved."


[Cleantempdirectory]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Clean Temp-Directory
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_CLEANTEMPDIRECTORY="Clean Temp-Directory"

COM_ADMINTOOLS_CLEANTEMPDIRECTORY_LBL_CLEANTMPDONE="Finished Cleaning Temp-directory"
COM_ADMINTOOLS_CLEANTEMPDIRECTORY_LBL_CLEANTMPINPROGRESS="Cleaning Temp-directory..."

[Databasetools]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Database Tools
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_DBTOOLS="Database Tools"
COM_ADMINTOOLS_DATABASETOOLS_LBL_OPTIMIZEDB="Repair &amp; Optimise Tables"
COM_ADMINTOOLS_DATABASETOOLS_LBL_OPTIMIZEDB_COMPLETE="Optimisation is complete"
COM_ADMINTOOLS_DATABASETOOLS_LBL_OPTIMIZEDB_INPROGRESS="Optimisation in progress..."
COM_ADMINTOOLS_DATABASETOOLS_LBL_PURGESESSIONS="Purge Sessions"
COM_ADMINTOOLS_DATABASETOOLS_LBL_PURGESESSIONS_COMPLETE="Finished purging the sessions table"
COM_ADMINTOOLS_DATABASETOOLS_LBL_PURGESESSIONS_WARN="WARNING: This will log out all users from the site, possibly including yourself."

[Emergencyoffline]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Emergency Off-Line
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_EMERGENCYOFFLINE="Emergency Off-Line"

COM_ADMINTOOLS_EMERGENCYOFFLINE_ERR_NOTAPPLIED="Could not apply the Emergency Off-Line mode. Click the Emergency Off-Line button for information on manually applying it."
COM_ADMINTOOLS_EMERGENCYOFFLINE_ERR_NOTUNAPPLIED="Could not deactivate the Emergency Off-Line mode. Click the Emergency Off-Line button for information on manually deactivating it."
COM_ADMINTOOLS_ERR_EXCEPTIONSFROMWAF_ALLNULL="You can not leave all fields blank; that would mean that some WAF settings are always inactive!"

COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_APPLIED="Your site is now in Emergency Off-Line mode"
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_PREAPPLY="Clicking the button below will set your site to the Emergency Off-Line mode. In this mode nobody will be able to access your site except visitors coming from your current IP address. Should your Internet connection drop or your IP change for any reason, the only way to access your site will be removing the <code>.htaccess</code> file from your site's root using FTP. Please read this very carefully and print this page for reference."
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_PREAPPLYMANUAL="In case this automated tools fails to create the <code>.htaccess</code> file on your site's root, please remove your current <code>.htaccess</code> (if any) and create a new <code>.htaccess</code> file with the following contents:"
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_PREUNAPPLY="Clicking the Set Offline button will re-apply Emergency Off-Line mode's <code>.htaccess</code> file on your site's root. Clicking the Set Online button will remove that file."
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_PREUNAPPLYMANUAL="If setting the site back on-line fails, you can still do it using FTP, SFTP or your hosting control panel's file manager. Remove the current <code>.htaccess</code> file from your site's root. Then rename the <code>.htaccess.eom</code> file back to <code>.htaccess</code>."
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_SETOFFLINE="Set Offline"
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_UNAPPLIED="Your site is now On-Line"
COM_ADMINTOOLS_EMERGENCYOFFLINE_LBL_UNAPPLY="Set Online"


[Fixpermissions]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Fix Permissions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_FIXPERMISSIONS="Fix Permissions"

COM_ADMINTOOLS_FIXPERMISSIONS_LBL_DONE="Finished fixing permissions"
COM_ADMINTOOLS_FIXPERMISSIONS_LBL_INPROGRESS="Fixing permissions..."

[Configurepermissions]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Permissions Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_CONFIGUREPERMISSIONS="Permissions Configuration"

COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_CUSTOMSAVED="The custom permissions have been saved"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_CUSTOMSAVEDAPPLIED="The custom permissions have been saved and applied"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_DEFAULTS="Default permissions"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_DEFAULTSSAVED="Default permissions have been saved"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_DEFDIRPERM="Directories"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_DEFFILEPERMS="Files"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_FILES_HEADER="Files"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_FILE="File"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_FOLDER="Folder"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_FOLDERS_HEADER="Folders"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_OWNER="Owner"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_PATH="Path"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_PERMS="Permissions"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_ROOT="&lt; Root &gt;"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_SAVEAPPLYPERMS="Save and Apply custom permissions"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_SAVEDEFAULTS="Save default permissions"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_SAVEPERMS="Save custom permissions"
COM_ADMINTOOLS_CONFIGUREPERMISSIONS_LBL_SHOW_HIDDEN="Apply to dot (hidden) files"

[Serverconfigmaker]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Common server configuration file maker
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_SERVERCONFIGMAKER_ERR_PROTECTION_HEAD="Admin Tools detected an unauthorised security settings modification"
COM_ADMINTOOLS_SERVERCONFIGMAKER_ERR_PROTECTION_DETECTED="WARNING! A third party extension is trying to silently modify your site's security settings."
COM_ADMINTOOLS_SERVERCONFIGMAKER_ERR_PROTECTION_DETAILS="Admin Tools has detected that a third party software is trying to modify its settings. This may lead to degradation of your site's security and your site getting hacked. Admin Tools has prevented this action to protect you. You can find some technical information below."
COM_ADMINTOOLS_SERVERCONFIGMAKER_ERR_PROTECTION_RESOLUTION="This tells you which extension triggered this error message. Please contact its developer and ask them to fix this issue by REMOVING the code which automatically modifies Admin Tools' settings."

[Htaccessmaker]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; .htaccess Maker
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_HTACCESSMAKER=".htaccess Maker"

COM_ADMINTOOLS_LBL_SERVERTECH_RESET_CONFIRM="Do you really want to reset all of the options displayed on this page to their default values?"

COM_ADMINTOOLS_HTACCESSMAKER_LBL_ALLOWXMLRPC="Allow access to the XML-RPC server"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_APPLIED="The new .htaccess has been written to disk"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_APPLY="Save and create .htaccess"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_AUTOCOMPRESS="Automatically compress static resources"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_AUTOROOT="Redirect index.php to the site's root"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_AUTOROOT_ALT="Alternate"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_AUTOROOT_OFF="No"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_AUTOROOT_STD="Standard"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BACKENDPROT="Backend protection"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BASICSEC="Basic security"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BEPEXDIRS="Backend directories where file type exceptions are allowed"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BEPEXTYPES="Backend file types allowed in selected directories"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BLOCKCOMMON="Block common exploits"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CFIPFWD="Allow IP forwarding"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PROXY_IPS="Reverse Proxy / Load Balancer IPs"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_COMMON_IP_OR_CIDR="IP address or CIDR"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CLICKJACKING="Protect against clickjacking"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CORS="Cross-Origin Resource Sharing (CORS)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CORS_OPT_ENABLE="Explicitly allowed"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CORS_OPT_SAMEORIGIN="Explicitly disallowed"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CORS_OPT_UNSET="Let the browser decide (default)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CUSTFOOT="Custom .htaccess rules at the bottom of the file"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CUSTHEAD="Custom .htaccess rules at the top of the file"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_CUSTOM="Custom .htaccess rules"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ENABLESEF="Enable SEF URLs"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ENCUTF8="Set the default character encoding to utf-8"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE="Send ETag"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE_DEFAULT="Server default"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE_FULL="Full"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE_NONE="None (no ETag sent)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE_SIZE="Size only"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_ETAGTYPE_SIZETIME="Size and Time"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXCEPTIONDIRS="Allow direct access, except .php files, to these directories"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXCEPTIONFILES="Allow direct access to these files"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXPTIME="Set a long expiration time for static media"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXPTIME_NO="Immediate expiration (default)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXPTIME_VARIES="One week for CSS/JS, one month for static media"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_EXPTIME_YEAR="One year for all static media"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FASTCGIPASSBLOCK="fastcgi_pass code block setting (read the documentation)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FEPEXDIRS="Frontend directories where file type exceptions are allowed"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FEPEXTYPES="Frontend file types allowed in selected directories"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FILEINJ="Protect against common file injection attacks"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FILEORDER="Force index.php parsing before index.html"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FORCEGZIP="Force GZip compression for mangled Accept-Encoding headers"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FRONTENDPROT="Frontend protection"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FULLACCESSDIRS="Allow direct access, including .php files, to these directories"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HOGGERAGENTS="User agents to block"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HSTSHEADER="HSTS Header (for HTTPS-only sites)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HSTSHEADER_OPT_NONE="No"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HSTSHEADER_OPT_BASIC="Basic"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HSTSHEADER_OPT_PRELOAD="For HSTS Preloading"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HTTPHOST="Host name for HTTP requests (without http://)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HTTPSHOST="Host name for HTTPS requests (without https://)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_HTTPSURLS="Force HTTPS for these URLs (do not include the domain name)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_KITCHENSINK="Advanced NginX Settings"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_LEFTOVERS="Block access to configuration.php-dist and htaccess.txt"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_MAXCLIENTBODY="Set maximum client body size to 1 Gb"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NGINXSECURITY="Tighten NginX security settings"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NODIRLISTS="Disable directory listings (recommended)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NOHOGGERS="Block access from specific user agents"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NOSERVERSIGNATURE="Remove web server and PHP version signature"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NOTAPPLIED="Could not write the .htaccess file. Please use the Preview button to get its contents and upload it manually."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NOTRACETRACK="Disable HTTP methods TRACE and TRACK (protect against XST)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_NOTRANSFORM="Prevent content transformation"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OLDDOMAIN="Redirect this (old) domain name to the new one"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTFHNDLCACHE="Optimise file handle cache"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTOUTBUF="Optimise output buffering"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTSOCKETS="Optimise socket settings"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTTCPPERF="Optimise TCP performance"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTTIMEOUT="Optimise timeout handling"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_OPTUTIL="Optimisation and utility"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REDUCEMIMETYPERISKS="Reduce MIME type security risks"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERER="Anti-leech protection for static resources outside images/stories"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY="Referrer Policy header"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_DISABLED="Do not set any policy"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_EMPTY="(Empty)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_NOREF="no-referrer"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_NOREF_DOWNGRADE="no-referrer-when-downgrade"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_ORIGIN="origin"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_ORIGINCROSS="origin-when-cross-origin"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_SAMEORIGIN="same-origin"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_STRICTORIGIN="strict-origin"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_STRICTORIGINGCROSS="strict-origin-when-cross-origin"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFERERPOLICY_UNSAFE="unsafe-url"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REFLECTEDXSS="Reflected XSS prevention"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_RESET="Reset Htaccess Maker options"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_RESET_DONE="Htaccess Maker options has been reset"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_REWRITEBASE="Base directory of your site (/ for domain's root)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SAVE="Save without creating .htaccess"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SAVED="Changes have been successfully saved. Do not forget to apply them by creating the new .htaccess file"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SERVERPROT="Server protection"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SERVERPROT_EXCEPTIONS="Exceptions from Server Protection"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SVGNEUTRALISE="Neutralise SVG script execution"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYMLINKS="Follow symlinks (may cause a blank page or 500 Internal Server Error)"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYMLINKS_DEFAULT="Server default"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYMLINKS_FOLLOW="Yes, always"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYMLINKS_IFOWNERMATCH="Only if owner matches"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYMLINKS_OFF="Default"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_SYSCONF="System configuration"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_TUNETEXT="If some of the aspects of your site suddenly stop working it's up to you to find the proper exceptions required for their correct operation. Instructions are given in the component's documentation."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_UTF8CHARSET="Set the UTF-8 character set as the default"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WARNING="WARNING!"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WARNTEXT="Due to varying compatibility of the following settings among servers, applying the .htaccess file may cause inability to access your site with a white page or an Internal Server Error 500 message. In this case, remove the .htaccess and try disabling some options before reapplying."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WILLTHISWORK="Will the .htaccess Maker work with my server?"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WILLTHISWORK_MAYBE="<b>Maybe</b>. We have detected a server type which may or may not be compatible with .htaccess files. If the options below have no effect please ask your host if your server supports .htaccess files."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WILLTHISWORK_NO="<b>No, not at all</b>. We have detected that you are using a server type which is incompatible with .htaccess files (e.g. Microsoft IIS or NginX). Using the .htaccess Maker will have <strong>no effect whatsoever</strong> on your site."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WILLTHISWORK_YES="<b>Most likely yes</b>. We have detected that your web server type is Apache which supports .htaccess files. If the options below have no effect or turning them all off still results in a 500 Internal Server Error or blank page please contact your host and ask them to enable .htaccess file support."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WWWREDIR="Redirect www and non-www addresses"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WWWREDIR_NO="Do not redirect"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WWWREDIR_NONWWW="Redirect www to non-www"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_WWWREDIR_WWW="Redirect non-www to www"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_COMMON_DIRECTORY="Directory"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_COMMON_FILE="File"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_COMMON_URL_PATH="Relative URL"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_BESTATICRISKS="Disable client-side risky behavior in backend static content"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_FESTATICRISKS="Disable client-side risky behavior in frontend static content"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS="PHP handler directives found"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_DESC="Admin Tools detected that your <code>.htaccess</code> file contains directives instructing your web server to use a specific PHP version. These directives, shown below, need to be copied into the Custom .htaccess Rules field for your site to operate correctly upon creating a new .htaccess file with Admin Tools. Click the Apply button below to do this automatically."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_APPLY="Apply"
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_ERR_NO_HTACCESS="There is no <code>.htaccess</code> file in your site's root."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_ERR_NO_HANDLERS="There are no recognizable PHP handler directives in the <code>.htaccess</code> file in your site's root."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_ERR_ALREADY_SAVED="The PHP handler directives are already set up in the Custom .htaccess Rules field. Please remove them first, and save your changes (without creating a .htaccess file) before trying to use this feature again."
COM_ADMINTOOLS_HTACCESSMAKER_LBL_PHPHANDLERS_SAVED="The PHP handler directives found in the <code>.htaccess</code> file in your site's root have been copied into the Custom .htaccess Rules field. Please check that they look right, then click on Save &amp; create a .htaccess to complete the process."

[Nginxconfmaker]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; NginX Configuration Maker
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_NGINXCONFMAKER="NginX Configuration Maker"

COM_ADMINTOOLS_NGINXCONFMAKER_LBL_APPLIED="The new nginx.conf has been written to disk. Remember to include it or copy it inside your NginX site configuration file and reload or restart your server."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_APPLY="Save and create nginx.conf"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_NOTAPPLIED="Could not write the nginx.conf file. Please use the Preview button to get its contents and include it manually in your site's configuration file."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_RESET="Reset NginX Maker options"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_RESET_DONE="Nginx Maker options has been reset"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_SAVE="Save without creating nginx.conf"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_SAVED="Changes have been successfully saved. Do not forget to apply them by creating the new nginx.conf file and reloading or restarting your NginX server."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_TUNETEXT="If some of the aspects of your site suddenly stop working it's up to you to find the proper exceptions required for their correct operation. Instructions are given in the component's documentation. Please remember that settings do not take effect until you reload or restart your NginX server."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WARNING="IMPORTANT"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WARNTEXT="Due to the efficient way NginX works, you will need to do two things for these settings to have any effect. First, you should copy the contents of the NginX configuration file for this site and copy it into your main one (if this is a dev site you could simply include the site file adding the line <code>include %s;</code> inside the server definition). Then you need to reload or restart your server."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WILLTHISWORK="Will the NginX Configuration Maker work with my server?"
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WILLTHISWORK_MAYBE="<b>Maybe</b>. We could not detect the server type, therefore we have no idea if your site supports NginX configuration files. Please consult with your host about their support for NginX configuration files and the proper way to use a custom nginx.conf file with your site."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WILLTHISWORK_NO="<b>No, not at all</b>. We have detected that you are using a server type which is incompatible with NginX configuration files (e.g. Microsoft IIS, Apache, Lightspeed or Lighttpd). Using the NginX Configuration Maker will have <strong>no effect whatsoever</strong> on your site."
COM_ADMINTOOLS_NGINXCONFMAKER_LBL_WILLTHISWORK_YES="<b>Most likely yes</b>. We have detected that your web server type is NginX. Support for custom per-site configuration is, however, up to your host. Please consult with your host about the proper way to use a custom nginx.conf file with your site."

[Webconfigmaker]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; web.config Maker
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_WEBCONFIGMAKER="web.config Maker"

COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_APPLIED="The new web.config has been written to disk."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_APPLY="Save and create web.config"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_NOTAPPLIED="Could not write the web.config file. Please use the Preview button to get its contents and include it manually in your web.config file."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_RESET="Reset WebConfig Maker options"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_RESET_DONE="WebConfig Maker options has been reset"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_SAVE="Save without creating web.config"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_SAVED="Changes have been successfully saved."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_TUNETEXT="If some of the aspects of your site suddenly stop working it's up to you to find the proper exceptions required for their correct operation. Instructions are given in the component's documentation."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WARNING="WARNING!"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WARNTEXT="Due to varying compatibility of the following settings among servers, applying the web.config file may cause inability to access your site with a white page or an Internal Server Error 500 error message. In this case, remove the web.config file and try disabling some options before reapplying."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WILLTHISWORK="Will the web.config Maker work with my server?"
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WILLTHISWORK_MAYBE="<b>Maybe</b>. There was uncertainty in the server type detection. Simply put, we're not sure that you're running your site on Microsoft IIS, the only server type supporting web.config files. If you are told by your host that you are running on Microsoft IIS you can try using the web.config Maker."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WILLTHISWORK_NO="<b>No, not at all</b>. We have detected that you are using a server type which is incompatible with web.config files (e.g. Apache or NginX). Using the web.config Maker will have <strong>no effect whatsoever</strong> on your site."
COM_ADMINTOOLS_WEBCONFIGMAKER_LBL_WILLTHISWORK_YES="<b>Most likely yes</b>. We have detected that your web server type is IIS which supports web.config files. If the options below have no effect or turning them all off still results in a 500 Internal Server Error or blank page please contact your host and ask them to enable web.config file support."


[Ipautobanhistories]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Auto IP Blocking History
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_IPAUTOBANHISTORIES="Auto IP Blocking History"

COM_ADMINTOOLS_IPAUTOBANHISTORIES_EMPTYSTATE_TITLE="No Automatic IP Blocking History entries."
COM_ADMINTOOLS_IPAUTOBANHISTORIES_EMPTYSTATE_CONTENT="This page displays the history of IP addresses which had been automatically blocked. This information can be used to permanently block IP addresses of repeat and persistent offenders. Each entry here will list these previously blocked IP addresses, the last reason a request from each one was blocked and until when each one was blocked."
COM_ADMINTOOLS_IPAUTOBANHISTORIES_EMPTYSTATE_BUTTON_ADD="Go back"

COM_ADMINTOOLS_IPAUTOBANHISTORIES_TABLE_CAPTION="Table of automatically blocked IP address history."
COM_ADMINTOOLS_IPAUTOBANHISTORIES_LBL_REASON_SELECT="– Last block reason –"

COM_ADMINTOOLS_IPAUTOBANHISTORIES_LBL_IP="IP Address"
COM_ADMINTOOLS_IPAUTOBANHISTORIES_LBL_REASON="Last block reason"
COM_ADMINTOOLS_IPAUTOBANHISTORIES_LBL_UNTIL="Blocked until"

COM_ADMINTOOLS_IPAUTOBANHISTORIES_N_ITEMS_DELETED="%d Automatic IP Blocking History entries were deleted."
COM_ADMINTOOLS_IPAUTOBANHISTORIES_N_ITEMS_DELETED_1="The Automatic IP Blocking History entry was deleted."

[Autobannedaddresses]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Auto IP Blocking Administration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_AUTOBANNEDADDRESSES="Auto Blocked IP Addresses"

COM_ADMINTOOLS_AUTOBANNEDADDRESS_EMPTYSTATE_TITLE="No Automatically Blocked IP Addresses."
COM_ADMINTOOLS_AUTOBANNEDADDRESS_EMPTYSTATE_CONTENT="IP addresses will be automatically blocked after requests coming from them get blocked <em>at least as many</em> times as you've set up in the Configure WAF page, Auto-ban tab. This page here will list these blocked IP addresses, the last reason a request from each one was blocked and until when each one will remain blocked."
COM_ADMINTOOLS_AUTOBANNEDADDRESS_EMPTYSTATE_BUTTON_ADD="Go back"

COM_ADMINTOOLS_AUTOBANNEDADDRESSES_TABLE_CAPTION="Table of automatically blocked IP addresses."
COM_ADMINTOOLS_AUTOBANNEDADDRESS_LBL_REASON_SELECT="– Latest block reason –"

COM_ADMINTOOLS_AUTOBANNEDADDRESS_LBL_IP="IP Address"
COM_ADMINTOOLS_AUTOBANNEDADDRESS_LBL_REASON="Latest block reason"
COM_ADMINTOOLS_AUTOBANNEDADDRESS_LBL_UNTIL="Blocked until"

COM_ADMINTOOLS_AUTOBANNEDADDRESS_N_ITEMS_DELETED="%d Automatically Blocked IP addresses were deleted."
COM_ADMINTOOLS_AUTOBANNEDADDRESS_N_ITEMS_DELETED_1="The Automatically Blocked IP address was deleted."

[Disallowlist]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Site IP Disallow List
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_DISALLOWLISTS="Site IP Disallow List"
COM_ADMINTOOLS_TITLE_DISALLOWLIST_EDIT="Edit an IP Disallow List entry"
COM_ADMINTOOLS_TITLE_DISALLOWLIST_ADD="Add an IP Disallow List entry"

COM_ADMINTOOLS_DISALLOWLISTS_EMPTYSTATE_TITLE="No Site IP Disallow List entries have been defined yet."
COM_ADMINTOOLS_DISALLOWLISTS_EMPTYSTATE_CONTENT="Site IP Disallow list entries block specific IP addresses or address ranges from having access to your site, public frontend and administrator backend. Use this to block persistent attackers. Try to keep the list small; too many entries and your site will become sluggish."
COM_ADMINTOOLS_DISALLOWLISTS_EMPTYSTATE_BUTTON_ADD="Add a Site Disallowed IP"

COM_ADMINTOOLS_DISALLOWLIST_ERR_TOOMANY_TITLE="Too many blocked IPs may negatively affect the performance of your site"
COM_ADMINTOOLS_DISALLOWLIST_ERR_TOOMANY_BODY="Too many blocked IP addresses may negatively affect your site's performance. Furthermore, you are most likely unwittingly blocking legitimate users. Please consult <a href='%s'>our documentation</a> for more details."
COM_ADMINTOOLS_DISALLOWLIST_ERR_NOTENABLED_BODY="The IP addresses you enter below will <strong>not</strong> be taken into account until you enable the “Disallow site access to IPs in IP Disallow List” option in the Configure WAF page."
COM_ADMINTOOLS_DISALLOWLIST_ERR_NOTENABLED_TITLE="The IP Disallow List feature is not enabled"

COM_ADMINTOOLS_BLACKLISTEDADDRESSES_EXPORT="Export IP"
COM_ADMINTOOLS_BLACKLISTEDADDRESSES_IMPORT="Import IP"

COM_ADMINTOOLS_DISALLOWLIST_ERR_NEEDS_IP="You have to specify an IP address"
COM_ADMINTOOLS_DISALLOWLIST_ERR_NOITEMS="No IPs have been added to the Disallow List yet"
COM_ADMINTOOLS_DISALLOWLIST_LBL_DELETED="IP ranges are now removed from the IP Disallow List"
COM_ADMINTOOLS_DISALLOWLIST_LBL_DESCRIPTION="Description"
COM_ADMINTOOLS_DISALLOWLIST_LBL_DESCRIPTION_DESC="A short description of this IP or IP range. This is for your own reference."
COM_ADMINTOOLS_DISALLOWLIST_LBL_IP="IP address range"
COM_ADMINTOOLS_DISALLOWLIST_LBL_IP_DESC="<p>You can specify an IP or IP range in the following formats:<ul><li><b>Single IP</b>, i.e. <var>192.168.1.1</var></li><li><b>Simple IP Range</b>, i.e. <var>192.168.1.1-192.168.1.255</var></li><li><b>Implied IP Range</b>, i.e. <var>192.168.1.</var></li><li><b>CIDR Block</b>, i.e. <var>192.168.1.0/24</var></li><p>"

COM_ADMINTOOLS_DISALLOWLIST_LBL_YOURIP="Your current IP <em>as seen by your web server</em>"
COM_ADMINTOOLS_DISALLOWLIST_LBL_YOURIP_PLACEHOLDER="(could not determine your IP address)"

COM_ADMINTOOLS_DISALLOWLISTS_N_ITEMS_COPIED="%d IP Disallow List entries were copied."
COM_ADMINTOOLS_DISALLOWLISTS_N_ITEMS_COPIED_1="The IP Disallow List entry was copied."
COM_ADMINTOOLS_DISALLOWLISTS_N_ITEMS_DELETED="%d IP Disallow List entries were deleted."
COM_ADMINTOOLS_DISALLOWLISTS_N_ITEMS_DELETED_1="The IP Disallow List entry was deleted."
COM_ADMINTOOLS_DISALLOWLIST_LBL_SAVED="The IP Disallow List entry was saved."

[Allowlist]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Site IP Disallow List
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_ALLOWLISTS="Site IP Allow List"
COM_ADMINTOOLS_TITLE_ALLOWLIST_EDIT="Edit an IP Allow List entry"
COM_ADMINTOOLS_TITLE_ALLOWLIST_ADD="Add an IP Allow List entry"

COM_ADMINTOOLS_ALLOWLISTS_EMPTYSTATE_TITLE="No Site IP Allow List entries have been defined yet."
COM_ADMINTOOLS_ALLOWLISTS_EMPTYSTATE_CONTENT="Site IP Allow list entries will let requests from specific IP addresses or address ranges to go through, without being being stopped by Admin Tools. Use this to allow known, vetted services and servers e.g. your payment services provider. Keep in mind that if an attack originates from one of these IP addresses <em>it will not be stopped</em>."
COM_ADMINTOOLS_ALLOWLISTS_EMPTYSTATE_BUTTON_ADD="Add a Site Allowed IP"

COM_ADMINTOOLS_ALLOWLIST_ERR_TOOMANY_TITLE="Too many allowed IPs may negatively affect the performance of your site"
COM_ADMINTOOLS_ALLOWLIST_ERR_TOOMANY_BODY="Too many allowed IP addresses may negatively affect your site's performance. Furthermore, you are most likely unwittingly allowing attacks from IP addresses which have been reassigned to untrusted parties. Please consult <a href='%s'>our documentation</a> for more details."

COM_ADMINTOOLS_ALLOWLIST_ERR_NEEDS_IP="You have to specify an IP address"
COM_ADMINTOOLS_ALLOWLIST_ERR_NOITEMS="No IPs have been added to the Allow List yet"
COM_ADMINTOOLS_ALLOWLIST_LBL_DELETED="IP ranges are now removed from the IP Allow List"
COM_ADMINTOOLS_ALLOWLIST_LBL_DESCRIPTION="Description"
COM_ADMINTOOLS_ALLOWLIST_LBL_DESCRIPTION_DESC="A short description of this IP or IP range. This is for your own reference."
COM_ADMINTOOLS_ALLOWLIST_LBL_IP="IP address range"
COM_ADMINTOOLS_ALLOWLIST_LBL_IP_DESC="<p>You can specify an IP or IP range in the following formats:<ul><li><b>Single IP</b>, i.e. <var>192.168.1.1</var></li><li><b>Simple IP Range</b>, i.e. <var>192.168.1.1-192.168.1.255</var></li><li><b>Implied IP Range</b>, i.e. <var>192.168.1.</var></li><li><b>CIDR Block</b>, i.e. <var>192.168.1.0/24</var></li><p>"

COM_ADMINTOOLS_ALLOWLIST_LBL_YOURIP="Your current IP <em>as seen by your web server</em>"
COM_ADMINTOOLS_ALLOWLIST_LBL_YOURIP_PLACEHOLDER="(could not determine your IP address)"

COM_ADMINTOOLS_ALLOWLISTS_N_ITEMS_COPIED="%d IP Allow List entries were copied."
COM_ADMINTOOLS_ALLOWLISTS_N_ITEMS_COPIED_1="The IP Allow List entry was copied."
COM_ADMINTOOLS_ALLOWLISTS_N_ITEMS_DELETED="%d IP Allow List entries were deleted."
COM_ADMINTOOLS_ALLOWLISTS_N_ITEMS_DELETED_1="The IP Allow List entry was deleted."
COM_ADMINTOOLS_ALLOWLIST_LBL_SAVED="The IP Allow List entry was saved."


[Adminallowlist]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Administrator Exclusive Allow IP List
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_ADMINALLOWLISTS="Administrator Exclusive Allow IP List"
COM_ADMINTOOLS_TITLE_ADMINALLOWLIST_EDIT="Edit an Administrator Exclusive Allow IP"
COM_ADMINTOOLS_TITLE_ADMINALLOWLIST_ADD="Add an Administrator Exclusive Allow IP"

COM_ADMINTOOLS_ADMINALLOWLISTS_EMPTYSTATE_TITLE="No Administrator Exclusive Allow IP have been defined yet."
COM_ADMINTOOLS_ADMINALLOWLISTS_EMPTYSTATE_CONTENT="Administrator Exclusive Allow IP limit who can access your site's administrator backend to a select few IP addresses only. Use this when you only ever access your site from a connection with a static IP address or through a corporate VPN with a known IP address."
COM_ADMINTOOLS_ADMINALLOWLISTS_EMPTYSTATE_BUTTON_ADD="Add an Administrator Exclusive Allow IP"

COM_ADMINTOOLS_ADMINALLOWLISTS_TABLE_CAPTION="Table of Administrator Exclusive Allow IP addresses and IP ranges."

COM_ADMINTOOLS_ADMINALLOWLIST_ERR_NEEDS_IP="You have to specify an IP address, IP range, or a lookup domain name"

COM_ADMINTOOLS_ADMINALLOWLIST_ERR_NOTENABLED_TITLE="The Administrator Exclusive Allow IP List feature is not enabled"
COM_ADMINTOOLS_ADMINALLOWLIST_ERR_NOTENABLED_BODY="The IP addresses you enter below will <strong>not</strong> be taken into account until you enable the “Allow administrator access only to IPs in the Exclusive Allow IP List” option in the Configure WAF page."

COM_ADMINTOOLS_ADMINALLOWLIST_LBL_DESCRIPTION="Description"
COM_ADMINTOOLS_ADMINALLOWLIST_LBL_DESCRIPTION_DESC="This is for your own reference. It is not visible to anyone else and does not have any effect. Use to describe the IP address, IP range or lookup domain name you are adding to the list."
COM_ADMINTOOLS_ADMINALLOWLIST_LBL_IP="IP address range"
COM_ADMINTOOLS_ADMINALLOWLIST_LBL_IP_DESC="<p>You can specify an IP or IP range, or a lookup domain name in the following formats:<ul><li><b>Single IP</b>, i.e. <var>192.168.1.1</var></li><li><b>Simple IP Range</b>, i.e. <var>192.168.1.1-192.168.1.255</var></li><li><b>Implied IP Range</b>, i.e. <var>192.168.1.</var></li><li><b>CIDR Block</b>, i.e. <var>192.168.1.0/24</var></li><li><b>IPv4 lookup for a domain name</b>, i.e. <var>@example.dyndns.info</var>, useful for allowing your dynamically assigned IPv4 (does not resolve to IPv6).</li><li><b>IPv6 lookup for a domain name</b>, i.e. <var>#example.dyndns.info</var>, useful for allowing your dynamically assigned IPv6 (does not resolve to IPv4).</li></ul><p>"

COM_ADMINTOOLS_ADMINALLOWLIST_LBL_YOURIP="Your current IP <em>as seen by your web server</em>"
COM_ADMINTOOLS_ADMINALLOWLIST_LBL_YOURIP_PLACEHOLDER="(could not determine your IP address)"

COM_ADMINTOOLS_ADMINALLOWLISTS_N_ITEMS_COPIED="%d Administrator Exclusive Allow IPs were copied."
COM_ADMINTOOLS_ADMINALLOWLISTS_N_ITEMS_COPIED_1="The Administrator Exclusive Allow IP was copied."

COM_ADMINTOOLS_ADMINALLOWLISTS_N_ITEMS_DELETED="%d Administrator Exclusive Allow IPs were deleted."
COM_ADMINTOOLS_ADMINALLOWLISTS_N_ITEMS_DELETED_1="The Administrator Exclusive Allow IP was deleted."

COM_ADMINTOOLS_ADMINALLOWLIST_LBL_SAVED="Administrator Exclusive Allow IP saved"

[Mainpassword]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Main Password
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_MAINPASSWORD="Main Password"

COM_ADMINTOOLS_MAINPASSWORD_LBL_ALL="All"
COM_ADMINTOOLS_MAINPASSWORD_LBL_NONE="None"
COM_ADMINTOOLS_MAINPASSWORD_LBL_PASSWORD="Main Password"
COM_ADMINTOOLS_MAINPASSWORD_LBL_PROTVIEWS="Protected Features"
COM_ADMINTOOLS_MAINPASSWORD_LBL_PWPROMPT="Password"
COM_ADMINTOOLS_MAINPASSWORD_LBL_QUICKSELECT="Quick selection:"
COM_ADMINTOOLS_MAINPASSWORD_LBL_SAVED="Main Password and feature protection settings have been saved"


[Quickstart]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Quick Setup Wizard
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_QUICKSTART="Quick Setup Wizard"

COM_ADMINTOOLS_QUICKSTART_ADMINISTRATORPASSORD_INFO="Whenever you visit your <code>administrator</code> login area you will need to enter this username and password to your browser before seeing the login form where you can enter your Joomla! username and password. This will slow hackers down considerably."
COM_ADMINTOOLS_QUICKSTART_ADMINLOGINEMAIL_DESC="Whenever an administrator login attempt is detected, successful or failed, an email will be sent to this address with information about the login username, IP address and so on."
COM_ADMINTOOLS_QUICKSTART_ADMINLOGINEMAIL_LBL="Send an email for all administrator login attempts"
COM_ADMINTOOLS_QUICKSTART_ALMOSTTHERE_INTRO="We're almost there. Before proceeding you need to know what to do if things go wrong. Admin Tools is a security tool which changes the way your web site works. Depending on what you are trying to do and your Admin Tools configuration it may sometimes interfere with the way both Joomla itself and its various extensions work. If you are unable to log in or access your site or otherwise have some unidentified issue using your site right after applying this wizard please refer to the following URLs for troubleshooting instructions:"
COM_ADMINTOOLS_QUICKSTART_ALMOSTTHERE_OUTRO="Before clicking the button below <strong>please print out this page, or take a screenshot</strong>, for your reference."
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_BODY="You have already configured Admin Tools, either manually or by running this Quick Setup Wizard in the past. We do not recommend or support running the Quick Setup Wizard again. Doing so will overwrite your Admin Tools configuration, possibly breaking your site. Are you sure you want to continue?"
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_BTN_NO="No, go back!"
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_BTN_YES="Yes, run the Quick Setup Wizard"
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_HEAD="You have already configured Admin Tools."
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_NOSUPPORT_BODY="Using this wizard will overwrite all of your Admin Tools configuration settings. If you do not want to overwrite ALL of your Admin Tools settings please click the Back button now."
COM_ADMINTOOLS_QUICKSTART_ALREADYCONFIGURED_NOSUPPORT_HEAD="You are about to overwrite all of your configuration settings"
COM_ADMINTOOLS_QUICKSTART_AUTOBAN_DESC="If a request from the same IP address is blocked three or more times in a minute they will blocked from accessing your site for 15 minutes."
COM_ADMINTOOLS_QUICKSTART_AUTOBAN_LBL="Automatically block repeat offenders"
COM_ADMINTOOLS_QUICKSTART_AUTOBLACKLIST_DESC="If a repeat offender's IP is auto-blocked three or more times their IP will be permanently added to the IP Disallow List, meaning they won't be able to access your site any more."
COM_ADMINTOOLS_QUICKSTART_AUTOBLACKLIST_LBL="Add repeated blocked IPs to the IP Disallow List"
COM_ADMINTOOLS_QUICKSTART_ENABLEWAF_DESC="Enabling the Web Application Firewall will let Admin Tools protect you against the most common attacks against your site. You can fine tune this protection later from the Web Application Firewall, Configure WAF page of Admin Tools."
COM_ADMINTOOLS_QUICKSTART_ENABLEWAF_LBL="Enable Web Application Firewall"
COM_ADMINTOOLS_QUICKSTART_HEAD_ADMINSECURITY="Administrator security"
COM_ADMINTOOLS_QUICKSTART_HEAD_ADVANCEDSECURITY="Advanced security"
COM_ADMINTOOLS_QUICKSTART_HEAD_ALMOSTTHERE="We're almost there..."
COM_ADMINTOOLS_QUICKSTART_HTMAKER_DESC="This .htaccess file will prevent many types of attacks at the web server level."
COM_ADMINTOOLS_QUICKSTART_HTMAKER_LBL="Create a security tightening .htaccess"
COM_ADMINTOOLS_QUICKSTART_INTRO="This wizard will guide you through the basic configuration of Admin Tools. Hover your mouse over each label to get more information about what each option does. Please use it only on a new installation of Admin Tools. It will override any settings you may have already set. This wizard is not intended as a substitute for reading the <a href=\"%s\">documentation</a> and fine tuning the protection for your site."
COM_ADMINTOOLS_QUICKSTART_MSG_DONE="Your Admin Tools setup preferences have been saved"
COM_ADMINTOOLS_QUICKSTART_MSG_HTMAKERNOTAPPLIED="Could not write the .htaccess file. Please go to the .htaccess Maker page and use the Preview button to get the new .htaccess file's contents. Then upload the file manually per the documentation instructions."
COM_ADMINTOOLS_QUICKSTART_MSG_IPADDEDBYWIZARD="Your IP as detected by the Quick Setup Wizard"
COM_ADMINTOOLS_QUICKSTART_NONEWADMINS_DESC="You will no longer be able to edit or create users with administrator area access, e.g. Super Users or Administrators. You will also not be able to convert existing users to Super Users, Administrators and so on. Trying to do that will result in a 403 Access Denied error message."
COM_ADMINTOOLS_QUICKSTART_WHITELIST_DESC="Access to the administrator area will only be allowed to a preset list of IP addresses. By default this only includes your current IP address, <code>%s</code>."
COM_ADMINTOOLS_QUICKSTART_MSG_PLEASERUNWIZARD="Admin Tools is not protecting your site yet. Please run the <a href='%s'>Quick Setup Wizard</a> to configure Admin Tools on your site."


[Urlredirection]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; URL Redirection
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_URLREDIRECTIONS="URL Redirection"
COM_ADMINTOOLS_TITLE_URLREDIRECTION_ADD="Add a URL Redirection"
COM_ADMINTOOLS_TITLE_URLREDIRECTION_EDIT="Edit a URL Redirection"

COM_ADMINTOOLS_URLREDIRECTIONS_EMPTYSTATE_TITLE="No URL Redirections have been created yet."
COM_ADMINTOOLS_URLREDIRECTIONS_EMPTYSTATE_CONTENT="URL Redirections allow you to redirect any SEF or non-SEF URL to any internal URL belonging to your site, or any external URL. Use it to provide continuity of your URLs after restructuring your site and / or creating short URLs for use on marketing material."
COM_ADMINTOOLS_URLREDIRECTIONS_EMPTYSTATE_BUTTON_ADD="Add a URL Redirection"

COM_ADMINTOOLS_URLREDIRECTIONS_TABLE_CAPTION="Table of URL redirections."

COM_ADMINTOOLS_REDIRECTION_ERR_NEEDS_DEST="You must specify the “Visiting this” URL"
COM_ADMINTOOLS_REDIRECTION_ERR_NEEDS_SOURCE="You must specify the “Takes you there” URL"
COM_ADMINTOOLS_REDIRECTION_ERR_NOITEMS="No redirections are specified yet. Use the New button to create one."

COM_ADMINTOOLS_REDIRECTION_LBL_DEST="Visiting this"
COM_ADMINTOOLS_REDIRECTION_LBL_DEST_DESC="This is a relative URL on your site. When someone visits it they will be redirected to the “Takes you there” URL below. It must not have the http:// or https:// protocol prefix, your domain name or a leading slash. Examples: <code>search/on/google</code> or <code>456-blog/123-my-article</code>. Please note that you cannot specify the fragment (the <code>#</code> sign in the URL and anything following it) since this is a client-side feature; your server does NOT see the fragment, therefore we cannot make a server-side redirection based on the fragment contents."
COM_ADMINTOOLS_REDIRECTION_LBL_SOURCE="Takes you here"
COM_ADMINTOOLS_REDIRECTION_LBL_SOURCE_DESC="This is the relative or absolute URL where the visitor will be taken to. This URL must be valid even if you turn off the redirection feature. It can be a URL to your own site or a different one. Examples: <code>https://www.example.com</code> or <code>blog/123-my-article</code>."
COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS="Keep URL Parameters"
COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS_DESC="Choose what to do with query string parameters in the visited URL. “None” ignores them and keeps the query string parameters from the ‘Takes you here’ URL, if any. “Override all” merges them with the query string parameters from the ‘Takes you here’ URL, overriding the latter even if they are set. “Add new” will add any query string parameters defined in the visted URL <em>as long as</em> they are NOT already defined in the ‘Takes you here’ URL."

COM_ADMINTOOLS_REDIRECTION_LBL_ORDER_SOURCE_ASC="Takes you here, ascending"
COM_ADMINTOOLS_REDIRECTION_LBL_ORDER_SOURCE_DESC="Takes you here, descending"
COM_ADMINTOOLS_REDIRECTION_LBL_ORDER_DEST_ASC="Visiting this, ascending"
COM_ADMINTOOLS_REDIRECTION_LBL_ORDER_DEST_DESC="Visiting this, descending"

COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS_SELECT="– Keep URL Parameters –"
COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS_OFF="None"
COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS_ALL="Override all"
COM_ADMINTOOLS_REDIRECTION_LBL_KEEPURLPARAMS_ADD="Add new"
COM_ADMINTOOLS_REDIRECTION_LBL_PUBLISHED_DESC="When set to Unpublished the redirection is disabled"

COM_ADMINTOOLS_REDIRECTION_LBL_PREFERENCE="Enable the URL Redirection feature?"
COM_ADMINTOOLS_REDIRECTION_LBL_PREFERENCE_SAVE="Save preference"
COM_ADMINTOOLS_REDIRECTION_LBL_PREFERENCE_SAVED="Your URL Redirection preference was saved"

COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_COPIED="%d URL Redirections were copied."
COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_COPIED_1="The URL Redirection was copied."

COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_DELETED="%d URL Redirections were deleted."
COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_DELETED_1="The URL Redirection was deleted."

COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_CHECKED_IN="%d URL Redirections were checked in."
COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_CHECKED_IN_1="The URL Redirection was checked in."

COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_PUBLISHED="%d URL Redirections were published"
COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_PUBLISHED_1="The URL Redirection was published"

COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_UNPUBLISHED="%d URL Redirections were unpublished"
COM_ADMINTOOLS_URLREDIRECTIONS_N_ITEMS_UNPUBLISHED_1="The URL Redirection was unpublished"

[Scanner]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Scanner Settings
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_SCANNER="Scanner Settings"

[Scans]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; PHP File Change Scanner
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_SCANS="PHP File Change Scanner"
COM_ADMINTOOLS_TITLE_SCAN_EDIT="Edit comment"

COM_ADMINTOOLS_SCANS_EMPTYSTATE_TITLE="No PHP File Change Scanner scans yet."
COM_ADMINTOOLS_SCANS_EMPTYSTATE_CONTENT="The PHP File Change Scanner lets you monitor your site for new and changed PHP files, as well as assess the likelihood that they are malicious. Run the scanner regularly — at the very least before and after every Joomla! and extension update — to monitor your site efficiently."
COM_ADMINTOOLS_SCANS_EMPTYSTATE_BUTTON_ADD="Start a new scan"

COM_ADMINTOOLS_LBL_SCANS_EMAIL_HEADING="File Scan results"
COM_ADMINTOOLS_LBL_SCANS_EMAIL_NOTHING_TO_REPORT="The PHP File Change Scanner has not detected and newly added, modified or suspicious files"
COM_ADMINTOOLS_LBL_SCANS_EMAIL_OVERVIEW="Overview"
COM_ADMINTOOLS_LBL_SCANS_EMAIL_SUBJECT="File scan results for %s"

COM_ADMINTOOLS_SCANS_TABLE_CAPTION="Table of PHP File Change Scanner runs."

COM_ADMINTOOLS_SCANS_ERR_FILE_TOO_LARGE="File too large; if this is a log file please exclude it from the scan. Size %s Mb"

COM_ADMINTOOLS_SCANS_LBL_SINCE="Scans since this date"
COM_ADMINTOOLS_SCANS_LBL_UNTIL="Scans until this date"
COM_ADMINTOOLS_SCANS_LBL_COMMENT="Comment"

COM_ADMINTOOLS_SCANS_LBL_STATUS_FAIL="Failed"
COM_ADMINTOOLS_SCANS_LBL_STATUS_RUN="Running"
COM_ADMINTOOLS_SCANS_LBL_STATUS_COMPLETE="Complete"

COM_ADMINTOOLS_SCANS_LBL_ORIGIN_BACKEND="Backend"
COM_ADMINTOOLS_SCANS_LBL_ORIGIN_CLI="CLI"
COM_ADMINTOOLS_SCANS_LBL_ORIGIN_JOOMLA="Joomla Scheduled Tasks"

COM_ADMINTOOLS_SCAN_LBL_ACTIONS="Actions &amp; Reports"
COM_ADMINTOOLS_SCAN_LBL_ACTIONS_NOREPORT="No report generated"
COM_ADMINTOOLS_SCAN_LBL_ACTIONS_VIEW="View Report"
COM_ADMINTOOLS_SCAN_LBL_ADDED="Added"
COM_ADMINTOOLS_SCAN_LBL_DELETED="Deleted"
COM_ADMINTOOLS_SCAN_LBL_MODIFIED="Modified"
COM_ADMINTOOLS_SCAN_LBL_SUSPICIOUS="Suspicious"
COM_ADMINTOOLS_SCAN_LBL_THREATNONZERO="Possible Threats"
COM_ADMINTOOLS_SCAN_LBL_TOTAL="Total Files"
COM_ADMINTOOLS_SCAN_LBL_CONFIGURE="Configure"
COM_ADMINTOOLS_SCAN_LBL_START="Scan Date"

COM_ADMINTOOLS_SCAN_LBL_MSG_CONFIGUREHELP="You can configure the PHP File Change Scanner in the component's <strong>Options</strong> page. The toolbar above has a button to open that page."
COM_ADMINTOOLS_SCAN_LBL_MSG_LASTSERVERRESPONSE="Last server response: %s seconds ago"
COM_ADMINTOOLS_SCAN_LBL_MSG_PLEASEWAIT="Please wait&hellip;"
COM_ADMINTOOLS_SCAN_LBL_MSG_PURGE="Purge file cache"
COM_ADMINTOOLS_SCAN_LBL_MSG_PURGE_COMPLETED="Scanned files cache cleared"
COM_ADMINTOOLS_SCAN_LBL_MSG_PURGE_ERROR="An error occurred while clearing the scanned files cache"
COM_ADMINTOOLS_SCAN_LBL_MSG_SCANINPROGRESS="Scan in progress"
COM_ADMINTOOLS_SCAN_LBL_MSG_SCANNOW="Scan Now"

COM_ADMINTOOLS_SCANS_N_ITEMS_DELETED="%d PHP File Change Scanner runs have been deleted."
COM_ADMINTOOLS_SCANS_N_ITEMS_DELETED_1="The PHP File Change Scanner run has been deleted."


[Scanalerts]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; PHP File Change Scanner Reports
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_SCANALERTS="PHP File Change Scanner Report #%u"
COM_ADMINTOOLS_TITLE_SCANALERTS_MAINPASSWORD="PHP File Change Scanner Reports"
COM_ADMINTOOLS_TITLE_SCANALERT_EDIT="PHP File Scanner &ndash; Report #%u &ndash; Examine file"

COM_ADMINTOOLS_TITLE_SCANALERT_ERR_NO_SUCH_SCAN="Scan #%d not found."
COM_ADMINTOOLS_SCANALERTS_TABLE_CAPTION="Table of new, modified or potentially dangerous files reported by the PHP File Change Scanner."

COM_ADMINTOOLS_SCANALERTS_LBL_CSV="Export CSV"
COM_ADMINTOOLS_SCANALERTS_LBL_PRINT="Print"

COM_ADMINTOOLS_SCANALERTS_LBL_SORT_THREATSCORE_ASC="Threat Score, ascending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_THREATSCORE_DESC="Threat Score, descending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_STATUS_ASC="Status, ascending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_STATUS_DESC="Status, descending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_PATH_ASC="File Path, ascending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_PATH_DESC="File Path, descending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_ACKNOWLEDGED_ASC="Marked Safe, ascending"
COM_ADMINTOOLS_SCANALERTS_LBL_SORT_ACKNOWLEDGED_DESC="Marked Safe, descending"

COM_ADMINTOOLS_SCANALERTS_LBL_FILENOTFOUND="The file <code>%s</code> no longer exists on your server."

COM_ADMINTOOLS_SCANALERTS_LBL_ACKNOWLEDGED="Marked safe"
COM_ADMINTOOLS_SCANALERTS_LBL_ACKNOWLEDGED_SELECT="– Marked safe –"
COM_ADMINTOOLS_SCANALERTS_LBL_ACKNOWLEDGED_SAFE="Marked safe"
COM_ADMINTOOLS_SCANALERTS_LBL_ACKNOWLEDGED_UNSAFE="Not marked safe"
COM_ADMINTOOLS_SCANALERTS_LBL_MARKSAFE="Mark Safe"
COM_ADMINTOOLS_SCANALERTS_LBL_MARKUNSAFE="Unmark Safe"
COM_ADMINTOOLS_SCANALERTS_LBL_MD5="Current checksum"
COM_ADMINTOOLS_SCANALERTS_LBL_PATH="File path"
COM_ADMINTOOLS_SCANALERTS_LBL_STATUS="Status"
COM_ADMINTOOLS_SCANALERTS_LBL_STATUS_SELECT="– Status –"
COM_ADMINTOOLS_SCANALERTS_LBL_STATUS_MODIFIED="Modified"
COM_ADMINTOOLS_SCANALERTS_LBL_STATUS_NEW="New"
COM_ADMINTOOLS_SCANALERTS_LBL_STATUS_SUSPICIOUS="Suspicious"
COM_ADMINTOOLS_SCANALERTS_LBL_THREAT_SCORE="Threat score"
COM_ADMINTOOLS_SCANALERTS_LBL_DIFF="Diff to the previous version"
COM_ADMINTOOLS_SCANALERTS_LBL_FILEINFO="File Information"
COM_ADMINTOOLS_SCANALERTS_LBL_SAVED="Scanned file status changed"
COM_ADMINTOOLS_SCANALERTS_LBL_SCANDATE="Scan date"
COM_ADMINTOOLS_SCANALERTS_LBL_SOURCE="Current file source"
COM_ADMINTOOLS_SCANALERTS_LBL_SOURCE_NOTE="Please note that it may be different than the source scanned"
COM_ADMINTOOLS_SCANALERTS_LBL_MARKALLSAFE="Mark All as Safe"

COM_ADMINTOOLS_SCANALERTS_N_ITEMS_PUBLISHED="%d files were marked as Safe."
COM_ADMINTOOLS_SCANALERTS_N_ITEMS_PUBLISHED_1="The file was marked as Safe."
COM_ADMINTOOLS_SCANALERTS_N_ITEMS_UNPUBLISHED="%d files are no longer marked as Safe."
COM_ADMINTOOLS_SCANALERTS_N_ITEMS_UNPUBLISHED_1="The file is no longer marked as Safe."

[Seoandlinktools]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; SEO and Link Tools
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_SEOANDLINKTOOLS="SEO and Link Tools"

COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_CONFIGSAVED="SEO and Link settings have been saved"
COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_OPTGROUP_MIGRATION="Link Migration"
COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_OPTGROUP_TOOLS="Tools"
COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_OPT_LINKMIGRATION="Enable link migration"
COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_OPT_LINKMIGRATIONLIST="Old locations (domain names)"
COM_ADMINTOOLS_SEOANDLINKTOOLS_LBL_OPT_LINKMIGRATIONLIST_TIP="Enter one domain per entry, without the http prefix. If you were using a subdirectory include it without a trailing slash. For example, <code>www.example.com</code> and <code>www.example.com/joomlasite</code> are correct, whereas <s><code>https://www.example.com</code></s> and <s><code>https://www.example.com/joomlasite/</code></s> are <strong>INCORRECT</strong>."

[Webapplicationfirewall]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Web Application Firewall
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_WAF="Web Application Firewall"

[Wafdenylist]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; WAF Deny List
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_WAFDENYLISTS="WAF Deny List"
COM_ADMINTOOLS_TITLE_WAFDENYLIST_EDIT="Edit a WAF Deny List rule"
COM_ADMINTOOLS_TITLE_WAFDENYLIST_ADD="Add a WAF Deny List rule"

COM_ADMINTOOLS_WAFDENYLIST_EMPTYSTATE_TITLE="No WAF Deny List rules have been created yet."
COM_ADMINTOOLS_WAFDENYLIST_EMPTYSTATE_CONTENT="WAF Deny List rules allow you to block requests to your site matching specific request criteria. You can use them to prevent known security issues in older component versions you cannot upgrade just yet."
COM_ADMINTOOLS_WAFDENYLIST_EMPTYSTATE_BUTTON_ADD="Add a WAF Deny List rule"

COM_ADMINTOOLS_WAFDENYLIST_TABLE_CAPTION="Table of WAF Deny List rules."

COM_ADMINTOOLS_WAFDENYLISTS_LBL_ERR_ALLEMPTY="You must provide at least one of Component, View, Task or Query for the WAF Deny List rule to be valid."

COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION="Application"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_DESC="Which Joomla! application should this rule apply to. Frontend is the public frontend of yoru site, Backend is the administrator backend interface (<code>/administrator/</code> URLs), API is the Joomla API application (<code>/api/</code> URLs). “(Any)” applies the rule in all applications."
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_SELECT="– Application –"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_BOTH="(Any)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_SITE="Frontend"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_ADMIN="Backend"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_APPLICATION_API="API"

COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB="HTTP Verb"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_DESC="Which HTTP verb to apply this rule (GET, POST etc. etc.). Your site's front- and backend typically use GET to display pages or retrieve content via JavaScript requests; and POST to submit forms or otherwise submit content back to the site. The API application typically uses GET, POST, DELETE and PATCH requests."
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_ALL="(Any)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_GET="GET"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_POST="POST"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_PUT="PUT"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_DELETE="DELETE"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_PATCH="PATCH"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_HEAD="HEAD"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VERB_TRACE="TRACE"

COM_ADMINTOOLS_WAFDENYLISTS_LBL_OPTION="Component"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_OPTION_ALL="(All)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_OPTION_DESC="The name of the Joomla component this rule matches. Leaving empty (“– Component –”) matches all components."
COM_ADMINTOOLS_WAFDENYLISTS_LBL_OPTION_SELECT="– Component –"

COM_ADMINTOOLS_WAFDENYLISTS_LBL_VIEW="View Name"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VIEW_DESC="The component's view (component area) or controller name which need to be present in the URL for this rule to match. Turn off SEF URLs and you will see either <code>view=ViewName</code> or <code>task=ViewName.TaskName</code> where <var>ViewName</var> is the View Name you need to enter here. Leaving empty matches all views."
COM_ADMINTOOLS_WAFDENYLISTS_LBL_VIEW_ANY="(All)"

COM_ADMINTOOLS_WAFDENYLISTS_LBL_TASK="Task"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_TASK_ANY="(All)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_TASK_DESC="Which task (a command for a specific component area) to apply this rule. Turn off SEF URLs and you will see either <code>task=TaskName</code> or <code>task=ViewName.TaskName</code> where <var>TaskName</var> is the Task you need to enter here. Leaving empty matches all views."

COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY="Query Parameter"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_DESC="Which query string parameter's content will be used to match this rule e.g. <code>id</code>. Leave blank to match the rule regardless of query parameter content. Note that the query content matching is only ever applied <strong>after</strong> Joomla has converted a SEF URL to its non-SEF format. This means that some query parameters may not be visible to you — even though they are visible to Joomla and Admin Tools, therefore can result in the request being blocked by the Web Application Firewall — unless you turn off SEF URLs."

COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE="Query Parameter filter type"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE_ANY="(All)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE_DESC="Choose how the Query Parameter will be matched. “RegEx” means that the Query Parameter field contains a <a href=\"https://www.php.net/manual/en/reference.pcre.pattern.syntax.php\" target=\"_blank\">PHP regular expression</a> to match the query parameter contents. You can negate a regular expression by prefixing it with an exclamation mark(<code>!</code>). “Exact” means that the query parameter name must match the Query Parameter field exactly as entered, including lower- and uppercase letters. “Partial” means that the query parameter name must include the Query Parameter you entered e.g. Query Parameter “bar” will match any of the following query parameter names: “re<em>bar</em>”, “<em>bar</em>tender” and “<em>bar</em>”."

COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE_EXACT="Exact"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE_PARTIAL="Partial"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_TYPE_REGEX="RegEx"

COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_CONTENT="Query content"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_CONTENT_ANY="(Any content)"
COM_ADMINTOOLS_WAFDENYLISTS_LBL_QUERY_CONTENT_DESC="Leave blank to match the rule regardless of the query content. Otherwise, provide a <a href=\"https://www.php.net/manual/en/reference.pcre.pattern.syntax.php\" target=\"_blank\">PHP regular expression</a>; if it matches the query parameter content the rule matches. You can negate a regular expression by prefixing it with an exclamation mark(<code>!</code>)."

COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_COPIED="%d WAF Deny List rules were copied."
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_COPIED_1="The WAF Deny List rule was copied."
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_DELETED="%d WAF Deny List rules were deleted."
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_DELETED_1="The WAF Deny List rule was deleted."
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_PUBLISHED="%d WAF Deny List rules were published"
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_PUBLISHED_1="The WAF Deny List rule was published"
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_UNPUBLISHED="%d WAF Deny List rules were unpublished"
COM_ADMINTOOLS_WAFDENYLISTS_N_ITEMS_UNPUBLISHED_1="The WAF Deny List rule was unpublished"

[Configurewaf]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Configure WAF
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_CONFIGUREWAF="Configure WAF"

COM_ADMINTOOLS_CONFIGUREWAF_ERR_NOPLUGINACTIVE="You have to publish the \"System - Admin Tools\" plug-in before any of these settings have any effect."
COM_ADMINTOOLS_CONFIGUREWAF_ERR_NOPLUGINACTIVE_DOIT="Click here to go to the Plugins Manager"
COM_ADMINTOOLS_CONFIGUREWAF_ERR_NOPLUGINEXISTS="You have to install and publish the \"System - Admin Tools\" (plg_admintools) plug-in before any of these settings have any effect. You may try to reinstall Admin Tools, twice in a row, without uninstalling before or in between to force Joomla! to install the missing plugin."
COM_ADMINTOOLS_CONFIGUREWAF_ERR_MAINPHPRENAMED_KNOWN="You have renamed the <code>plugins/system/admintools/services/provider.php</code> file to <code>%s</code>. As a result Admin Tools <strong>does not</strong> protect your site. If you did this intentionally, to fix some problem you were experiencing, please remember to rename the file back to provider.php. In most cases you can click the link below to do it automatically."
COM_ADMINTOOLS_CONFIGUREWAF_ERR_MAINPHPRENAMED_DOIT="Rename the file back to provider.php"
COM_ADMINTOOLS_CONFIGUREWAF_ERR_MAINPHPRENAMED_UNKNOWN="You have renamed the <code>plugins/system/admintools/services/provider.php</code> file. As a result Admin Tools <strong>does not</strong> protect your site. If you did this intentionally, to fix some problem you were experiencing, please remember to rename the file back to provider.php."
COM_ADMINTOOLS_CONFIGUREWAF_ERR_PLUGINNOTLOADED="The System - Admin Tools plugin is not loaded. Unfortunately we cannot determine the cause. Some file may be missing or corrupt. We strongly recommend reinstalling Admin Tools, twice in a row, without uninstalling before or in between to force Joomla! to install and overwrite any missing or corrupt files."

COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_DOMAIN="Domain name"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_FILEPATH="File path"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_USER="User"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_USERNAME="Username"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_TMPL="Template keyword"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_URLPATH="URL Path"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_IP="IP Address"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_COMMON_DESCRIPTION="Description"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_ALERT_WORKS="User self-service activation is enabled on your site. Automatically deactivated users will be emailed instructions to re-activate their user account."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ALERT_ADMINACTIVATION="User activation is set to <strong>Admin</strong>, this means that the new activation email will be sent to the Super Users and they will have to reactivate the user."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ALERT_NOREGISTRATION="User registration on your site is disabled, therefore Admin Tools can't deactivate users."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ALERT_NOUSERACTIVATION="User activation on your site is disabled, therefore Admin Tools can't deactivate users"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE="Away Schedule"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE_FROM="Away Schedule from (hh:mm)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE_TIMEZONE_HEAD="Your server reports that the current time is <strong>%s</strong> (<em>%s</em> timezone)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE_TIMEZONE="<p>The Away Schedule times must be given in the %s time zone. You can change this time zone in Joomla's Global Configuration page. If the current time still doesn't look right please ask your host to check their server's time and their PHP and operating system time zone settings.</p>"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE_TIP="Away Schedule disables access to your site's administrator area during the time period you specify in the from and to fields. This is useful when you are the sole administrator of the site and want to make sure that while you are asleep / away nobody can access your site's administrator section. The time must be given in the Server Time zone you have set up in your site's Global Configuration. The time zone and the current time in this timezone is printed in the message under the Away Schedule From field for your convenience"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_AWAYSCHEDULE_TO="Away Schedule to (hh:mm)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_CONFIGSAVED="The Web Application Firewall's configuration was saved."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_CONFIGNOTSAVED="There were errors trying to save the Web Application Firewall's configuration."

COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINLOGINFOLDER="Change administrator login directory to"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINLOGINFOLDER_TIP="For instance, if you enter the word <code>test</code> here you will only be able to access your site's administrator area with a URL similar to <code>http://www.example.com/test</code>. If you try to access it as <code>http://www.example.com/administrator</code> you will be redirected to the site's home page. After visiting the secret URL with your browser you will be able to also visit <code>http://www.example.com/administrator</code> without being blocked until your session expires. If you do not wish to use this feature, leave this field blank. Please keep in mind that this feature requires the <strong>SEF URLs</strong> and <strong>Use URL rewriting</strong> options in Joomla's Global Configuration page to be both set to Yes."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINLOGINFOLDER_NOTICE_HEAD="This feature is experimental and unsupported"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINLOGINFOLDER_NOTICE_TEXT="On some sites the <strong>Custom administrator login folder</strong> may perform erratically, not work at all, or make it impossible to log in. We are aware and there is no workaround for this. For this reason this feature is provided <strong>WITHOUT SUPPORT</strong>. Please read the documentation for more information."

COM_ADMINTOOLS_CONFIGUREWAF_LBL_CUSTOMMESSAGE_DESC="This message will be shown to users when their request is deemed suspicious of a security violation. Keep it short and courteous. Leave it blank to use the default message."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_CUSTOMMESSAGE_HEADER="Customisation"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_CUSTOMMESSAGE_LABEL="Custom message"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_NUM="Number of failed logins"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_NUM_TIP="Users will be deactivated when this many failed login attempts occur for them in the period of time configured by the next two options"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_NUMFREQ="Failed logins period"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_NUMFREQ_TIP="Users will be deactivated when at least as many failed login attempts as entered above happen in up to this much time. The unit of time measurement (seconds, minutes, hours, days) is specified in the next option."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_FREQ="Unit of time measurement"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_DEACTIVATE_FREQ_TIP="Sets the unit of time measurement for the Failed logins period field."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_FREQSECOND="Seconds"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_FREQMINUTE="Minutes"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_FREQDAY="Days"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_FREQHOUR="Hours"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_EMAILAFTERIPAUTOBAN="Email this address after an automatic IP ban"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_EMAILAFTERIPAUTOBAN_TIP="Admin Tools can optionally send you an email when an IP is automatically banned, to the email address entered in this field. Leave this field empty (default) to disable this feature."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_GENERATOR="Generator tag"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_GENERATOR_TIP="Enter a custom generator meta tag value, or leave blank to use an automatically generated value"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_HTACCESSTIP="For further protection of your site, also use the .htaccess Maker feature of this component"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_IPLOOKUPSCHEME_HTTP="http://"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_IPLOOKUPSCHEME_HTTPS="https://"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_IPLOOKUP_DESC="Link to an IP lookup service. {ip} will be substituted with the IP address. Default: http://ip-lookup.net/index.php?ip={ip}"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_IPLOOKUP_LABEL="IP Lookup Service"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NEVERBLOCKIPS="Never block these IPs"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NEVERBLOCKIPS_TIP="Enter the IP addresses which should never be automatically blocked, regardless of your Auto-ban settings. You can use single IPv4 and IPv6 addresses (e.g. <em>127.0.0.1</em> and <em>::1</em>), IPv4 ranges (e.g. <em>127.0.0.1-127.0.0.10</em>), implied IPv4 range notation (<em>127.0.0.</em> for the entire 127.0.0.1 to 127.0.0.255 block) and IPv4/IPv6 CIDR block notation (e.g. <em>127.0.0.0/8</em> for IPv4 or <em>2001:db8::/32</em> for IPv6)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_ACTIVEFILTERING="Request Filtering"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_BASIC="Basic Security"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_BASICSETTINGS="Basic Features"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_EXCEPTIONS="Exceptions"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_FINGERPRINTING="Cloaking"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_JHARDENING="Hardening Options"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPTGROUP_LOGGINGANDREPORTING="Logging & Reporting"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_404SHIELD="404 Shield"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_404SHIELD_ENABLE="Enable 404 Shield"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_404SHIELD_ENABLE_TIP="Click to enable or disable the feature 404 Shield"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_404SHIELD_TIP="This feature treats 404 Not Found errors as a reason to block a request when these occur on URLs known to be used by hackers to scan your site for vulnerabilities. For example, when a hacker tries to access the WordPress login page even though you have a Joomla! site"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ADMINPW="Administrator secret URL parameter"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ADMINPW_TIP="For example, if you enter 'test', then you will only be able to access your administrator area by typing the URL <code>http://www.example.com/administrator/index.php?test</code>. <strong>WARNING! IT MUST START WITH A LETTER, NOT A NUMBER</strong>. For better compatibility across servers, please use lowercase ASCII characters and numbers only (a-z, 0-9)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ADMINPW_TIP_LONG="The Administrator Secret URL Parameter can only consist of lowercase and uppercase latin letters without accents or diacritics (a-z and A-Z), numbers 0-9, dashes, and underscores. The first character cannot be a dash or underscore. It must be 4 to 64 characters long."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ADMINPW_INVALID="The Adminstrator Secret URL Parameter is invalid. Please remember it can only consist of lowercase and uppercase latin letters without accents or diacritics (a-z and A-Z), numbers 0-9, dashes, and underscores. The first character cannot be a dash or underscore. It must be 4 to 64 characters long."

COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE="Browser cookie override for the administrator secret URL parameter"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE_TIP="Should I set a browser cookie on successful administrator login which allows the browser to access the administrator login page anytime in the next 30 days even without providing the administrator secret URL parameter? The cookie is invalidated if you use Joomla!'s Logout feature or change the user's password. Please read the documentation for more information. If unsure, set to “Enabled, notify when used”."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE_OFF="Disabled"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE_ON="Enabled"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE_ON_WARN="Enabled, notify when used"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_ADMINPW_COOKIE_ON_MAXWARN="Enabled, remind to use the full URL"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ALLOWSITETEMPLATE="Allow site templates"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ALLOWSITETEMPLATE_TIP="Enabling this option partially overrides the previous option (the blocking of template=foo in the URL). If the template= URL query parameter specifies the name of a template which exists in your template directory, then it will be allowed without causing request to be blocked. This is required only on sites which are using more than one template at the same time."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ANTISPAM="Anti-spam filtering based on Bad Words list"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ANTISPAM_TIP="When enabled, all requests containing at least one word in the <a href='%s'>Bad Words</a> list will be blocked."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BBHTTPBLKEY="<a href='http://www.projecthoneypot.org/httpbl_configure.php' target='_blank'>Project Honeypot</a> HTTP:BL Key"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BBHTTPBLKEY_TIP="Enter your HTTP:BL key. You can sign up for Project Honeypot and get your key at <a href='http://www.projecthoneypot.org/httpbl_configure.php'>http://www.projecthoneypot.org/httpbl_configure.php</a>."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKEDEMAILDOMAINS="Email domains"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKEDEMAILDOMAINS_TIP="Enter one domain per entry, without a protocol e.g. <code>example.com</code> but NOT <s><code>https://www.example.com</code></s>. Admin Tools will allow or block registration accordingly to the above field. Leave it empty to disable any restriction during user registration."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES="Block common usernames"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES_TIP="When enabled, Admin Tools will block the creation of a user whose username is inside the default blocking list (ie admin, ceo, manager etc.)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES_ALLOW="Username explicitly allowed"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES_ALLOW_TIP="List of usernames that are explicitly allowed, one per line"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES_FORBID="Usernames explicitly forbidden"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_BLOCKUSERNAMES_FORBID_TIP="List of usernames that are explicitly forbidden, one per line"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORACTION="Action for configuration monitoring"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORACTION_BLOCK="Block"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORACTION_EMAIL="Email"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORACTION_TIP="What do you want to do when either global or component configuration is enabled and a change is detected in the configuration. 'Email' will simply send a warning email to the email addresses you've configured to receive emails about blocked requests and only if you have explicitly configured that email addresses. The changes in configuration will go through. 'Block' will treat these changes as a reason to block the request. The changes in configuration will NOT go through."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORCOMPONENTS="Monitor component configuration"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORCOMPONENTS_TIP="When this is enabled and someone tries to change the configuration of any core Joomla! or third party component (what you see when you click Options in a component's toolbar) from the back-end of your site you will either be notified or they will get blocked (depending on your settings below)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORGLOBAL="Monitor Global Configuration"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONFIGMONITORGLOBAL_TIP="When this is enabled and someone tries to change the Global Configuration of Joomla!, either from the back-end or the front-end, you will either be notified or they will get blocked (depending on your settings below)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONSOLEWARN="Warn about self XSS"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CONSOLEWARN_TIP="Display a message in browser console to warn the user to avoid running any command inside it. This can lead to hacking yourself (a.k.a. Self XSS attacks) and steal your account data."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CRITICALFILES="Monitor Critical Files"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CRITICALFILES_GLOBAL="Monitor these files for changes"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CRITICALFILES_GLOBAL_TIP="Monitor the following files (one per entry) for changes. If a change is detected you will be notified by email. The file paths are relative to your site's root."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CRITICALFILES_TIP="Critical files commonly modified by hackers (index.php, administrator/index.php and the index.php, error.php and component.php of all templates installed on the site) will be monitored for changes on every page load. If a change is detected you will be notified by email. This usually lets you get an ahead warning in case of a successful hacking attempt."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CUSTGENERATOR="Customise the generator meta tag"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_CUSTGENERATOR_TIP="All Joomla! installations set the meta generator tag, a piece of HTML in the header of all pages, to advertise the fact that your site is running on Joomla!. This information is cached by search engines and is exploited by attackers to deduce that your site is running Joomla! when looking for potential targets. Enabling this option allows you to set a custom value for the generator tag in the next option. Be inventive!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DEACTIVATEUSERS="Deactivate users on failed login"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DEACTIVATEUSERS_TIP="Admin Tools can optionally deactivate existing user accounts when there are multiple failed attempts to log in using their username, protecting user accounts from brute force attacks. In here you can specify the number of failed logins and the time period these have to occur before the user is deactivated, e.g. 3 failed logins in 1 minute. Setting the number of failed logins to 0 deactivates this feature."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DFISHIELD="Direct File Inclusion shield (DFIShield)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DFISHIELD_TIP="When this option is enabled, Admin Tools will search the request parameters for anything which looks like a file path. If one is found, it will be scanned. If it is found to contain PHP code, the request will be rejected."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEPWDRESET="Disable password reset for specific User Groups"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEPWDRESET_TIP="Blocks users belonging in one of the selected User Groups from requesting a password reset using the “Forgot your password?” feature in the frontend of the site."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEPWDRESET_GROUPS="User groups blocked from resetting the password"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEPWDRESET_GROUPS_TIP="Users in these user groups will not be allowed to request a password reset. You do not need to add groups with Super User permissions; these are blocked automatically by Joomla! itself."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS="Prevent forgotten backend users from logging in"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_ACTION="Login prevention method"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_ACTION_BLOCK="Block"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_ACTION_RESET="Force password reset"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_ACTION_TIP="Choose how Admin Tools will enforce login prevention for the forgotten users. “Block” will permanently block the user; a Super User will have to unblock them manually. “Force passwrod reset” (recommended) will force the user to reset their password next time they log in and won't allow them to do anything else on the site until they complete the password reset."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_FREQ="Check every [minutes]"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_FREQ_TIP="Run this check at most every this many minutes."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_GROUPS="Backend user groups"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_GROUPS_TIP="Which user groups with backend access does this feature apply to? Select no groups to apply to all user groups with login access to your site's backend."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_HEAD="Forgotten backend users"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_MAXDAYS="Maximum number of days since last login"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_MAXDAYS_TIP="Users who belong in the user groups specified above and who have not logged in for at least this many days will be prevented from logging in."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_PROTECTED="Protected users"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_PROTECTED_TIP="These users will never be blocked. It's recommended that you only place a <strong>very</strong> limited number of user accounts in this list. Typically, this should be the site owner's and the site developer's user accounts, nobody else (especially <strong>NOT</strong> other staff members who may leave while their user accounts were left behind, i.e. the whole point of this protection)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_DISABLEOBSOLETEADMINS_TIP="Prevent users with backend access who have not logged in for a very long time from logging into the site. Most likely these are obsolete users you forgot to remove and their password got compromised in the meantime."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILADMINFAILEDLOGIN="Email this address on failed administrator login"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILADMINFAILEDLOGIN_TIP="Enter an email address to be notified upon an unsuccessful login of anyone in your site's administrator backend. Leave blank to not be sent a notification. Make sure your site can send out emails first!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILADMINLOGIN="Email this address on successful backend login"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILADMINLOGIN_TIP="Enter an email address to be notified upon a successful login of anyone in your site's administrator backend. Leave blank to not be sent a notification. Make sure your site can send out emails first!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILBREACHES="Email this address on blocked request"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILBREACHES_TIP="Enter an email address to be notified upon any request blocked on your site. Leave blank to not be sent a notification. Make sure your site can send out emails first!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILPHPEXCEPTIONS="Email PHP Exceptions to this address"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILPHPEXCEPTIONS_TIP="Whenever an unhandled PHP exception is raised (i.e. an error on a database query), Admin Tools will send an email containing all the details (time, file and line raising the exception) for later debugging."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILTHROTTLE="Enable blocked requests email throttling"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_EMAILTHROTTLE_TIP="When enabled the frequency of emails sent by Admin Tools can be throttled down. See the Email Templates for the maximum email frequency settings."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_FILTER_REGISTRATION="Filter user registration by email"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_FILTER_REGISTRATION_ALLOW="Allow"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_FILTER_REGISTRATION_BLOCK="Block"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_FILTER_REGISTRATION_TIP="Choose if Admin Tools should only allow or block email domains from the list below"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLBLOCKSUSPICIOUS="Also block suspicious IPs, not just confirmed spammers"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLBLOCKSUSPICIOUS_TIP="Sometimes Project Honeypot is not sure if an IP belongs to a spammer or it's a hapless chap who clicked on the wrong link. In this case the IP is marked as \"suspicious\". The default behaviour is to not block these IPs. However, if you are receiving a lot of spam it's a good idea to enable this feature and block even \"suspicious\" IPs. Ultimately, some unfortunate users will be inadvertently blocked, so use this option with caution!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLENABLE="Enable HTTP:BL filtering"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLENABLE_TIP="Enables the integration with <a href='http://www.projecthoneypot.org'>Project Honeypot</a>. <strong>IMPORTANT</strong>: You need to register to Project Honeypot, get a key and enter it in the next option for this feature to work."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLMAXAGE="Maximum age of accepted HTTP:BL results (days)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLMAXAGE_TIP="Project Honeypot reports when was the last time this IP was caught sending spam messages. The older this is (the higher the age is), the less likely is that this IP is still used by a spammer. You can chose here what will be the maximum reported age that will be blocked. The default value of 30 means that IPs which have submitted a spam message in the last 30 days will be blocked."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLTHRESHOLD="Minimum Threat Rating to block"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_HTTPBLTHRESHOLD_TIP="Project Honeypot uses a logarithmic “threat rating” to rank the possibility of a specific IP being a spammer. This options defines the minimum threat level an IP must have before it's blocked. A value of 25 means that this IP has submitted 100 spam messages on Project Honeypot's spam catching honeypots and is usually a safe indication that it belongs to a spammer. Do note that the rating is logarithmic. A value of 50 means 1,000 spam messages and a value of 75 means one million spam messages. Do not set it to values over 50, as you will most likely never block any spammer at all. The default value is 25 (100 spam messages detected from that IP address)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_IPBL="Disallow site access to IPs in the IP Disallow List"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_IPBL_TIP="When enabled, if the visitor's IP is in the IP Disallow List (see the IP Disallow List< feature) they will immediately get a 403 Forbidden error message upon trying to access your site."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_IPWL="Allow administrator access only to IPs in Exclusive Allow IP List"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_IPWL_TIP="When enabled, only IPs in the Exclusive Allow IP List (see the Administrator Exclusive Allow IP List feature) will be allowed to access the administrator area of the site. All other attempts to access the administrator pages will be redirected to the site's home page. Be careful when using this feature! If you haven't added your own IP to the Exclusive Allow IP List you will get locked out of your administrator area!"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ITEMIDSHIELD="ItemidShield"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ITEMIDSHIELD_TIP="When enabled, Admin Tools will block any invalid value for the ItemId URL param or attempt to clean it to a valid integer value"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ITEMIDSHIELD_OFF="Off"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ITEMIDSHIELD_BLOCK="Block"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ITEMIDSHIELD_CLEAN="Clean"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SUSPICIOUS_PARAMS="Block Suspicious Core Parameters"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SUSPICIOUS_PARAMS_TIP="Blocks requests with suspicious values in core Joomla! query string parameters, such as <code>option</code>, <code>view</code>, <code>task</code>, etc."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LEAKEDPWD="Warn about use of well-known passwords"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LEAKEDPWD_GROUPS="User groups to check for well-known passwords"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LEAKEDPWD_GROUPS_TIP="Admin Tools will check for well-known passwords only users belonging to those groups (deafult to Super Users)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LEAKEDPWD_TIP="When this option is enabled, Admin Tools will connect to the Have I Been Pwned database and check if the hash of the current password is known. If a match is found, the user will be blocked from using an insecure password."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGBREACHES="Log blocked requests"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGBREACHES_TIP="It is suggested to keep this option enabled. When enabled, all potential security breaches —blocked by Admin Tools— will be logged in the database and made available under the Blocked Requests Log tool."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGFILE="Keep a debug log file"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGFILE_TIP="Admin Tools can optionally keep a log file inside your configured Joomla log folder. When this option is enabled an entry is added to the log file every time a request is blocked. This entry contains additional information useful for troubleshooting, including a full dump of the request data. This means that you will potentially be storing personally identifiable or sensitive information in an unencrypted file. You are advised to only turn this option on when you are troubleshooting an otherwise elusive problem and turn this option back off when you've collected enough information to address the problem."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGUSERNAMES="Log usernames"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_LOGUSERNAMES_TIP="When enabled, Admin Tools will include the username while tracking failed logins (see above). WARNING! We strongly suggest to keep this option disabled to avoid issues with GDPR"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_MUASHIELD="Malicious User Agent block (MUAShield)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_MUASHIELD_TIP="Many hackers will try to access your site using a browser configured to send malicious PHP code in its user agent string (a small piece of text used to describe the browser to your server). The idea is that buggy log processing software will parse it and allow the hacker to gain control of your website. When enabled, this feature allows Admin Tools to detect such attacks and block the request."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NOFESALOGIN="Forbid frontend Super Administrator login"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NOFESALOGIN_TIP="When enabled, it will not be possible for Super Administrators to log in to your site's frontend. This is a security precaution against password brute forcing. Even users with Super User privileges will not be able to log the frontend of your site."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWADMINS="Disable editing user properties"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWADMINS_TIP="When enabled, trying to modify the settings of an existing or create a new a Manager, Administrator or Super Administrator will fail."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWADMINS_GROUPS="Disable editing user properties for these user groups"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWADMINS_GROUPS_TIP="Which user groups with backend access does this feature apply to? If you select no groups, Admin Tools will disable editing user properties for all users who have login access to the backend of your site."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWFRONTENDADMINS="Disable creating / editing users from the frontend"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWFRONTENDADMINS_TIP="You should normally be unable to create a new user with administrative backend login privileges from the public frontend. When this option is enabled it will treat attempts to create this kind of accounts as hacking attempts and block them from executing. This addresses some of the most notorious zero day attacks in Joomla! which took place between 2015 and 2016."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWFRONTENDADMINS_GROUPS="Disable creating / editing users in these groups from the frontend"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_NONEWFRONTENDADMINS_GROUPS_TIP="Which user groups with backend access does this feature apply to? If you select no groups, Admin Tools will disable creating or editing users from the backend for all users who have or would gain login access to the backend of the site."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_PHPSHIELD="PHP stream wrappers block (PHPShield)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_PHPSHIELD_TIP="Some hackers will try to use the so-called PHP stream wrapper (they look like URLs beginning with php://, phar:// etc etc) to surreptitiously manipulate files of your site, bypassing the regular file upload controls built into Joomla!. When this option is enabled, Admin Tools will block every request which includes text matching any of the PHP stream wrappers commonly used by hackers."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_REASONS_NOEMAIL="Do not send email notifications for these reasons"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_REASONS_NOEMAIL_TIP="Requests blocked by these reasons will not result in an email being sent to the email address specified in <em>Email this address on blocked request</em>"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_REASONS_NOLOG="Do not log these reasons"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_REASONS_NOLOG_TIP="Requests blocked by these reasons will not be logged. As a result, IPs triggering a blocked request repeatedly for this reason will not be automatically banned from your site. Moreover, as there is no log, it will be impossible to tell why someone is being blocked from accessing your site when they trigger one of those reasons."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_RESETJOOMLATFA="Disable Joomla!'s Two-Factor Authentication on password reset"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_RESETJOOMLATFA_TIP="When enabled, Admin Tools will disable the Joomla! Two Factor Authentication configuration for a user when they are resetting their password. This only applies to the built-in Joomla! 3.2 and later Two Factor Authentication feature, not the Two Factor Authentication feature of Admin Tools."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_RFISHIELD="Remote File Inclusion block (RFIShield)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_RFISHIELD_TIP="Some hackers will try to force a vulnerable extension into loading PHP code directly from their server. This is done by passing an http(s):// or ftp:// URL in their request, pointing to their malicious site. When this option is enabled, Admin Tools will look for such cases, try to fetch the remote URL and scan its contents. If it is found to contain PHP code, it will block the request."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SAVEUSERSIGNUPIP="Save user sign-up IP in User Notes"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SAVEUSERSIGNUPIP_TIP="When enabled, the IP new users signed up from will be stored as User Notes. Users created through the backend will not have their IP saved as a User Note because it makes no sense to do so (it's an administrator registering the user account on their behalf). Third party components creating new user accounts may also not trigger the plugin event."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SAVEUSERSIGNUPIP_CATEGORY="User Notes category"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SAVEUSERSIGNUPIP_CATEGORY_TIP="Select the User Notes Categories where Admin Tools should save user IP, default to Uncategorized"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SELFPROTECT="Defend against plugin deactivation"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SELFPROTECT_TIP="When enabled, Admin Tools will prevent back-end users from trying to disable (unpublish) the plugin. This means that you will also be unable to unpublish the plugin until you disable this option! Moreover please note that this has no effect against someone editing your database directly; or renaming or deleting the files of the Admin Tools system plugin (the <code>plugins/system/admintools</code> directory on your site). It also does not protect against uninstallation of Admin Tools because only Super Users can do that by default. If an attacker gains Super User privileges, them disabling Admin Tools is the least of your worries."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SESSIONSHIELD="PHP session data poisoning protection (SessionShield)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SESSIONSHIELD_TIP="Prevents malicious input data which can be used to trick PHP's internal session handler into executing arbitrary code when it's restoring the user session. CAUTION: It <em>may</em> block some legitimate requests as well."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SQLISHIELD="SQLiShield protection against SQL injection attacks"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SQLISHIELD_TIP="When enabled, Admin Tools will try to detect common SQL injection attacks against your site and block them."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SUPERUSERSLIST="Monitor Super User accounts"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_SUPERUSERSLIST_TIP="Admin Tools will keep track of the user accounts with Super User access. If a new Super User is added outside of Joomla's Users page you will be notified by email. Moreover, the detected new Super User accounts will be automatically blocked. Users created or added by other Super Users in the backend of the site using Joomla's Users page will NOT be blocked by this feature. Please use the &ldquo;Disable editing backend users' properties&rdquo; feature to prevent this."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TEMPLATE="Block template=foo site template switch"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TEMPLATE_TIP="Another Joomla! hidden feature is the ability to switch between installed templates by passing a special URL parameter. For instance, if you want to apply the Beez5 template, just pass the parameter <code>?template=beez5</code>"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TMPL="Block tmpl=foo system template switch"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TMPLWHITELIST="List of allowed tmpl= keywords"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TMPLWHITELIST_TIP="One tmpl keyword per entry. The component and system entries are always added, regardless of whether you explicitly add them here."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TMPL_TIP="One of the lesser known Joomla! features are its system templates. Whenever an error occurs or you put your site offline, Joomla! loads the respective system template. Passing the name of the template in the URL by appending, say, ?tmpl=offline allows you to test those templates without having to actually produce an error or put your site off-line. Enabling this option will turn off this hidden Joomla! feature. Do note that tmpl=system and tmpl=component must be permitted (see next option), as they are required by some extensions to work."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TRACKFAILEDLOGINS="Treat failed logins as a reason for blocking the request"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TRACKFAILEDLOGINS_TIP="When enabled, failed login attempts of any kind of user (even simple registered users) count as a valid reason to block the request and are being logged in Admin Tools' Blocked Request Log. There is a very useful implication to that. Since they count as reasons to block a request they also count towards the limit you set up in the automatic IP blocking. Therefore, after a number of failed login attempts, the user's IP will be automatically blocked for the duration you have set up."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TROUBLESHOOTEREMAIL="Send troubleshooting email on administrative functions"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_TROUBLESHOOTEREMAIL_TIP="Sends an email to the currently logged in backend user whenever they take an Admin Tools administrative function which may result in them getting blocked out of the site or the site no longer working properly. The email contains links to the troubleshooting articles which help them rectify the issue and restore the site back to its working state. You are very advised to keep this feature enabled. Following the troubleshooting information is far faster than waiting for a reply back from our support."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_USE403VIEW="Show errors using a customisable HTML template"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_USE403VIEW_TIP="By default, the Blocked Request Message will be shown using Joomla!'s standard error message page. When this option is enabled, however, Admin Tools will use a customisable HTML template. The default HTML template file is located in the components/com_admintools/View/Blocks/tmpl/default.php file. DO NOT MODIFY THIS FILE DIRECTLY! Read the documentation for the proper method to create a template override."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_WHITELIST_DOMAINS="Never blocked domains"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_WHITELIST_DOMAINS_TIP="If the IP address of the visitor whose request would be blocked resolves to a domain name ending in what you enter here they will not be blocked; their request will go through normally. Effectively, these domain names have a free pass on your site. Please note that a long list will cause a big performance impact. The default list entries are .crawl.baidu.com, .crawl.baidu.jp, .google.com, .googlebot.com, .search.msn.com, .crawl.yahoo.net, .yandex.ru, .yandex.net, .yandex.com which allows most common search engine indexers."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PERMABAN="Add persistent offenders to the IP Disallow List"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PERMABANNUM="Permanently disallow IP after this many automatic blocks"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PERMABANNUM_2="automatic IP blocks"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PERMABANNUM_TIP="When the previous option is enabled, after how many auto-bans an IP will be permanently banned (added to the IP Disallow List)."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PERMABAN_TIP="If an IP triggers this many auto-bans it will be permanently banned (added to the IP Disallow List) if they are about to be auto-banned again. Make sure that you turn on the IP Disallow List feature by setting <em>Disallow site access to IPs in the IP Disallow List</em> to Yes, otherwise the permanent adding to the IP Disallow List will have no effect."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_PROJECTHONEYPOT="Project Honeypot"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_SIGNUPIP_BODY="<p>The user signed up to the site using IP address <strong>%s</strong></p><p>The user agent string of the user's browser was:<br/>%s</p><p>This information was automatically recorded in this User Note by Admin Tools Professional.</p>"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_SIGNUPIP_SUBJECT="Sign-up IP address"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_SPAMMERMESSAGE="Show this message to blocked IPs"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_SPAMMERMESSAGE_TIP="Allows you to show a specific message to blocked IP addresses. You may want to explain to the user that his IP was blocked because suspicious activity was detected as originating from his IP address. You can use the special text [IP] in all capital letters, without spaces between the brackets and IP, to display the user's IP in the message. This may be useful if someone gets accidentally blocked and asks you to help them."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSR="Auto-ban"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRBANNUM="Block duration"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRBANNUM_TIP="How long the block will last. For example, setting it to 1 day will block all access from this IP address for a whole day. Enter the number in this field, select the unit of time measurement in the next field."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRBANFREQUENCY="Unit of time measurement for block duration"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRBANFREQUENCY_TIP="The unit of time measurement for the “Block duration” setting above. Choose one of seconds, minutes, days or hours."

COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRENABLE="IP blocking of repeat offenders"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRENABLE_TIP="When set to yes, the IP address of repeat offenders will be automatically banned based on the rest of the settings"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRSTRIKES="Block IP after this many blocked requests"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRSTRIKES_TIP="When requests from an IP address are blocked at least this many times within the period of time defined by the next two options it will be temporarily blocked from accessing the site. For example, if you set it to 3 attacks in 1 hour, Admin Tools will disallow access from an IP address which got at least 3 of its requests blocked within the last hour. Enter the value 0 to disable this feature."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRNUMFREQ="Time period"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRNUMFREQ_TIP="The number of blocked requests defined above must occur within this many seconds, minutes, hours or days. You enter the number here; you choose the unit of time measurement in the option below."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRFREQUENCY="Unit of time measurement"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_TSRFREQUENCY_TIP="The unit of time measurement for the “Time period” setting above. Choose one of seconds, minutes, days or hours."
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN="Password authentication when WebAuthn is enabled for a user account"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_TIP="If a user enables WebAuthn authentication for their user account should they be allowed to alternatively log in with a password?"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_OPT_ALLOWED="Always allowed (Joomla default)"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_OPT_USERDECIDES="Let the users decide"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_OPT_NOBACKEND_OTHERALLOWED="Disabled for back-end users, allowed for others"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_OPT_NOBACKEND_OTHERDECIDE="Disabled for back-end users, let others decide"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_NOPWONWEBAUTHN_OPT_NOBODY="Disabled for everyone"

COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ALLOWED_DOMAINS="Allowed domains"
COM_ADMINTOOLS_CONFIGUREWAF_LBL_OPT_ALLOWED_DOMAINS_TIP="Enter all fully qualified domain names your site is supposed to respond to e.g. <em>example.com, www.example.com, example.net</em>. One entry per text field; add more fields clicking/tapping the green + button. You do not need to add <code>localhost</code> or any other domain name which resolves to <code>127.0.0.1</code> or <code>::1</code> (localhost addresses). If someone tries to spoof the HTTP Host header to a domain name not in this list they will receive an HTTP 400 Bad Request response. This feature prevents Host header spoofing on some misconfigured hosts."

[Wafexceptions]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; WAF Exceptions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_WAFEXCEPTIONS="WAF Exceptions"
COM_ADMINTOOLS_TITLE_WAFEXCEPTION_ADD="Add a WAF Exception"
COM_ADMINTOOLS_TITLE_WAFEXCEPTION_EDIT="Edit a WAF Exception"

COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_WHATSTHIS_INTRO = "This page allows you to select specific components, views or query strings <i>to NOT be protected</i> by the Web Application Firewall. Exceptions are applied in two groups:"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_WHATSTHIS_GROUP_A = "When <i>all query strings</i> are specified for a component or view, the following WAF features are disabled completely: Bad Behaviour, SQLiShield, XSSShield, MUAShield, RFIShield, DFIShield and Bad Words Filtering"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_WHATSTHIS_GROUP_B = "When <i>specific query strings</i> are specified for a component or view, the following WAF features are disabled <i>only for those query strings</i>: SQLiShield, XSSShield, RFIShield, DFIShield, Bad Words Filtering, and Block Suspicious URL Parameters"

COM_ADMINTOOLS_WAFEXCEPTION_EMPTYSTATE_TITLE="No WAF Exception rules have been created yet."
COM_ADMINTOOLS_WAFEXCEPTION_EMPTYSTATE_CONTENT="WAF Exception rules allow you to prevent blocking requests to your site for specific components, views and query string parameters. This can be used when you know a component is secure but the way it works will always lead to false positives."
COM_ADMINTOOLS_WAFEXCEPTION_EMPTYSTATE_BUTTON_ADD="Add a WAF Exception rule"

COM_ADMINTOOLS_WAFEXCEPTION_TABLE_CAPTION="Table of Web Application Firewall Exception rules."

COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_ERR_ALLEMPTY="You must provide at least one of Component, View, or Query for the WAF Exception rule to be valid."

COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_OPTION="Component"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_OPTION_ALL="(All)"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_OPTION_DESC="The name of the Joomla component this rule matches. Leaving empty (“– Component –”) matches all components."
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_OPTION_SELECT="– Component –"

COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_VIEW="View Name"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_VIEW_DESC="The component's view (component area) or controller name which need to be present in the URL for this rule to match. Turn off SEF URLs and you will see either <code>view=ViewName</code> or <code>task=ViewName.TaskName</code> where <var>ViewName</var> is the View Name you need to enter here. Leaving empty matches all views. If you want to match a SEF URL path leave the Component set to “(All)” and enter the SEF path <strong>WITH</strong> a leading slash but <strong>WITHOUT</strong> <code>index.php</code>. For example, use <code>/foo/bar</code>. On multi-language sites you must NOT include the language prefix e.g. <s><code>/en/example</code></s> is wrong, whereas <code>/example</code> is correct. Please note that this can be a <em>partial</em> path i.e. <code>/foo/bar</code> matches both <code>/foo/bar/test</code> and <code>/foo/bar.html</code>."
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_VIEW_ANY="(All)"

COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_QUERY="Query Parameter"
COM_ADMINTOOLS_WAFEXCEPTIONS_LBL_QUERY_DESC="Which query string parameter to disable security filtering for, e.g. <code>id</code>. Leave blank to match all query parameters. Note that WAF Exceptions are applied after Joomla has converted a SEF URL to its non-SEF format regardless of whether you have enabled SEF URLs on your site."

COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_COPIED="%d WAF Exception rules were copied."
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_COPIED_1="The WAF Exception rule was copied."
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_DELETED="%d WAF Exception rules were deleted."
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_DELETED_1="The WAF Exception rule was deleted."
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_PUBLISHED="%d WAF Exception rules were published"
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_PUBLISHED_1="The WAF Exception rule was published"
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_UNPUBLISHED="%d WAF Exception rules were unpublished"
COM_ADMINTOOLS_WAFEXCEPTIONS_N_ITEMS_UNPUBLISHED_1="The WAF Exception rule was unpublished"

[Checktempandlogdirectories]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Check Temp and Log Directories
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_CHECKTEMPANDLOGDIRECTORIES="Check Temp and Log Directories"

COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_ERR_CHMOD_TMPFOLDER="Can not change the permissions of the temporary folder. Please enable the FTP layer inside Joomla Global configuration and try again. If you already did that, please contact your host and ask him to fix the permissions on your site."
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_ERR_TMPDIR_CREATION="Can not create a temporary folder. Please enable the FTP layer inside Joomla Global configuration and try again. If you already did that, please contact your host and ask him to fix the permissions on your site."
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_ERR_CHMOD_LOGFOLDER="Can not change the permissions of the logging folder. Please enable the FTP layer inside Joomla Global configuration and try again. If you already did that, please contact your host and ask him to fix the permissions on your site."
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_ERR_LOGDIR_CREATION="Can not create a log folder. Please enable the FTP layer inside Joomla Global configuration and try again. If you already did that, please contact your host and ask him to fix the permissions on your site."
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_ERR_SAVING_JCONFIG="Admin Tools was not able to update your Joomla Global configuration. Please enable the FTP layer inside Joomla Global configuration and try again."
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_TMPDIR_WORKAROUND="In order to make the temporary folder writable to Joomla, Admin Tools set its permissions to 777 and protected it from web access by creating an .htaccess file. <strong>This is just a temporary solution</strong>. You should contact your host and ask him to fix the permissions on your site; after that remember to change the permissions of the %s folder back to 0755"
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_LOGDIR_WORKAROUND="In order to make the log folder writable to Joomla, Admin Tools set its permissions to 777 and protected it from web access by creating an .htaccess file. <strong>This is just a temporary solution</strong>. You should contact your host and ask him to fix the permissions on your site; after that remember to change the permissions of the %s folder back to 0755"

COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_CHECKCOMPLETED="Success"
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_CHECKFAILED="Check failed"
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_CHECKINPROGRESS="Checking paths in progress…"
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_TEMP_PATH="Temporary path"
COM_ADMINTOOLS_CHECKTEMPANDLOGDIRECTORIES_LBL_LOG_PATH="Log path"

[Schedulinginformation]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; PHP File Change Scanner Scheduling
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_SCHEDULINGINFORMATION="PHP File Change Scanner Scheduling"

COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_ALTCLICRON="Alternative Command-Line CRON jobs"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_ALTCLICRON_INFO="This method is recommended only if the regular Command-Line CRON job does not complete. This method internally uses the frontend scheduling method and is a little slower than the native CLI method."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_CLICRON="Command-Line CRON jobs (recommended)"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_CLICRON_INFO="This is the recommended method for all servers supporting command-line CRON jobs. This method bypasses the web interface of Joomla!, achieving maximum site scan speed."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_CLIGENERICIMPROTANTINFO="Important"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_CLIGENERICINFO="Remember to substitute <em>%s</em> with the real path to your host's PHP <strong>CLI (Command Line Interface)</strong> executable. Do remember that you must use the PHP CLI executable; the PHP CGI (Common Gateway Interface) executable will <em>not</em> work with our CRON scripts. If unsure what this means, please consult your host. They are the only people who can provide this information."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP="Frontend Scheduling Feature"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_INFO="This method uses a public URL and a secret key to trigger a scan of your site. The scan progresses by means of HTTP redirects. Please note that most hosts' URL-based 'CRON' jobs, as well as most third-party URL-based CRON services, do not support HTTP redirects. If the examples with wget and curl below don't work for you, please use the frontend scheduling URL with the very cheap webcron.org third party service."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_MANYMETHODS="The frontend scheduling feature can be used with a great variety of methods. Click the tabs below to see all each method's description. Remember that all of them are explained in detail in our documentation."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_TAB_CURL="cURL"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_TAB_SCRIPT="PHP Script"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_TAB_URL="URL"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_TAB_WEBCRON="WebCron.org"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTENDBACKUP_TAB_WGET="WGet"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_CURL="CRON scheduling using cURL:"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_CUSTOMSCRIPT="Custom PHP script to run the frontend scheduling:"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_DISABLED="The frontend scheduling feature of Admin Tools is not enabled. You cannot use this scheduling method unless you enable it. Please go to the Control Panel of Admin Tools, click on Options and enable the frontend scheduling feature. Do not forget to also specify a secret word of your liking."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_RAWURL="URL for use with your own scripts and third party services:"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_SECRET="The frontend scheduling feature's secret key is empty. You cannot use this scheduling method unless you create a secret key. Please go to Admin Tools's Control Panel, click on Options and enter a secret key of your liking."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON="Configuration of a scan job with WebCron.org:"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_ALERTS="Alerts"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_ALERTS_INFO="If you have already set up alert methods in webcron.org's interface, we recommend choosing an alert method here and not checking the 'Only on error' so that you always get a notification when the backup CRON job runs."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_EXECUTIONTIME="Execution time"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_EXECUTIONTIME_INFO="That's the grid below the other options. Select when and how often you want your CRON job to run."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_INFO="Log in to webcron.org. In the CRON area, click on the New Cron button. Below you'll find what you have to enter at webcron.org's interface."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_LOGIN="Login"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_LOGINPASSWORD_INFO="Leave this blank"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_NAME="Name of cronjob"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_NAME_INFO="Anything you like, e.g. <em>Scan of my site</em>"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_PASSWORD="Password"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_THENCLICKSUBMIT="Finally, click on the Submit button to finish setting up your CRON job."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_TIMEOUT="Timeout"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_TIMEOUT_INFO="180sec; if the scan doesn't complete, increase it. Most sites will work with a setting of 180 or 600 here. If you have a very big site which takes more than 5 minutes to scan, you might consider using the native CLI CRON job instead, as it's much more cost-effective."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WEBCRON_URL="Url you want to execute"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_FRONTEND_WGET="CRON scheduling using wget (most hosts):"

COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER="Joomla Scheduled Tasks"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_INFO="You can schedule a scan of your site using Joomla's Scheduled Task's feature. Please read the documentation first to understand the compromises and potential problems depending on the way you choose to trigger Joomla's Scheduled Tasks."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_BUTTON="Manage your Scheduled Tasks"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_ONLYJ41_HEAD="Scheduled Tasks are only available on Joomla 4.1 and later"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_ONLYJ41_BODY="Joomla introduced the Scheduled Tasks feature in Joomla! version 4.1.0. Please update your site to the latest Joomla version to get access to Scheduled Tasks."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_PLUGIN_DISABLED_HEAD="The “Task – Admin Tools” plugin is disabled."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_PLUGIN_DISABLED_BODY="The “Task – Akeeba Backup” plugin must be enabled forJoomla's Scheduled Tasks to know how to run backups with Akeeba Backup. Please go to System, Manage, Plugins and enable the plugin. Alternatively click the following button to edit the plugin directly."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_JOOMLASCHEDULER_PLUGIN_DISABLED_BUTTON="Edit the plugin"

COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_GENERICREADDOC="Read the documentation"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_GENERICUSECLI="Use the following command in your host's CRON interface:"
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_HEADERINFO="Admin Tools offers several methods for scheduling the execution of the PHP File Change Scanner. You will find more information about each scheduling method below. Please do read the documentation of each scheduling method. It will answer a lot of your questions and will help you schedule your site scans more easily."
COM_ADMINTOOLS_SCHEDULINGINFORMATION_LBL_RUN_FILESCANNER="PHP File Change Scanner Scheduling"

[Exportimport]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Export and Import settings
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_EXPORTIMPORT="Export &amp; Import settings"
COM_ADMINTOOLS_TITLE_EXPORT_SETTINGS="Export settings"
COM_ADMINTOOLS_TITLE_IMPORT_SETTINGS="Import settings"

COM_ADMINTOOLS_EXPORTIMPORT_ERR_FAILURE="Import failed. Reason %s"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_BADWORDS="An error occurred while importing the Bad Words list"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_BLACKLIST="An error occurred while importing the Site IP Disallow List"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_IPALLOW="An error occurred while importing the Site IP Allow List"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_EMAILTEMPLATES="An error occurred while importing email templates"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_FILE="Missing file to import"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_FILE_TYPE="The file must be a CSV"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_LINE="Error on row %s, row has been skipped and not imported"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_READING_FILE="An error occurred while reading the file"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_UPLOAD="There was an error while uploading the file"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_WAFBLACKLIST="An error occurred while importing WAF Deny List"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_WAFEXCEPTIONS="An error occurred while importing WAF Exceptions"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_WHITELIST="An error occurred while importing the Exclusive Allow IP List"
COM_ADMINTOOLS_EXPORTIMPORT_ERR_NOFILE="Please upload the file with saved settings"

COM_ADMINTOOLS_EXPORTIMPORT_LBL_BADWORDS="Bad words"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_DELIMITERS="CSV delimiters"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_DELIMITERS_CUSTOM="Custom delimiters"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_DELIMITERS_DESC="Choose the field delimiters found in your CSV file. You may need to open the file in a plain text editor (e.g. Notepad, gEdit, TextEdit) to see what is the actual delimiter used."
COM_ADMINTOOLS_EXPORTIMPORT_LBL_DETAILS="Import details"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FAIL="Import failed: %s"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FIELD_DELIMITERS="Field delimiter"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FIELD_DELIMITERS_DESC="Please enter the char used to separate fields."
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FIELD_ENCLOSURE="Field enclosure"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FIELD_ENCLOSURE_DESC="Please enter the char (if present) used to wrap text data."
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FILE="File"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FILE_DESC="Choose the CSV file to import"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_FINE_TUNING="Fine tuning"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_IMPORT_OK="Admin Tools settings imported successfully"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_IPBLACKLIST="Site IP Disallow List"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_IPALLOW="Site IP Allow List"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_IPWHITELIST="Exclusive Allow IP List"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_OK="Import successfully completed. %s imported records"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_SELECT_DATA_WARN="Please select the settings you want to export"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_WAFBLACKLIST="WAF Deny List"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_WAFCONFIG="WAF configuration"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_WAFEXCEPTIONS="WAF exceptions"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_WITH_WARNINGS="Import successfully completed, but there were some warnings"
COM_ADMINTOOLS_EXPORTIMPORT_LBL_USERAGENTS="User Agents to Block"

[Blockedrequestslog]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Blocked Request Log
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_LOG="Blocked Request Log"
COM_ADMINTOOLS_LOG_ERR_NOID="Blocked request record not found"

COM_ADMINTOOLS_BLOCKEDREQUESTSLOG_TABLE_CAPTION="Table of requests blocked by Admin Tools"

COM_ADMINTOOLS_BLOCKEDREQUESTSLOG_EMPTYSTATE_TITLE="No Blocked Requests have been recorded yet."
COM_ADMINTOOLS_BLOCKEDREQUESTSLOG_EMPTYSTATE_CONTENT="Admin Tools logs any requests it blocked or you asked it to record based on your Web Application Firewall configuration options. These log entries are used to decide when to temporarily block IP addresses which seem to be attacking your site. This page lets you review the log of blocked requests and remove records when you so wish."
COM_ADMINTOOLS_BLOCKEDREQUESTSLOG_EMPTYSTATE_BUTTON_ADD="Go Back"

COM_ADMINTOOLS_LOG_LBL_IP="IP address"
COM_ADMINTOOLS_LOG_LBL_LOGDATE="Date"
COM_ADMINTOOLS_LOG_LBL_REASON="Reason"
COM_ADMINTOOLS_LOG_LBL_BAN="Add to IP Disallow List"
COM_ADMINTOOLS_LOG_LBL_UNBAN="Remove from IP Disallow List"
COM_ADMINTOOLS_LOG_LBL_URL="Target URL"

COM_ADMINTOOLS_LOG_N_ITEMS_DELETED="%d blocked requests log entries were deleted."
COM_ADMINTOOLS_LOG_N_ITEMS_DELETED_1="The blocked request log entry was deleted."

COM_ADMINTOOLS_LOG_LBL_REASON_SELECT="Select a reason"

COM_ADMINTOOLS_LOG_LBL_REASON_404SHIELD="404 Shield"
COM_ADMINTOOLS_LOG_LBL_REASON_ADMINDIR="Admin directory"
COM_ADMINTOOLS_LOG_LBL_REASON_ADMINLOGINSUCCESS="Successful administrator login"
COM_ADMINTOOLS_LOG_LBL_REASON_ADMINPW="Admin Query String"
COM_ADMINTOOLS_LOG_LBL_REASON_ALL="All"
COM_ADMINTOOLS_LOG_LBL_REASON_ANTISPAM="Bad Words Filtering"
COM_ADMINTOOLS_LOG_LBL_REASON_AWAYSCHEDULE="Away Schedule"
COM_ADMINTOOLS_LOG_LBL_REASON_CONFIGMONITOR="Configuration Editing"
COM_ADMINTOOLS_LOG_LBL_REASON_CSRFSHIELD="CSRF Shield (obsolete)"
COM_ADMINTOOLS_LOG_LBL_REASON_DFISHIELD="DFIShield"
COM_ADMINTOOLS_LOG_LBL_REASON_EXTERNAL="Third Party Application"
COM_ADMINTOOLS_LOG_LBL_REASON_GEOBLOCKING="Geo Block"
COM_ADMINTOOLS_LOG_LBL_REASON_HTTPBL="Spammer (via HTTP:BL)"
COM_ADMINTOOLS_LOG_LBL_REASON_IPBL="Site IP Disallow List"
COM_ADMINTOOLS_LOG_LBL_REASON_IPWL="Admin Exclusive Allow IP List"
COM_ADMINTOOLS_LOG_LBL_REASON_ITEMIDSHIELD="ItemidShield"
COM_ADMINTOOLS_LOG_LBL_REASON_LOGINFAILURE="Login failure"
COM_ADMINTOOLS_LOG_LBL_REASON_MUASHIELD="MUA Shield"
COM_ADMINTOOLS_LOG_LBL_REASON_NONEWADMINS="Backend Edit Admin User"
COM_ADMINTOOLS_LOG_LBL_REASON_NONEWFRONTENDADMINS="Frontend Edit Admin User"
COM_ADMINTOOLS_LOG_LBL_REASON_OTHER="Other"
COM_ADMINTOOLS_LOG_LBL_REASON_PHPSHIELD="PHPShield"
COM_ADMINTOOLS_LOG_LBL_REASON_RFISHIELD="RFIShield"
COM_ADMINTOOLS_LOG_LBL_REASON_SESSIONSHIELD="SessionShield"
COM_ADMINTOOLS_LOG_LBL_REASON_SQLISHIELD="SQLi Shield"
COM_ADMINTOOLS_LOG_LBL_REASON_SUPERUSERSLIST="Monitor Super User list"
COM_ADMINTOOLS_LOG_LBL_REASON_SUSPARAM="Suspicious Core Parameter"
COM_ADMINTOOLS_LOG_LBL_REASON_TEMPLATE="template= in URL"
COM_ADMINTOOLS_LOG_LBL_REASON_TMPL="tmpl= in URL"
COM_ADMINTOOLS_LOG_LBL_REASON_UPLOADSHIELD="UploadShield"
COM_ADMINTOOLS_LOG_LBL_REASON_WAFBLACKLIST="WAF Deny List"

COM_ADMINTOOLS_WAFEMAILTEMPLATE_REASON_IPAUTOBAN="IP auto-ban"


[Unblockip]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Unblock an IP
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_UNBLOCKIP="Unblock an IP"

COM_ADMINTOOLS_UNBLOCKIP_LBL_INFO="You can use this page to unblock the IP of a user / client who got accidentally blocked by Admin Tools. This will remove all records relevant to that IP which might contribute to the block. It only works for automatically blocked IPs and single IPs in the IP Disallow List. It will not work for an IP blocked as a result of an IP address range or other kind of multiple IP block you have manually entered in the IP Disallow List. It will of course not work for IPs blocked due to external factors such as directives in your .htaccess file you placed yourself, a third party firewall in front of your site and so on."
COM_ADMINTOOLS_UNBLOCKIP_LBL_CHOOSE_IP="IP to unblock"
COM_ADMINTOOLS_UNBLOCKIP_LBL_IP="Unblock this IP"
COM_ADMINTOOLS_UNBLOCKIP_LBL_OK="The IP has been unblocked."
COM_ADMINTOOLS_UNBLOCKIP_LBL_NOTFOUND="Unblocking the IP failed. The IP was not found to be automatically blocked."


[Tempsuperusers]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Temporary Super Users
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
COM_ADMINTOOLS_TITLE_TEMPSUPERUSERS="Temporary Super Users"
COM_ADMINTOOLS_TITLE_TEMPSUPERUSER_ADD="Create a Temporary Super User"
COM_ADMINTOOLS_TITLE_TEMPSUPERUSER_EDIT="Edit a Temporary Super User"

COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_CANTEDITSELF="You can not create, edit or delete a Temporary Super User that is the same user as the one you are currently logged in!"
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_EXPIRATIONINPAST="You can set an expiration date in the past."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_PASSWORD2="The password you have entered in the “Password” and “Password (repeat)” fields does not match."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_NOTASUPERUSER="You have not selected any Super User groups for this user."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_UNAVAILABLETOTEMP="Managing Temporary Super Users is not available to Temporary Super Users for security reasons."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_EXPIRATION_EMPTY="You need to set an expiration date."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_NOTSUPER="The username already exists but does not belong to a Super User."
COM_ADMINTOOLS_TEMPSUPERUSERS_ERR_NOTBLOCKED="The username is already assigned to an active (not blocked) Super User. For security reasons you are not allowed to convert active Super Users to temporary. Block the user through Joomla's Users page and retry converting them to a Temporary Super User."

COM_ADMINTOOLS_TEMPSUPERUSERS_TABLE_CAPTION="Table of temporary Super User accounts."
COM_ADMINTOOLS_TEMPSUPERUSERS_FIELD_USER_ID="User ID"
COM_ADMINTOOLS_TEMPSUPERUSERS_FIELD_EXPIRATION="Expiration"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_USER="Joomla User"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_USERNAME="Username"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_PASSWORD="Password"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_PASSWORD2="Password (repeat)"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_EMAIL="Email address"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_NAME="Full name"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_GROUPS="User Groups"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_DEFAULTNAME="Temporary User"
COM_ADMINTOOLS_TEMPSUPERUSERS_LBL_USERINFO="Super User Information"

COM_ADMINTOOLS_TEMPSUPERUSERS_EMPTYSTATE_TITLE="No Temporary Super Users have been created yet."
COM_ADMINTOOLS_TEMPSUPERUSERS_EMPTYSTATE_CONTENT="Temporary Super Users are user accounts with Super User privileges (full access to your site). However, unlike regular Super User accounts, these accounts will be automatically deactivated on the date and time you choose.<br/><br/>Use them whenever you want to temporarily give full access to your site e.g. to a developer, support person, consultant and so on."
COM_ADMINTOOLS_TEMPSUPERUSERS_EMPTYSTATE_BUTTON_ADD="Add a Temporary Super User"

COM_ADMINTOOLS_TEMPSUPERUSERS_N_ITEMS_DELETED = "%d Temporary Super Users were deleted."
COM_ADMINTOOLS_TEMPSUPERUSERS_N_ITEMS_DELETED_1 = "The Temporary Super User was deleted."
COM_ADMINTOOLS_TEMPSUPERUSER_SAVE_SUCCESS = "The Temporary Super User was saved."
COM_ADMINTOOLS_TEMPSUPERUSER_SUBMIT = "The Temporary Super User was created."