msgid ""
msgstr ""
"Project-Id-Version: WP Hide & Security Enhancer\n"
"POT-Creation-Date: 2025-09-23 16:01+0300\n"
"PO-Revision-Date: 2025-09-23 16:01+0300\n"
"Last-Translator: NspCode <contact@nsp-code.com>\n"
"Language-Team: Nsp Code\n"
"Language: en\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 3.5\n"
"X-Poedit-KeywordsList: _;gettext;gettext_noop;__;_e;esc_html__;esc_html_e\n"
"X-Poedit-Basepath: ..\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-SearchPath-0: .\n"

#: compatibility/webarx.php:48 compatibility/wps-hide-login.php:45
msgid "WP Hide Conflict Notice."
msgstr ""

#: compatibility/webarx.php:48 compatibility/wps-hide-login.php:45
msgid ""
"You use another plugin (WebARX) to change the default wp-login.php. To avoid "
"conflicts, activate the option within a single code."
msgstr ""

#: compatibility/wp-simple-firewall.php:84
msgid ""
"<b>Conflict notice</b>: <b>The Security Firewall</b> - Login Protection -> Hide "
"Login -> use similar functionality as to WP Hide plugin - Admin Login Url "
"change.  "
msgstr ""

#: include/admin-interface.class.php:123
#: include/admin-interfaces/setup.class.php:244
msgid "Checking your environment .."
msgstr ""

#: include/admin-interface.class.php:136
#: include/admin-interfaces/setup.class.php:257
msgid ""
"Critical issues were identified on your site, please fix them before proceeding "
"with customizations."
msgstr ""

#: include/admin-interface.class.php:143
#: include/admin-interfaces/setup.class.php:264
msgid "No problems have been found on your server environment."
msgstr ""

#: include/admin-interface.class.php:215
msgid "Save"
msgstr ""

#: include/admin-interface.class.php:231
msgid "Reset Page Settings"
msgstr ""

#: include/admin-interface.class.php:256
msgid "Reset All Settings"
msgstr ""

#: include/admin-interface.class.php:462
msgid "There is no help available for this option."
msgstr ""

#: include/admin-interfaces/notice-cache-path.php:5
msgid "Unable to create cache folder at "
msgstr ""

#: include/admin-interfaces/notice-cache-path.php:5
msgid " Is the folder writable? No cache data will be available."
msgstr ""

#: include/admin-interfaces/notice-is-litespeed.php:7
msgid ""
"Your site runs on LiteSpeed ! Before starting, ensure your server is properly "
"configured and it processes the .htaccess file, or there might be layout and "
"functionality breaks."
msgstr ""

#: include/admin-interfaces/notice-is-litespeed.php:7
msgid "For more details check at"
msgstr ""

#: include/admin-interfaces/notice-is-litespeed.php:8
msgid ""
"Also, once the plugin options changed, a LiteSpeed service may be required. "
"Through SSH run the command"
msgstr ""

#: include/admin-interfaces/notice-is-litespeed.php:9
msgid ""
"On certain servers (e.g. Hostinger ) the service restart may not be required."
msgstr ""

#: include/admin-interfaces/notice-is-wpengine.php:5
msgid ""
"Your server run on WPEngine which works on Nginx rewrite rules, the current "
"version can't create the required rewrite data, please check with WP Hide "
msgstr ""

#: include/admin-interfaces/notice-is_multisite.php:6
msgid ""
"This plugin version can't handle MultiSite environment and may fail to provide "
"specific features, please check with WP Hide PRO at"
msgstr ""

#: include/admin-interfaces/notice-mu-loader-update.php:5
msgid ""
"Unable to update /wp-content/mu-plugins/wp-hide-loader.php. Please make sure /"
"wp-content/mu-plugins/ is writable so the plugin updates the required file."
msgstr ""

#: include/admin-interfaces/notice-mu-loader.php:5
msgid ""
"Unable to launch WP Hide through /wp-content/mu-plugins/wp-hide-loader.php. "
"Please make sure /wp-content/mu-plugins/ is writable so the plugin creates the "
"required file."
msgstr ""

#: include/admin-interfaces/notice-no-permalinks.php:5
msgid ""
"Permalink is required to be turned ON at Settings > Permalinks, for WP Hide & "
"Security Enhancer to work"
msgstr ""

#: include/admin-interfaces/notice-rewrite-test-static-file.php:6
msgid "Rewrite test for static php files failed! "
msgstr ""

#: include/admin-interfaces/notice-rewrite-test-static-file.php:8
msgid ""
"This is a <b>soft error</b> and impact only the option at Rewrite > Theme > "
"'Remove description header from Style file' and should be disabled until the "
"issue fixed."
msgstr ""

#: include/admin-interfaces/notice-rewrite-test.php:9
#: include/admin-interfaces/notice-rewrite-test.php:15
msgid "Rewrite test failed! "
msgstr ""

#: include/admin-interfaces/notice-rewrite-test.php:9
msgid "Ensure the rewrites are active for your server."
msgstr ""

#: include/admin-interfaces/notice-server-not-supported.php:5
msgid ""
"Your site runs on a server type which the current version can't create the "
"required rewrite data, please check with"
msgstr ""

#: include/admin-interfaces/notice-server-not-supported.php:5
msgid "version at"
msgstr ""

#: include/admin-interfaces/notice-server-not-supported.php:6
msgid ""
"This basic version can work with Apache, LiteSpeed, IIS, Nginx set as reverse "
"proxy for Apache, your site runs"
msgstr ""

#: include/admin-interfaces/notice-write-check.php:6
msgid "Unable to write/update required rewrite rules to your site"
msgstr ""

#: include/admin-interfaces/notice-write-check.php:6
msgid ""
"Is this file writable? Until fixed, no changes are applied on the front side."
msgstr ""

#: include/admin-interfaces/notice-write-check.php:7
msgid ""
"Try to go at Settings > Permalinks and save once, the core will attempt to "
"update the required rewrites. If the problem persists, check with your host "
"support on the correct file write permission."
msgstr ""

#: include/admin-interfaces/notice-write-check.php:8
msgid "Once the file permission is fixed, Save the options once."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:196
#: include/admin-interfaces/security-scan.class.php:223
#: include/admin-interfaces/security-scan.class.php:558
#: include/widgets.class.php:56
msgid "Security Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:251
msgid "Unknow - Start a new Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:312
msgid "Unknown"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:315
#: include/admin-interfaces/security-scan.class.php:360
msgid "Running first Scan.. Please wait!"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:332
#: include/widgets.class.php:46
msgid "Your current estimated protection is"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:356
msgid "Start First Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:358
#: include/admin-interfaces/security-scan.class.php:393
msgid "Working"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:358
#: include/admin-interfaces/security-scan.class.php:393
msgid "of"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:358
#: include/admin-interfaces/security-scan.class.php:393
msgid "total tests"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:361
#: include/admin-interfaces/security-scan.class.php:423
msgid "Last Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:361
msgid "Unavailable"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:372
#: include/admin-interfaces/security-scan.class.php:414
msgid "Another Scan instance in progress. Refresh the page in a minute."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:381
msgid "Passed"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:385
msgid "Failed"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:391
msgid "Start New Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:419
msgid "Found new Items, a new Security Scann is recommended."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:474
msgid "Very Poor"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:476
msgid "Poor"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:478
msgid "Fair"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:480
msgid "Good"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:482
msgid "Great"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:484
msgid "Excellent"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:486
msgid "Perfect"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:545
#: include/admin-interfaces/security-scan.class.php:548
msgid "unsatisfactory"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:551
msgid "dangerously low, an imminent security breach is highly likely."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:555
msgid "The current protection level is "
msgstr ""

#: include/admin-interfaces/security-scan.class.php:555
msgid ""
"Consider improving the overall security by fixing the issues reported by the "
"Scan"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:573
#: include/functions.class.php:1073 include/functions.class.php:1140
#: include/functions.class.php:1303 include/functions.class.php:1370
msgid "Ignore"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:576
msgid "Restore"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:602
msgid "Another Scan instance in progress. Please wait until completed."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:632
msgid "Scan completed."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:814
msgid "The wp_remote_get() returns a Not Found page."
msgstr ""

#: include/admin-interfaces/security-scan.class.php:820
#: include/functions.class.php:1127 include/functions.class.php:1243
#: include/functions.class.php:1357
msgid ""
"The wp_remote_get() returns a 401 error code, the request could not be "
"authenticated. Does the site use an httpd password?"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:826
#: include/functions.class.php:1135 include/functions.class.php:1251
#: include/functions.class.php:1365
msgid "The wp_remote_get() returns a"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:826
#: include/functions.class.php:1135 include/functions.class.php:1251
#: include/functions.class.php:1365
msgid "error code"
msgstr ""

#: include/admin-interfaces/security-scan.class.php:830
#: include/functions.class.php:1150 include/functions.class.php:1262
#: include/functions.class.php:1380
msgid "Unespected error code for wp_remote_get() call."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:32
msgid ""
"WordPress security is a serious matter and you can improve it by changing the "
"WordPress database prefix. A WordPress database contains all of the information "
"for your website, which makes it a prime target for hackers. \n"
"                                                                By default, the "
"WordPress database prefix is “wp_” and is quite easy to locate and target."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:46
#: include/admin-interfaces/security-scan/scan_item_db_debug.php:48
#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:44
#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:46
msgid "Current value: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:51
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The database prefix use the "
"default wp_ prefix."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:61
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The database prefix use a custom "
"name."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:32
#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:32
msgid ""
"Debugging PHP code is part of any project, but WordPress comes with specific "
"debug systems designed to simplify the process as well as standardize code "
"across the core, plugins and themes.\n"
"                                                                On production "
"sites, the debug should be disabled to avoid exposing paths and other pieces of "
"information related to the site. "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:53
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The database debug is active. "
"Check your site wp-config.php and comment the WP_DEBUG and  WP_DEBUG_DISPLAY "
"( if exists ) constants declaration."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:62
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The database debug is disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:32
msgid ""
"The WordPress theme/plugin file editor lets you open files from the site. It "
"displays the file content on the text editor allowing changes to the code, "
"directly on the dashboard.\n"
"                                                                <br />Unless "
"this is a development instance, it should be disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:49
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The file editor is enabled. \n"
"                                                                        <br /"
">To fix this security issue, add/change the wp-config.php:\n"
"                                                                        <br /"
"><code>define ( 'DISALLOW_FILE_EDIT', TRUE );</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:60
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The file editor is disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:29
msgid "Firewall"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:32
msgid ""
"A Firewall is a security piece of software that adds a layer of protection to "
"your site. A firewall works as a rules-based filter for all incoming traffic to "
"a website, it ensures only the secure traffic is reaching the server, all "
"malicious attempts will be blocked and logged.\n"
"                                                                <br />A "
"Firewall works as Proactive ratter reactive security solution, so it helps to "
"protect a website before the malicious and malware actually reach it. This is a "
"huge improvement for security, as preventing any harm and damages to a site, "
"spare the administrators of incalculable losses which the malware can do."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:49
msgid "Failed to block requests using malicious header calls."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:53
msgid "Failed to block requests using malicious set-cookie calls."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:57
msgid "Failed to block requests using malicious MySQL code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:61
msgid "Failed to block requests using malicious globals calls."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:65
msgid "Failed to block requests using malicious request calls."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:95
msgid "No valid respons for the call."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:112
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Your site does not appear to use "
"a Firewall or fails to block specific hacks."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:119
#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:137
msgid "Found"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_firewall.php:133
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>Your site appears to use a "
"Firewall."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_headers.php:29
msgid "HTTP Response Security Headers"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_headers.php:32
msgid ""
"HTTP Response Headers are a powerful tool to Harden Your Website.\n"
"                                                                The Hypertext "
"Transfer Protocol (HTTP) is based on a client-server architecture, in which the "
"client ( typically a web browser application ) establishes a connection with "
"the server through a destination URL and waits for a response.\n"
"                                                                The HTTP "
"Headers allow the client and the server send additional pieces of information "
"with the HTTP request or response.\n"
"                                                                The HTTP "
"Headers are categorised by their purpose: Authentication, Caching, Client "
"hints, Conditionals, Connection management, Content negotiation, Controls, "
"Cookies, CORS, Downloads, Message body information, Proxies, Redirects, Request "
"context, Response context, Range requests, Security, Server-sent events, "
"Transfer coding, WebSockets, Other\n"
"                                                                This area "
"provides support for the <a href='https://developer.mozilla.org/en-US/docs/Web/"
"HTTP/Headers#security' target='_blank'>Security Headers</a> type. Those are the "
"ones responsible for the security implementation for any page."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_headers.php:86
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Your site is missing some "
"security headers."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_headers.php:98
#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:81
#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:143
msgid "Unable to complete this security task as an error occoured"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_headers.php:110
#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:92
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>There are no headers containing "
"valuable pieces of information regarding your environment."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:29
msgid "New admin-ajax.php"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:32
msgid ""
"The admin-ajax.php is being used by WordPress core and many plugins to initiate "
"AJAX calls from dashboard and front side. This is specific to WordPress, a site "
"using such slug is an easy target to hack attempts."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Rewriting the admin-ajax.php to "
"another slug to increase overall security for a WordPress site."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:66
#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:66
#: include/admin-interfaces/security-scan/scan_item_hide_json.php:67
#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:66
#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:70
#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:66
#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:69
#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:70
#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:66
#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:65
#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:65
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The option appears properly "
"configured."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:29
#: modules/components/admin-admin_url.php:66
#: modules/components/admin-admin_url.php:72
msgid "New Admin Url"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:32
msgid ""
"Despite the flexibility of WordPress framework, there are few ways to configure "
"the admin login url customization for making a bit safer against unauthorized "
"access and brute force attempts. All methods are not provided out of the box "
"through WordPress core but require custom code to make it happen.\n"
"                                                                <br />This "
"feature provide an easy way to change the default /wp-admin/ to a different "
"slug."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:55
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Map a new admin url instead "
"default prevent hackers boot to attempt to brute force a site login."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:29
msgid "New Child Theme Path"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:32
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:32
msgid ""
"This option helps to change the theme url to a custom one. As default all theme "
"assets ( styles, JavaScript etc ) are loaded using the theme url and appear on "
"front side HTML source code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:47
#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:50
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>On the last scan, you are not "
"using a Child Theme."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:77
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:67
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default theme url has not "
"been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:81
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:71
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default theme url is still "
"found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:83
#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:80
#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:73
#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:74
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:73
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:73
#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:73
#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:73
msgid "<br />Ensure you cleared the site cache, then check again."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:95
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:85
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default theme url cannot be "
"found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:29
msgid "New Child Theme Style File Path"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:32
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:32
msgid ""
"This allow to change the default style.css filename to something else e.g. "
"template-style.css. Per this example, on front side the main style link change "
"from /style.css to /template-style.css "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:74
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:67
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default theme style url has "
"not been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:78
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:71
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default theme style url is "
"still found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:92
#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:85
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default theme style url "
"cannot be found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:29
#: modules/components/rewrite-comments.php:54
#: modules/components/rewrite-comments.php:58
msgid "New wp-comments-post.php"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:32
msgid ""
"To avoid boots to create smap comments, the default wp-comments-post.php should "
"be changed to a custom one.\n"
"                                                            <br />This makes it "
"easy to recognise as WordPress form. Boots always search for such file ( wp-"
"comments-post.php ) and automatically submit spam messages.Though this option a "
"new file slug can replace the default."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:67
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default wp-comments-post.php "
"has not been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:71
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default wp-comments-post.php "
"is still found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:85
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default wp-comments-post.php "
"cannot be found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:29
#: modules/components/rewrite-new_plugin_path.php:89
#: modules/components/rewrite-new_plugin_path.php:93
msgid "New Plugins Path"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:32
msgid ""
"In WordPress, a plugin is a small software application that extends the "
"features and functions of a WordPress website.\n"
"                                                                <br />Plugins "
"play a major role in building great websites using WordPress. They make it "
"easier for users to add features to their website without knowing a single line "
"of code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:68
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default plugins path has not "
"been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:72
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default plugins path is still "
"found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:86
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default plugins path cannot "
"be found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:29
#: modules/components/rewrite-new_theme_path.php:123
#: modules/components/rewrite-new_theme_path.php:127
#: modules/components/rewrite-new_theme_path.php:189
#: modules/components/rewrite-new_theme_path.php:193
msgid "New Theme Path"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:29
msgid "New Theme Style File Path"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:29
msgid "Hide default /wp-content/ "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:32
msgid ""
"As default a WordPress installation contain a wp-content folder which store "
"files and resources used by themes and plugin. The wp-content is a common "
"fingerprint, which makes easily to anyone to identify the site as being created "
"on WordPress."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:67
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default /wp-content/ has not "
"been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:71
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default /wp-content/ is still "
"found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:85
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default /wp-content/ cannot "
"be found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:29
msgid "Hide default /wp-includes/ "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:32
msgid ""
"As default a WordPress installation contain a wp-include folder which store "
"files and resources used by WordPress core, themes and plugin. The wp-includes "
"is a common fingerprint, which makes easily to anyone to identify the site as "
"being created on WordPress."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:67
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default /wp-includes/ has not "
"been customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:71
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The default /wp-includes/ is "
"still found within the source HTML."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:85
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The default /wp-includes/ cannot "
"be found anymore through the site source."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:29
#: modules/components/general-emulate.php:42
#: modules/components/general-emulate.php:46
msgid "Emulate CMS"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:32
msgid ""
"Using the option the system try to misguide the used WordPress by outputting "
"the wrong traces, of the selected CMS.\n"
"                                                                <br /"
">Misleading and making a false lead provides an extra security, as the attacker "
"search and attempt to hack something which not exist."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:55
msgid ""
"<span class=\"dashicons dashicons-no\"></span>It's recommended to use the "
"option to output specific CMSs HTML traces to mislead any peculiar check."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:29
msgid "JSON REST"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:32
msgid ""
"The WordPress REST API is an easy-to-use set of HTTP endpoints which allows "
"access a site data in simple JSON format. That including users, posts, "
"taxonomies and more. Retrieving or updating is as simple as sending a HTTP "
"request.\n"
"                                                                <br />A REST "
"API can be consumed everywhere. On mobile applications, on front-end (web apps) "
"or any other devices that have access on the net, practically everything can "
"connect from anywhere to your site and interact though JSON REST API service."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:56
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The JSON endpoint should be "
"customised. If not used, should be disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:29
#: modules/components/rewrite-json-rest.php:132
#: modules/components/rewrite-json-rest.php:136
msgid "Clean the REST API response"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:32
msgid ""
"When calling the site REST API base route ( e.g. /wp-json/ or ?rest_route=/ ) "
"the service outputs all available namespaces and routes for current site. This "
"can be a breach for the system, as outputs important information regarding "
"certain used theme and plugins.\n"
"                                                                <br /"
">Recommended selection for this option is Yes, to ensure no inside data is "
"being exposed. "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:55
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The \"Clean the REST API "
"response\" should be active."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:29
#: modules/components/rewrite-root-files.php:114
#: modules/components/rewrite-root-files.php:118
msgid "Block license.txt"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:32
#: modules/components/rewrite-root-files.php:119
msgid ""
"This is a text file which contain the licensing terms for WordPress framework. "
"Obviously you don't want that visible as every site containing such file must "
"be a WordPress."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:59
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The license.txt file is still "
"accessible."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:29
#: modules/components/admin-login_php.php:79
#: modules/components/admin-login_php.php:85
msgid "New wp-login.php"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:32
msgid ""
"There are a lot of security issues that come from having your login page open "
"to the public. Most specifically, brute force attacks. Because of the ubiquity "
"of WordPress, these kinds of attacks are becoming more and more common.\n"
"                                                                <br />Map a new "
"wp-login.php instead default prevent hackers boot to attempt to brute force a "
"site login. Being known only by the site owner, the url itself becomes private."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:55
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Map a new wp-login.php instead "
"default prevent hackers boot to attempt to brute force a site login. Being "
"known only by the site owner, the url itself becomes private."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:29
#: modules/components/general-meta.php:178 modules/components/general-meta.php:182
msgid "Remove Other Generator Meta"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:32
#: modules/components/general-meta.php:179 modules/components/general-meta.php:183
msgid ""
"Remove other meta generated tags within head (eg Theme Name, Theme Version)."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The Other Generator Meta is still "
"visible through the HTML code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:29
msgid "Post-Processing"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:32
msgid ""
"The feature provides a post-processing engine for all site assets ( CSS /  "
"JavaScript ). That encodes the CSS  and JavaScript, which makes it unable to "
"read. Also, ensure perfect URLs disguise, as even if changing the plugin's "
"name, most of the URLs still contain traces within. \n"
"                                                                    This is "
"also a great tool for making optimisation of the site assets by combining, "
"minifying, comment removal etc. \n"
"                                                                    Perfectly "
"functional and integration in conjunction with other SEO/Optimisation plugins.\n"
"                                                                    <p>&nbsp;</"
"p>\n"
"                                                                    <p>There "
"are 4 types of processing options:\n"
"                                                                    <b>Combine</"
"b>: Merge all code in (usually) 2 files, one in the header and another in the "
"footer.\n"
"                                                                    <b>Combine "
"& Encode Inline</b>: Merge all code in (usually) 2 files, one in the header and "
"another in the footer. Additionally, the Inline code will be base64 encoded and "
"placed in the same spot.\n"
"                                                                    <b>In "
"Place</b>: All JavaScript code will be processed and the results will be placed "
"in the same spot. Any InLine code will be processed and saved into a data-"
"collection directory for later usage.\n"
"                                                                    <b>In Place "
"& Encode Inline</b>: All code will be processed and the results will be placed "
"in the same spot. Additionally, the Inline code will be base64 encoded.</p>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:58
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Your site assets still contain "
"traceable data within CSS / JavaScript"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:29
#: modules/components/rewrite-root-files.php:132
#: modules/components/rewrite-root-files.php:136
msgid "Block readme.html"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:32
#: modules/components/rewrite-root-files.php:137
msgid ""
"A Hypertext Markup Language file with general information about installed "
"WordPress, version, instalation steps, updating, requirements, resources etc."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:59
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The readme.html file is still "
"accessible."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:29
msgid "User Registration"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:32
msgid ""
"Through your site, if the WordPress Membership option is active, anyone can "
"register."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The Registration should be "
"customised or disabled through Dashboard > Settings."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:29
#: modules/components/general-headers.php:77
#: modules/components/general-headers.php:81
#: modules/components/security-add_headers.php:66
msgid "Remove Link Header"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:32
msgid ""
"Remove Link Header being set as default by WordPress which outputs the site "
"JSON URL."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The site pages header still "
"contain the site JSON url."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:29
msgid "Remove Environment Headers"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:32
msgid ""
"Remove the X-Powered-By and Server Headers if set. This type of header "
"information discloses important details regarding your server environment."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:69
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Your site headers still contain "
"some valuable pieces of information regarding your environment."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:29
#: modules/components/general-html.php:113 modules/components/general-html.php:117
msgid "Remove Comments"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:32
#: modules/components/general-html.php:118
msgid ""
"The HTML source code usually contain many comment lines, however there is no "
"use for that, unless debugging. Remove all HTML Comments, which usually specify "
"Plugins Name and Version. Any Internet Explorer conditional tags are preserved."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The site pages still contain HTML "
"comments which may provide essential pieces of information regarding the active "
"plugins and themes."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:29
msgid "Replacements"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:32
msgid ""
"The module implements a post-processing engine, which allows arbitrary words to "
"be replaced with custom ones. This works for all site data as HTML, Css, "
"JavaScript assets.\n"
"                                                                This is the "
"perfect tool to white-label any plugins or active code on a site, by replacing "
"the specific words (classes, tags, JavaScript variables etc).\n"
"                                                                Examples can be "
"found at <a href='https://wp-hide.com/how-to-easily-hide-elementor-page-"
"builder/' target='_blank'>How to white label Elementor</a> also <a "
"href='https://wp-hide.com/hide-your-avada-theme-avada-builder-and-fusion-core/' "
"target='_blank'>HowHide your Avada Theme, Avada Builder and Fusion core</a> "
"this makes the plugins totally unrecognizable for anonymous users.\n"
"                                                                <p>&nbsp;</p>\n"
"                                                                <p>This feature "
"integrates perfectly with any site environment, regardles of the used plugins "
"and themes. Changing any fingerprint does not break the site layout or disable "
"any existing functionality.</p>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:130
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Your site assets still contain "
"traceable data within HTML / CSS / JavaScript. Those can be removed using the "
"Replacements functionality."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:137
msgid "Add replacements for <code>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:154
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>There are no obvious "
"fingerprints."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:29
msgid "Process robots.txt"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:32
msgid ""
"The robots.txt file plays a major role in search engine ranking. It blocks "
"search engine bots and helps index and crawl important parts of your site.\n"
"                                                                <br />As "
"default the robots.txt also includes an allow clause to admin URL and admin-"
"ajax.php url. Once customized those areas, the new slugs might not want to be "
"show to anyone. Turn this option to Yes removed any reference to new wp-admin "
"and admin-ajax.php."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:55
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The robots.txt should be "
"processed to ensure none of the default URLs is still used."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:29
#: modules/components/general-meta.php:246 modules/components/general-meta.php:250
msgid "Remove wlwmanifest Meta"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:32
msgid ""
"The wlwmanifest link is actually used by Windows Live Writer. If you don't te "
"application, this is just unnecessary code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>Unless using the Windows Live "
"Writer, the file have no usage so should be disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:29
#: modules/components/general-meta.php:158 modules/components/general-meta.php:162
msgid "Remove WordPress Generator Meta"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:32
#: modules/components/general-meta.php:159 modules/components/general-meta.php:163
msgid ""
"Remove the autogenerated meta generator tag within head (WordPress Version)."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The WordPress Generator is still "
"visible through the HTML code."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:29
msgid "Change WordPress TagLine"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:32
msgid ""
"The WordPress tagline is a short description of your website.  The WordPress "
"tagline can be modified by accessing the Dasboard > Settings > General"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:47
msgid "Just another WordPress site"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:54
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The tagline still uses the "
"default WordPress sample, and should be customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:29
msgid "XML-RPC"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:32
#: modules/components/rewrite-new_xml-rpc-path.php:76
msgid ""
"XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its "
"calls and HTTP as a transport mechanism. This service allow other applications "
"to talk to your WordPress site."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:56
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The XML-RPC module has not been "
"customised."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:67
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The XML-RPC appears properly "
"configured."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:32
msgid ""
"WordPress security authentication or secret key or SALT keys, are the encrypted "
"code that protects your login information. \n"
"                                                                Salt keys are "
"cryptographic elements used to 'hash' data in order to secure it. In fact, most "
"serious platforms and systems use similar mechanisms to protect sensitive data."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:69
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The Authentication unique keys "
"and salts are empty or invalid."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:79
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The Authentication unique keys "
"and salts are correctly set-up."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:32
msgid ""
"Using a higher MySQL version ensures better capability for your system. Older "
"versions are often exploitable making the system unstable and predisposing to "
"security breaches."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:47
#: include/admin-interfaces/security-scan/scan_item_php_version.php:47
#: include/admin-interfaces/security-scan/scan_item_wp_version.php:50
#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:49
msgid "Using Version: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:52
#: include/admin-interfaces/security-scan/scan_item_php_version.php:53
msgid ""
"<span class=\"dashicons dashicons-yes\"></span> You are using at least the "
"minimum recommended PHP version."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:57
#: include/admin-interfaces/security-scan/scan_item_php_version.php:58
msgid ""
"<span class=\"dashicons dashicons-no\"></span> You are using an older PHP "
"version that the minimum recommended."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:32
msgid ""
"Old WordPress plugins can do damage to your website. Vulnerabilities are found "
"within plugins all the time. Unmaintained code drastically increase the risk, "
"as there are no patches for known issues. \n"
"                                                                Inconsistent "
"updates can lead to serious security issues and compatibility problems, and "
"land you in technical debt.\n"
"                                                                This will check "
"for plugins with more than a year since their last update."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:81
msgid "Found old plugins: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:86
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The following plugins are very "
"old and appear unmaintained:"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:95
msgid " Last updated on "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:101
msgid ""
"<br /><p class=\"description\">We strongly suggest finding replacements for the "
"above plugins and remove from your site.</p>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:112
msgid "<span class=\"dashicons dashicons-yes\"></span>There are no Old Plugins."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:32
msgid ""
"Keeping your plugins up to date is important for the stability and security of "
"your WordPress site. It also lets you take advantage of any new features the "
"plugin's developers have added.\n"
"                                                                A key concept "
"of updating WordPress core, themes, and plugins is to protect your site from "
"the possible vulnerabilities that allow a hacker to compromise your site. "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:55
msgid "Found outdated plugins: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:60
#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:60
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The following plugins are found "
"outdated on your site:"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:75
#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:70
msgid " Upgrade from "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:75
#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:70
msgid " to "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:81
msgid ""
"<br /><p class=\"description\">The inactive plugins require updating as well, "
"as may contain harmful vulnerabilities, exploaitable even if the code is not "
"active.</p>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:92
msgid "<span class=\"dashicons dashicons-yes\"></span>All plugins are Up to Date."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:32
msgid ""
"The biggest reason to keep your WordPress website up to date is Security. When "
"you do not update your WordPress themes, you create a security risk and expose "
"your site to existing vulnerabilities and imminent attacks. \n"
"                                                        The WordPress "
"developers are constantly fixing security breaches or improving security."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:55
msgid "Found outdated themes: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:76
msgid ""
"<br /><p class=\"description\">The  inactive themes require updating as well, "
"as may contain harmful vulnerabilities, exploaitable even if the code is not "
"active.</p>"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:87
msgid "<span class=\"dashicons dashicons-yes\"></span>All themes are Up to Date."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:32
msgid ""
"The allow_url_include allows a developer to include a remote file using a URL "
"rather than a local file path. This technique is used to reduce the load on the "
"server. \n"
"                                                                There are many "
"servers with PHP configuration directive allow_url_include as enabled. When "
"this setting is enabled, the server’s directory allows data retrieval from "
"remote locations."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:49
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The allow_url_include is ON. \n"
"                                                                        To fix "
"this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /"
"><code>allow_url_include = \"off\"</code>\n"
"\n"
"                                                                        <br /"
">or within .htaccess:\n"
"\n"
"                                                                        <br /"
"><code>php_flag allow_url_include off</code>\n"
"                                                                        <br /"
">or within wp-config.php:\n"
"                                                                        <br /"
"><code>ini_set(\"allow_url_include\", \"0\");</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:67
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The allow_url_include is Off."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:32
msgid ""
"The display_error setting in PHP is used to determine whether errors should be "
"printed to the screen or not."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The display_errors is ON. \n"
"                                                                        <br /"
">To fix this security issue, change the php.ini:\n"
"                                                                        <br /"
"><code>display_errors = \"off\"</code>\n"
"                                                                        <br /"
">or within .htaccess:\n"
"                                                                        <br /"
"><code>php_flag display_errors off</code>\n"
"                                                                        <br /"
">or within wp-config.php:\n"
"                                                                        <br /"
"><code>ini_set(\"display_errors\", \"0\");</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:63
msgid "<span class=\"dashicons dashicons-yes\"></span>The display_errors is Off."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:32
msgid ""
"When the expose_php directive is enabled, PHP includes critical pieces of "
"information within the HTTP response X-Powered-By header when a page is "
"requested."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The expose_php is ON. \n"
"                                                                        To fix "
"this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /"
"><code>expose_php = \"off\"</code>\n"
"\n"
"                                                                        <br /"
">or within .htaccess:\n"
"\n"
"                                                                        <br /"
"><code>php_flag expose_php off</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:64
msgid "<span class=\"dashicons dashicons-yes\"></span>The expose_php is Off."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:32
msgid ""
"When register_globals is enabled, PHP will automatically create variables in "
"the global scope for any value passed in GET, POST or COOKIE. This, combined "
"with the use of variables without initialization, has led to numerous security "
"vulnerabilities."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The register_globals is ON. \n"
"                                                                        To fix "
"this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /"
"><code>register_globals = \"off\"</code>\n"
"\n"
"                                                                        <br /"
">or within .htaccess:\n"
"\n"
"                                                                        <br /"
"><code>php_flag register_globals off</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:64
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>The register_globals is Off."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:32
msgid ""
"The PHP safe mode is an attempt to solve the shared-server security problem. It "
"is architecturally incorrect to try to solve this problem at the PHP level, but "
"since the alternatives at the web server and OS levels aren't very realistic, "
"many people, especially ISP's, use safe mode for now."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The register_globals is ON. \n"
"                                                                        To fix "
"this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /"
"><code>safe_mode = \"off\"</code>\n"
"\n"
"                                                                        <br /"
">or within .htaccess:\n"
"\n"
"                                                                        <br /"
"><code>php_flag safe_mode off</code>."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:64
msgid "<span class=\"dashicons dashicons-yes\"></span>The safe_mode is Off."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_version.php:29
msgid "PHP Version"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_php_version.php:32
msgid ""
"Using the latest PHP version ensures the longevity of security updates. While "
"older versions of PHP offer security updates for a time past “end of life,” the "
"most secure option is the version that is actively maintained."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:29
msgid "Dangerous Files"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:32
msgid ""
"This security test checks for any dangerous files on your WordPress root. You "
"should avoid keeping any unnecessary files on domain root."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:50
#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:78
msgid "PHP executable file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:54
msgid "System Error log file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:58
msgid "System log file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:62
msgid "MySQL database file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:66
msgid "Backup file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:70
msgid "ZIP Archive file"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:74
msgid "Text file, may contain sensitive data"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:110
msgid ""
"<span class=\"dashicons dashicons-no\"></span> Your WordPress root still "
"includes dangerous files which may contain valuable pieces of information "
"regarding your environment."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:111
msgid "Consider re-locating the followng files from your site root:"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:132
msgid ""
"<span class=\"dashicons dashicons-yes\"></span> Your WordPress root still "
"includes dangerous files which may contain valuable pieces of information "
"regarding your environment."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:32
msgid ""
"When setting up a new WordPress site, many users create the default "
"administrator account using the username `admin`.\n"
"                                                                Considering "
"entering the dashboard requires a username and a password, using the login "
"`admin` makes the hackers have an easier time trying to brute force in. "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:51
msgid "Found users: "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:56
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The admin or administrator "
"usernames were found on your system!"
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:66
msgid ""
"<span class=\"dashicons dashicons-yes\"></span>There are no admin or "
"administrator usernames."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:51
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The WP_DEBUG is active. Check "
"your site wp-config.php and comment the constant declaration."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:60
msgid "<span class=\"dashicons dashicons-yes\"></span>The WP_DEBUG is disabled."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:32
msgid ""
"WordPress is a permanent evolving software with regularly released security "
"fixes. The core updates ensure the safety and efficiency of the WordPress "
"system.\n"
"                                                            WordPress updates "
"often include security fixes. It’s an ongoing battle since hackers find "
"vulnerabilities all the time. It’s important to keep WordPress up to date to "
"get the latest protections from new types of attacks."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:61
#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:60
msgid ""
"<span class=\"dashicons dashicons-no\"></span> Unable to connect with WordPress "
"API. Try again later."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:82
msgid ""
"<span class=\"dashicons dashicons-yes\"></span> You are up to date with the "
"latest Wordpress version."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:87
msgid "<span class=\"dashicons dashicons-no\"></span> An updated version "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:87
msgid " of WordPress is available."
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:32
msgid ""
"Over time, security breaches are found within the WordPress core. This option "
"checks whenever the WordPress version deployed on your site is succeptible to a "
"known vulenrability. "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:81
msgid ""
"<span class=\"dashicons dashicons-yes\"></span> The current Wordpress version "
"stability tag is "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:88
#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:91
msgid ""
"<span class=\"dashicons dashicons-no\"></span>  The current Wordpress version "
"stability tag is "
msgstr ""

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:91
msgid ". This is critical and require urgent WordPress update."
msgstr ""

#: include/admin-interfaces/setup.class.php:44
msgid ""
"Any existing options values will be overwritten, are you sure you want to "
"continue?"
msgstr ""

#: include/admin-interfaces/setup.class.php:60 include/wph.class.php:596
msgid "Settings saved"
msgstr ""

#: include/admin-interfaces/setup.class.php:60 include/wph.class.php:596
msgid "Remember, site cache clear is required."
msgstr ""

#: include/admin-interfaces/setup.class.php:198
msgid "Setup"
msgstr ""

#: include/admin-interfaces/setup.class.php:229
msgid "Sample Setup deployed !"
msgstr ""

#: include/admin-interfaces/setup.class.php:232
msgid ""
"A basic plugin set-up has been deployed, to get you started. A site cache clear "
"is required to ensure the updates are reflected on the front side"
msgstr ""

#: include/admin-interfaces/setup.class.php:233
msgid ""
"Check with the front side to ensure everything is working. Further adjustments "
"to other options is recommended"
msgstr ""

#: include/admin-interfaces/setup.class.php:270
msgid "Getting Started"
msgstr ""

#: include/admin-interfaces/setup.class.php:273
msgid ""
"plugin enhances your website's security by concealing your WordPress "
"installation, themes, and plugins. By keeping critical information hidden, it "
"prevents hackers and automated bots from exploiting known vulnerabilities"
msgstr ""

#: include/admin-interfaces/setup.class.php:273
msgid "With new vulnerabilities discovered every day"
msgstr ""

#: include/admin-interfaces/setup.class.php:273
msgid ""
"using WP Hide & Security Enhancer ensures an added layer of protection, keeping "
"your site safe and secure."
msgstr ""

#: include/admin-interfaces/setup.class.php:274
msgid "You can begin with a "
msgstr ""

#: include/admin-interfaces/setup.class.php:274
#: modules/components/security-check_headers.php:147
msgid "Sample Setup"
msgstr ""

#: include/admin-interfaces/setup.class.php:274
msgid "to get started quickly. Then, use the"
msgstr ""

#: include/admin-interfaces/setup.class.php:274
msgid ""
"interface to identify potential vulnerabilities and fine-tune the plugin "
"settings for optimal security. This approach ensures your website is protected "
"with the highest level of defense"
msgstr ""

#: include/admin-interfaces/setup.class.php:279 include/functions.class.php:2433
#: include/functions.class.php:2485
#: modules/components/security-check_headers.php:144
msgid "Recovery"
msgstr ""

#: include/admin-interfaces/setup.class.php:286
msgid "Basic functionality"
msgstr ""

#: include/admin-interfaces/setup.class.php:289
msgid ""
"The basic principle of the plugin is to change default assets URLs, remove or "
"change specific HTML elements, and disable unused services. This makes "
"WordPress unrecognizable. The process isn't automated, so it needs to be done "
"manually while getting feedback on the front side to ensure everything is still "
"functional. No file and directory are being changed anywhere, everything is "
"processed on the fly using output buffering and filters"
msgstr ""

#: include/admin-interfaces/setup.class.php:291
msgid ""
"A default directory structure for WordPress appears like this on outputted HTML"
msgstr ""

#: include/admin-interfaces/setup.class.php:293
msgid ""
"So the most important first step, is to change the default /wp-content/ and /wp-"
"includes/ to something else. This can be done at"
msgstr ""

#: include/admin-interfaces/setup.class.php:293 include/functions.class.php:2531
msgid "and"
msgstr ""

#: include/admin-interfaces/setup.class.php:294
msgid "Further adjustments to"
msgstr ""

#: include/admin-interfaces/setup.class.php:294
msgid "can be applied"
msgstr ""

#: include/admin-interfaces/setup.class.php:296
msgid ""
"At this point, for all simple sites, the WordPress CMS is already hidden. If "
"using complex themes and plugins, further plugin options adjustments are "
"necessarily or PRO might be required ( for example"
msgstr ""

#: include/admin-interfaces/setup.class.php:296
msgid "hiding Elementor"
msgstr ""

#: include/admin-interfaces/setup.class.php:298
msgid ""
"Take the time to understand each option, there are in-line additional help also "
"external description to each of the features. If need additional assistance, "
"use the support forum or contact us. Full description of each option can be "
"found at"
msgstr ""

#: include/admin-interfaces/setup.class.php:298
msgid "Documentation"
msgstr ""

#: include/admin-interfaces/setup.class.php:304
msgid "Sample setup"
msgstr ""

#: include/admin-interfaces/setup.class.php:307
msgid ""
"This establishes a straightforward setup to kickstart your journey. The process "
"triggers activation of fundamental plugin options. Be mindful that all settings "
"will revert to default, potentially overwriting existing values, so exercise "
"caution. Following this procedure, WordPress CMS will be concealed on basic "
"sites; otherwise, additional adjustments may be required for more customized "
"configurations."
msgstr ""

#: include/admin-interfaces/setup.class.php:309
msgid "Create Plugin Setup"
msgstr ""

#: include/admin-interfaces/setup.class.php:310
msgid "Comprehensive Setup"
msgstr ""

#: include/admin-interfaces/setup.class.php:315
msgid ""
"Additional adjustments to the settings may be needed to tailor them to your "
"specific environment. Utilize the Scan feature for easier identification of "
"necessary improvements."
msgstr ""

#: include/admin-interfaces/setup.class.php:316
msgid "For more complex sites, consider employing the "
msgstr ""

#: include/admin-interfaces/setup.class.php:316
msgid ""
"plugin, which offers advanced tools such as PostProcessing with Replacements "
"for targeted removal of individual fingerprints (e.g., elementor, divi, "
"woocommerce, etc.)."
msgstr ""

#: include/admin-interfaces/setup.class.php:322
msgid "Demo Video"
msgstr ""

#: include/class.environment.php:143
msgid ""
"<b>WP Hide</b> - Unable to create environment static file. The system returned "
"the following error: "
msgstr ""

#: include/class.environment.php:158 include/class.environment.php:174
msgid ""
"Some of plugin options will not work correctly so where turned off: <b>Remove "
"description header from Style file</b>, <b>Child - Remove description header "
"from Style file</b>"
msgstr ""

#: include/class.environment.php:169
msgid "Unable to create environment data at "
msgstr ""

#: include/class.environment.php:169
msgid "Is file writable"
msgstr ""

#: include/class.environment.php:169
msgid "Check with folder/file permission or contact server administrator."
msgstr ""

#: include/functions.class.php:285 include/functions.class.php:286
#: include/functions.class.php:287 include/functions.class.php:288
#: include/functions.class.php:289 include/functions.class.php:290
#: include/functions.class.php:291 include/functions.class.php:292
msgid "is a system reserved."
msgstr ""

#: include/functions.class.php:302
msgid "is similar to domain name."
msgstr ""

#: include/functions.class.php:316 include/functions.class.php:363
#: include/functions.class.php:382 include/functions.class.php:391
#: modules/components/security-check_headers.php:270
msgid "Value"
msgstr ""

#: include/functions.class.php:316 include/functions.class.php:342
#: include/functions.class.php:353 include/functions.class.php:363
#: include/functions.class.php:382 include/functions.class.php:391
msgid "set for"
msgstr ""

#: include/functions.class.php:316
msgid "already in use for another option."
msgstr ""

#: include/functions.class.php:342 include/functions.class.php:353
msgid "The value"
msgstr ""

#: include/functions.class.php:342 include/functions.class.php:353
#, php-format
msgid "must be a minimum of %s characters or longer."
msgstr ""

#: include/functions.class.php:363
msgid "use the same base slug "
msgstr ""

#: include/functions.class.php:363
msgid "used for another option."
msgstr ""

#: include/functions.class.php:498
msgid ""
"W3 Total Cache Plugin is active, make sure you clear the cache for new changes "
"to apply"
msgstr ""

#: include/functions.class.php:502
msgid ""
"WP Super Cache Plugin is active, make sure you clear the cache for new changes "
"to apply"
msgstr ""

#: include/functions.class.php:507
msgid ""
"WP Fastest Cache Plugin is active, make sure you clear the cache for new "
"changes to apply"
msgstr ""

#: include/functions.class.php:973
msgid ""
"Copy the following link to a safe place. You can use it later to reset all "
"plugin options if something goes wrong or lost the new login URL."
msgstr ""

#: include/functions.class.php:1073 include/functions.class.php:1303
msgid "Make a fix or manually check the "
msgstr ""

#: include/functions.class.php:1073 include/functions.class.php:1139
#: include/functions.class.php:1140 include/functions.class.php:1192
#: include/functions.class.php:1255 include/functions.class.php:1303
#: include/functions.class.php:1369 include/functions.class.php:1370
#: include/functions.class.php:1387
msgid "Test URL"
msgstr ""

#: include/functions.class.php:1073 include/functions.class.php:1303
msgid ""
"if the result is a JSON response (contains a name and description), the "
"rewrites are working correctly on your site and you can"
msgstr ""

#: include/functions.class.php:1073 include/functions.class.php:1140
#: include/functions.class.php:1303 include/functions.class.php:1370
msgid "this notification"
msgstr ""

#: include/functions.class.php:1074 include/functions.class.php:1141
#: include/functions.class.php:1304 include/functions.class.php:1371
msgid "Sample result, the appearance can be different from a browser to another:"
msgstr ""

#: include/functions.class.php:1075 include/functions.class.php:1142
#: include/functions.class.php:1305 include/functions.class.php:1372
msgid "The Ignore action will be available until the next plugin options update."
msgstr ""

#: include/functions.class.php:1076 include/functions.class.php:1306
msgid ""
"If the Test URL is not functional, the plugin will fail to provide specific "
"features. Check your Hosting provider for more details regarding rewrites and "
"how to activate on your account."
msgstr ""

#: include/functions.class.php:1082 include/functions.class.php:1198
#: include/functions.class.php:1312
msgid "The wp_remote_get() returns invalid Response Code"
msgstr ""

#: include/functions.class.php:1096 include/functions.class.php:1212
#: include/functions.class.php:1326
msgid ""
"The .htaccess file does not appears to exists on the server. To fix, go to "
"Settings > Permalinks and save once."
msgstr ""

#: include/functions.class.php:1101 include/functions.class.php:1217
#: include/functions.class.php:1331
msgid "The test rewrite does not exist."
msgstr ""

#: include/functions.class.php:1101 include/functions.class.php:1217
#: include/functions.class.php:1331
msgid ""
"To fix go to Settings > Permalinks and save once, the core will attempt to "
"update the required rewrites. If the problem persists, check with your host "
"support on the correct .htaccess file write permission."
msgstr ""

#: include/functions.class.php:1112
msgid ""
"The wp_remote_get() returns a Not Found page, the web.config file does not "
"appears to exists on the server. To fix, go to Settings > Permalinks and save "
"once."
msgstr ""

#: include/functions.class.php:1115
msgid ""
"The wp_remote_get() returns a Not Found page, the test rewrite does not exist. "
"To fix, go to Settings > Permalinks and save once. This can occour if you "
"updated from an old plugin version. "
msgstr ""

#: include/functions.class.php:1119
msgid ""
"The wp_remote_get() returns a Not Found page, probably the Rewrites are not "
"active on your server!"
msgstr ""

#: include/functions.class.php:1139 include/functions.class.php:1369
msgid ""
"A custom rewrite line has been inserted into your rewrite file for testing. The "
msgstr ""

#: include/functions.class.php:1139 include/functions.class.php:1369
msgid ""
"expected to return a JSON response (contains a name and description) The server "
"instead replied a"
msgstr ""

#: include/functions.class.php:1139 include/functions.class.php:1369
msgid "error with the message"
msgstr ""

#: include/functions.class.php:1140 include/functions.class.php:1370
msgid ""
"In certain environments ( e.g. Cloudflare) the plugin may not be allowed to "
"check the test rewrite automatically. If checking manually the "
msgstr ""

#: include/functions.class.php:1140 include/functions.class.php:1370
msgid ""
"if the result is a valid JSON response (contains a name and description), you "
"can"
msgstr ""

#: include/functions.class.php:1143 include/functions.class.php:1373
msgid ""
"If manually checking the Test URL fails too, you need to get in touch with your "
"server support for a fix. The rewrite engine is either disabled for your "
"account or their internal set-up does not allow such rewrites. "
msgstr ""

#: include/functions.class.php:1155 include/functions.class.php:1267
#: include/functions.class.php:1386
msgid ""
"The wp_remote_get() returns an invalid JSON data, probably the server blocks "
"custom rewrites."
msgstr ""

#: include/functions.class.php:1192 include/functions.class.php:1255
#: include/functions.class.php:1387
msgid "Make a fix and manually check the "
msgstr ""

#: include/functions.class.php:1228 include/functions.class.php:1342
msgid ""
"The wp_remote_get() returns a <b>Not Found</b> page, the web.config file does "
"not appears to exists on the server. To fix, go to Settings > Permalinks and "
"save once."
msgstr ""

#: include/functions.class.php:1231 include/functions.class.php:1345
msgid ""
"The wp_remote_get() returns a <b>Not Found</b> page, the test rewrite does not "
"exist. To fix, go to Settings > Permalinks and save once. This can occour if "
"you updated from an old plugin version. "
msgstr ""

#: include/functions.class.php:1235 include/functions.class.php:1349
msgid ""
"The wp_remote_get() returns a <b>Not Found</b> page, probably the Rewrites are "
"not active on your server!"
msgstr ""

#: include/functions.class.php:2300 modules/components/admin-login_php.php:206
msgid "Hello"
msgstr ""

#: include/functions.class.php:2301
msgid ""
"This is a system automated message to inform that you can always use a recovery "
"link if something go wrong"
msgstr ""

#: include/functions.class.php:2302
msgid "Please keep this URL to a safe place."
msgstr ""

#: include/functions.class.php:2434
msgid "The plugin options have been reset successfully."
msgstr ""

#: include/functions.class.php:2441
msgid ""
"Ensure the .htaccess file does not contain any WP-Hide rewrite lines. The "
"plugin already attempts to clear the lines, if the operation fails, they are "
"required to be removed manually. "
msgstr ""

#: include/functions.class.php:2448
msgid ""
"Ensure the web.config file does not contain any WP-Hide rewrite lines. The "
"plugin already attempts to clear the lines, if the operation fails, they are "
"required to be removed manually. "
msgstr ""

#: include/functions.class.php:2455 include/functions.class.php:2542
msgid "Continue to your Site"
msgstr ""

#: include/functions.class.php:2492
msgid "Headers Recovery"
msgstr ""

#: include/functions.class.php:2493
msgid "The plugin Headers options have been disabled successfully."
msgstr ""

#: include/functions.class.php:2500
msgid ""
"Ensure the .htaccess file does not contain any rewrite Header lines. The plugin "
"already attempted to clear the data. If the operation fails, manual removal is "
"required."
msgstr ""

#: include/functions.class.php:2507
msgid ""
"Ensure the web.config file does not contain any rewrite Header lines. The "
"plugin already attempted to clear the data. If the operation fails, manual "
"removal is required."
msgstr ""

#: include/functions.class.php:2518
msgid ""
"Your site use WPEngine! You need to get in touch with live support and ask to "
"remove the custom Nginx Header rewrite code from your account."
msgstr ""

#: include/functions.class.php:2524
msgid ""
"Your site use Kinsta! You need to get in touch with live support and ask to "
"remove the custom Nginx Header rewrite code from your account."
msgstr ""

#: include/functions.class.php:2531
msgid "Check with your Nginx config file located usually at"
msgstr ""

#: include/functions.class.php:2531
msgid "and remove any Header rewrite rules within"
msgstr ""

#: include/functions.class.php:2532
msgid "After the configuration file update"
msgstr ""

#: include/functions.class.php:2532
msgid "Test"
msgstr ""

#: include/functions.class.php:2532
msgid "the new data using "
msgstr ""

#: include/functions.class.php:2532
msgid "If successfully compiled, restart the Nginx service."
msgstr ""

#: include/functions.class.php:2815
#, php-format
msgid "The %1$s plugin header is deprecated. Use %2$s instead."
msgstr ""

#: include/functions.class.php:3385
msgid ""
"Help us to maintain this plugin by sending improvements, suggestions and "
"reporting any issues at "
msgstr ""

#: include/functions.class.php:3387
msgid "Did you know there is a"
msgstr ""

#: include/functions.class.php:3387
msgid "version of this plug-in?"
msgstr ""

#: include/functions.class.php:3389
msgid ""
"Did you find this plugin useful? Please support our work by submitting a "
"review, spread the word about the code, or write an article about the plugin in "
"your blog with a link to development site"
msgstr ""

#: include/widgets.class.php:56
msgid "Run a fist scan to determine the current protection level of your website."
msgstr ""

#: include/wph.class.php:407
msgid ""
"Are you sure to reset the current page settings? All options will be changed to "
"default. An Save is still required for the page."
msgstr ""

#: include/wph.class.php:408
msgid ""
"Are you sure to reset all settings? All options will be removed. Manual removal "
"of rewrite lines is required if no access from PHP."
msgstr ""

#: include/wph.class.php:409
msgid ""
"This creates a sample setup for Headers. That will overwrite any Headers "
"settings previously created through the plugin options. Are you sure?"
msgstr ""

#: include/wph.class.php:562
msgid "All Settings where restored to default"
msgstr ""

#: include/wph.class.php:570
msgid "Headers Sample Setup deployed successfully."
msgstr ""

#: include/wph.class.php:638
msgid "Cache cleared"
msgstr ""

#: include/wph.class.php:704
msgid "WP Hide Security Overview"
msgstr ""

#: modules/components/admin-admin_url.php:68
msgid "Create a new admin url instead default /wp-admin and /login."
msgstr ""

#: modules/components/admin-admin_url.php:72
#: modules/components/admin-admin_url.php:89
#: modules/components/admin-admin_url.php:112
#: modules/components/admin-login_php.php:85
#: modules/components/admin-login_php.php:108
#: modules/components/admin-login_php.php:135 modules/components/cdn-setup.php:44
#: modules/components/general-admin-bar.php:96
#: modules/components/general-block-detectors.php:48
#: modules/components/general-core.php:47
#: modules/components/general-emulate.php:46
#: modules/components/general-feed.php:46
#: modules/components/general-headers.php:81
#: modules/components/general-headers.php:101
#: modules/components/general-headers.php:120
#: modules/components/general-headers.php:140
#: modules/components/general-html.php:117 modules/components/general-html.php:135
#: modules/components/general-html.php:162 modules/components/general-html.php:181
#: modules/components/general-html.php:200 modules/components/general-html.php:219
#: modules/components/general-html.php:238 modules/components/general-meta.php:162
#: modules/components/general-meta.php:182 modules/components/general-meta.php:214
#: modules/components/general-meta.php:232 modules/components/general-meta.php:250
#: modules/components/general-meta.php:270 modules/components/general-meta.php:290
#: modules/components/general-meta.php:310 modules/components/general-meta.php:330
#: modules/components/general-meta.php:350
#: modules/components/general-oembed.php:44
#: modules/components/general-robots-txt.php:46
#: modules/components/general-scripts.php:45
#: modules/components/general-styles.php:56
#: modules/components/general-styles.php:75
#: modules/components/general-user-interactions.php:152
#: modules/components/general-user-interactions.php:171
#: modules/components/general-user-interactions.php:190
#: modules/components/general-user-interactions.php:208
#: modules/components/general-user-interactions.php:226
#: modules/components/general-user-interactions.php:244
#: modules/components/general-user-interactions.php:262
#: modules/components/general-user-interactions.php:281
#: modules/components/general-user-interactions.php:300
#: modules/components/general-user-interactions.php:319
#: modules/components/general-wpemoji.php:58
#: modules/components/general-wpemoji.php:76
#: modules/components/login_2fa_app.php:50
#: modules/components/login_2fa_defaults.php:100
#: modules/components/login_2fa_defaults.php:126
#: modules/components/login_2fa_defaults.php:139
#: modules/components/login_2fa_defaults.php:162
#: modules/components/login_2fa_defaults.php:189
#: modules/components/login_2fa_email.php:50
#: modules/components/login_2fa_recovery_codes.php:50
#: modules/components/login_captcha.php:104
#: modules/components/rewrite-author.php:69
#: modules/components/rewrite-author.php:85
#: modules/components/rewrite-author.php:110
#: modules/components/rewrite-comments.php:58
#: modules/components/rewrite-comments.php:75
#: modules/components/rewrite-json-rest.php:136
#: modules/components/rewrite-json-rest.php:155
#: modules/components/rewrite-json-rest.php:181
#: modules/components/rewrite-json-rest.php:208
#: modules/components/rewrite-json-rest.php:236
#: modules/components/rewrite-json-rest.php:254
#: modules/components/rewrite-json-rest.php:272
#: modules/components/rewrite-new_include_path.php:55
#: modules/components/rewrite-new_include_path.php:73
#: modules/components/rewrite-new_plugin_path.php:93
#: modules/components/rewrite-new_plugin_path.php:109
#: modules/components/rewrite-new_plugin_path.php:154
#: modules/components/rewrite-new_theme_path.php:127
#: modules/components/rewrite-new_theme_path.php:145
#: modules/components/rewrite-new_theme_path.php:165
#: modules/components/rewrite-new_theme_path.php:193
#: modules/components/rewrite-new_theme_path.php:211
#: modules/components/rewrite-new_theme_path.php:231
#: modules/components/rewrite-new_upload_path.php:57
#: modules/components/rewrite-new_upload_path.php:73
#: modules/components/rewrite-new_xml-rpc-path.php:75
#: modules/components/rewrite-new_xml-rpc-path.php:93
#: modules/components/rewrite-new_xml-rpc-path.php:114
#: modules/components/rewrite-new_xml-rpc-path.php:131
#: modules/components/rewrite-new_xml-rpc-path.php:148
#: modules/components/rewrite-root-files.php:118
#: modules/components/rewrite-root-files.php:136
#: modules/components/rewrite-root-files.php:154
#: modules/components/rewrite-root-files.php:186
#: modules/components/rewrite-root-files.php:211
#: modules/components/rewrite-root-files.php:229
#: modules/components/rewrite-root-files.php:247
#: modules/components/rewrite-search.php:57
#: modules/components/rewrite-search.php:75
#: modules/components/rewrite-slash.php:45
#: modules/components/rewrite-wp_content_path.php:55
#: modules/components/rewrite-wp_content_path.php:73
#: modules/components/security-add_headers.php:70
#: modules/components/security-add_headers.php:90
#: modules/components/security-add_headers.php:109
#: modules/components/security-header-cross-origin-embedder-policy.php:48
#: modules/components/security-header-cross-origin-opener-policy.php:49
#: modules/components/security-header-cross-origin-resource-policy.php:52
#: modules/components/security-header-referrer-policy.php:49
#: modules/components/security-header-x-content-type-options.php:49
#: modules/components/security-header-x-download-options.php:49
#: modules/components/security-header-x-frame-options.php:52
#: modules/components/security-header-x-permitted-cross-domain-policies.php:49
#: modules/components/security-header-x-xss-protection.php:49
msgid "Help"
msgstr ""

#: modules/components/admin-admin_url.php:73
msgid ""
"Despite the flexibility of WordPress framework, there are few ways to configure "
"the admin login url customization for making a bit safer against unauthorized "
"access and brute force attempts. All methods are not provided out of the box "
"through WordPress core but require custom code to make it happen."
msgstr ""

#: modules/components/admin-admin_url.php:74
msgid ""
"This feature provide an easy way to change the default /wp-admin/ to a "
"different slug."
msgstr ""

#: modules/components/admin-admin_url.php:75
msgid ""
"Once changed, the new url will be used to access all Dashboard sections, from "
"Posts and Pages section to Plugins, Appearance and Settings."
msgstr ""

#: modules/components/admin-admin_url.php:83
msgid "Disable Admin Url redirect to Login page"
msgstr ""

#: modules/components/admin-admin_url.php:85
msgid "Disable the customized Admin Url redirect to Login page"
msgstr ""

#: modules/components/admin-admin_url.php:89
#: modules/components/admin-admin_url.php:106
#: modules/components/admin-admin_url.php:112
msgid "Block default Admin Url"
msgstr ""

#: modules/components/admin-admin_url.php:90
msgid ""
"The option provides the ability to control the redirection behavior of the "
"customized URL to the login page."
msgstr ""

#: modules/components/admin-admin_url.php:91
msgid ""
"By default, when a non-logged-in user attempts to access the WordPress admin "
"area via the customized URL, they are automatically redirected to the login "
"page for authentication."
msgstr ""

#: modules/components/admin-admin_url.php:92
msgid "Instead it will be redirected to homepage."
msgstr ""

#: modules/components/admin-admin_url.php:93
msgid ""
"The option might interfere with specific plugins that use redirects when "
"calling the admin URL."
msgstr ""

#: modules/components/admin-admin_url.php:98
#: modules/components/admin-admin_url.php:126
#: modules/components/admin-login_php.php:121
#: modules/components/general-admin-bar.php:102
#: modules/components/general-block-detectors.php:61
#: modules/components/general-core.php:57
#: modules/components/general-emulate.php:60
#: modules/components/general-feed.php:56
#: modules/components/general-headers.php:89
#: modules/components/general-headers.php:108
#: modules/components/general-headers.php:128
#: modules/components/general-headers.php:146
#: modules/components/general-html.php:123 modules/components/general-html.php:147
#: modules/components/general-html.php:169 modules/components/general-html.php:188
#: modules/components/general-html.php:207 modules/components/general-html.php:226
#: modules/components/general-html.php:245 modules/components/general-meta.php:170
#: modules/components/general-meta.php:190 modules/components/general-meta.php:202
#: modules/components/general-meta.php:220 modules/components/general-meta.php:238
#: modules/components/general-meta.php:258 modules/components/general-meta.php:278
#: modules/components/general-meta.php:298 modules/components/general-meta.php:318
#: modules/components/general-meta.php:338 modules/components/general-meta.php:358
#: modules/components/general-oembed.php:49
#: modules/components/general-robots-txt.php:55
#: modules/components/general-scripts.php:56
#: modules/components/general-styles.php:63
#: modules/components/general-styles.php:81
#: modules/components/general-user-interactions.php:159
#: modules/components/general-user-interactions.php:178
#: modules/components/general-user-interactions.php:196
#: modules/components/general-user-interactions.php:214
#: modules/components/general-user-interactions.php:232
#: modules/components/general-user-interactions.php:250
#: modules/components/general-user-interactions.php:269
#: modules/components/general-user-interactions.php:288
#: modules/components/general-user-interactions.php:306
#: modules/components/general-user-interactions.php:325
#: modules/components/general-wpemoji.php:64
#: modules/components/general-wpemoji.php:82
#: modules/components/login_2fa_app.php:70
#: modules/components/login_2fa_defaults.php:114
#: modules/components/login_2fa_defaults.php:150
#: modules/components/login_2fa_defaults.php:198
#: modules/components/login_2fa_email.php:62
#: modules/components/login_2fa_recovery_codes.php:62
#: modules/components/rewrite-author.php:97
#: modules/components/rewrite-author.php:116
#: modules/components/rewrite-comments.php:81
#: modules/components/rewrite-json-rest.php:143
#: modules/components/rewrite-json-rest.php:169
#: modules/components/rewrite-json-rest.php:196
#: modules/components/rewrite-json-rest.php:223
#: modules/components/rewrite-json-rest.php:242
#: modules/components/rewrite-json-rest.php:260
#: modules/components/rewrite-json-rest.php:278
#: modules/components/rewrite-new_include_path.php:85
#: modules/components/rewrite-new_plugin_path.php:121
#: modules/components/rewrite-new_theme_path.php:178
#: modules/components/rewrite-new_theme_path.php:244
#: modules/components/rewrite-new_upload_path.php:85
#: modules/components/rewrite-new_xml-rpc-path.php:103
#: modules/components/rewrite-new_xml-rpc-path.php:120
#: modules/components/rewrite-new_xml-rpc-path.php:137
#: modules/components/rewrite-new_xml-rpc-path.php:153
#: modules/components/rewrite-root-files.php:124
#: modules/components/rewrite-root-files.php:142
#: modules/components/rewrite-root-files.php:161
#: modules/components/rewrite-root-files.php:199
#: modules/components/rewrite-root-files.php:217
#: modules/components/rewrite-root-files.php:235
#: modules/components/rewrite-root-files.php:253
#: modules/components/rewrite-search.php:81
#: modules/components/rewrite-slash.php:59
#: modules/components/rewrite-wp_content_path.php:85
#: modules/components/security-add_headers.php:78
#: modules/components/security-add_headers.php:97
#: modules/components/security-add_headers.php:115
msgid "No"
msgstr ""

#: modules/components/admin-admin_url.php:99
#: modules/components/admin-admin_url.php:127
#: modules/components/admin-login_php.php:122
#: modules/components/general-admin-bar.php:103
#: modules/components/general-block-detectors.php:62
#: modules/components/general-core.php:58 modules/components/general-feed.php:57
#: modules/components/general-headers.php:90
#: modules/components/general-headers.php:109
#: modules/components/general-headers.php:129
#: modules/components/general-headers.php:147
#: modules/components/general-html.php:124 modules/components/general-html.php:170
#: modules/components/general-html.php:189 modules/components/general-html.php:208
#: modules/components/general-html.php:227 modules/components/general-html.php:246
#: modules/components/general-meta.php:171 modules/components/general-meta.php:191
#: modules/components/general-meta.php:203 modules/components/general-meta.php:221
#: modules/components/general-meta.php:239 modules/components/general-meta.php:259
#: modules/components/general-meta.php:279 modules/components/general-meta.php:299
#: modules/components/general-meta.php:319 modules/components/general-meta.php:339
#: modules/components/general-meta.php:359
#: modules/components/general-oembed.php:50
#: modules/components/general-robots-txt.php:56
#: modules/components/general-scripts.php:57
#: modules/components/general-styles.php:64
#: modules/components/general-styles.php:82
#: modules/components/general-user-interactions.php:160
#: modules/components/general-user-interactions.php:179
#: modules/components/general-user-interactions.php:197
#: modules/components/general-user-interactions.php:215
#: modules/components/general-user-interactions.php:233
#: modules/components/general-user-interactions.php:251
#: modules/components/general-user-interactions.php:270
#: modules/components/general-user-interactions.php:289
#: modules/components/general-user-interactions.php:307
#: modules/components/general-user-interactions.php:326
#: modules/components/general-wpemoji.php:65
#: modules/components/general-wpemoji.php:83
#: modules/components/login_2fa_app.php:71
#: modules/components/login_2fa_defaults.php:115
#: modules/components/login_2fa_defaults.php:151
#: modules/components/login_2fa_defaults.php:199
#: modules/components/login_2fa_email.php:63
#: modules/components/login_2fa_recovery_codes.php:63
#: modules/components/rewrite-author.php:98
#: modules/components/rewrite-author.php:117
#: modules/components/rewrite-comments.php:82
#: modules/components/rewrite-json-rest.php:144
#: modules/components/rewrite-json-rest.php:170
#: modules/components/rewrite-json-rest.php:197
#: modules/components/rewrite-json-rest.php:243
#: modules/components/rewrite-json-rest.php:261
#: modules/components/rewrite-json-rest.php:279
#: modules/components/rewrite-new_include_path.php:86
#: modules/components/rewrite-new_plugin_path.php:122
#: modules/components/rewrite-new_theme_path.php:179
#: modules/components/rewrite-new_theme_path.php:245
#: modules/components/rewrite-new_upload_path.php:86
#: modules/components/rewrite-new_xml-rpc-path.php:104
#: modules/components/rewrite-new_xml-rpc-path.php:121
#: modules/components/rewrite-new_xml-rpc-path.php:138
#: modules/components/rewrite-new_xml-rpc-path.php:154
#: modules/components/rewrite-root-files.php:125
#: modules/components/rewrite-root-files.php:143
#: modules/components/rewrite-root-files.php:162
#: modules/components/rewrite-root-files.php:200
#: modules/components/rewrite-root-files.php:218
#: modules/components/rewrite-root-files.php:236
#: modules/components/rewrite-root-files.php:254
#: modules/components/rewrite-search.php:82
#: modules/components/rewrite-slash.php:60
#: modules/components/rewrite-wp_content_path.php:86
#: modules/components/security-add_headers.php:79
#: modules/components/security-add_headers.php:98
#: modules/components/security-add_headers.php:116
msgid "Yes"
msgstr ""

#: modules/components/admin-admin_url.php:108
msgid "Block default admin url and files from being accesible."
msgstr ""

#: modules/components/admin-admin_url.php:113
msgid ""
"If set to Yes, the old admin url will be blocked and a default theme 404 error "
"page will be returned."
msgstr ""

#: modules/components/admin-admin_url.php:114
msgid ""
"Ensure the New Admin Url option works correctly on your server before activate "
"this."
msgstr ""

#: modules/components/admin-admin_url.php:121
#: modules/components/admin-login_php.php:116
#: modules/components/rewrite-json-rest.php:164
#: modules/components/rewrite-json-rest.php:191
#: modules/components/rewrite-json-rest.php:218
#: modules/components/rewrite-new_include_path.php:80
#: modules/components/rewrite-new_plugin_path.php:116
#: modules/components/rewrite-new_theme_path.php:173
#: modules/components/rewrite-new_theme_path.php:239
#: modules/components/rewrite-new_upload_path.php:80
#: modules/components/rewrite-new_xml-rpc-path.php:99
#: modules/components/rewrite-root-files.php:194
#: modules/components/rewrite-wp_content_path.php:80
msgid "This is an advanced option !"
msgstr ""

#: modules/components/admin-admin_url.php:121
msgid ""
"This can break the layour of dashboard admin if server not supporting the "
"feature. Ensure `New Admin Url` option works fine before activate this.<br />If "
"not working, use the recovery link to revert."
msgstr ""

#: modules/components/admin-login_php.php:81
msgid "Map a new wp-login.php instead default."
msgstr ""

#: modules/components/admin-login_php.php:86
msgid ""
"There are a lot of security issues that come from having your login page open "
"to the public. Most specifically, brute force attacks. Because of the ubiquity "
"of WordPress, these kinds of attacks are becoming more and more common."
msgstr ""

#: modules/components/admin-login_php.php:87
msgid ""
"Map a new wp-login.php instead default prevent hackers boot to attempt to brute "
"force a site login. Being known only by the site owner, the url itself becomes "
"private."
msgstr ""

#: modules/components/admin-login_php.php:88
msgid "Make sure you keep the new login url to a safe place, in case to forget."
msgstr ""

#: modules/components/admin-login_php.php:97
msgid ""
"Make sure your log-in url is not already modified by another plugin or theme. "
"In such case, you should disable other code and take advantage of these "
"features."
msgstr ""

#: modules/components/admin-login_php.php:104
#: modules/components/admin-login_php.php:108
msgid "Block default wp-login.php"
msgstr ""

#: modules/components/admin-login_php.php:105
msgid "Block default wp-login.php file from being accesible."
msgstr ""

#: modules/components/admin-login_php.php:109
msgid ""
"If set to Yes, the old login url will be blocked and a default theme 404 error "
"page will be returned."
msgstr ""

#: modules/components/admin-login_php.php:110
msgid ""
"Ensure the New wp-login.php option works correctly on your server before "
"activate this."
msgstr ""

#: modules/components/admin-login_php.php:116
msgid ""
"This can break the login page if server not supporting the feature. Ensure `New "
"wp-login.php` option works fine before activate this.<br />If not working, use "
"the recovery link to revert."
msgstr ""

#: modules/components/admin-login_php.php:129
msgid "Custom Login page Logo"
msgstr ""

#: modules/components/admin-login_php.php:131
msgid "Change the default WordPress login page Logo."
msgstr ""

#: modules/components/admin-login_php.php:135
msgid "Custom Login Logo"
msgstr ""

#: modules/components/admin-login_php.php:136
msgid ""
"The feature in the WP Hide plugin allows you to replace the standard WordPress "
"login page logo with a custom image of your choice. This customization enhances "
"your site's branding by displaying your logo on the login page, admin "
"dashboard, and other areas where the default logo appears. To use this feature, "
"simply upload your desired logo in the WP Hide settings and save the changes. "
"Your new logo will be displayed immediately, providing a more personalized and "
"professional appearance for your WordPress site."
msgstr ""

#: modules/components/admin-login_php.php:137
msgid "Recommended width size is 320px."
msgstr ""

#: modules/components/admin-login_php.php:207
msgid ""
"This is an automated message to inform that your login url has been changed at"
msgstr ""

#: modules/components/admin-login_php.php:208
msgid "The new login url is"
msgstr ""

#: modules/components/admin-login_php.php:209
msgid ""
"Additionally, you can use the following link to recover the default login/admin "
"access: "
msgstr ""

#: modules/components/admin-login_php.php:210
msgid ""
"Please ensure the safety of this URL for potential recovery in case of "
"forgetfulness."
msgstr ""

#: modules/components/cdn-setup.php:40 modules/components/cdn-setup.php:44
msgid "CDN Url"
msgstr ""

#: modules/components/cdn-setup.php:41
msgid ""
"Some CDN providers (like stackpath.com ) replace site assets with custom url, "
"enter here such url. Otherwise this option should stay empty."
msgstr ""

#: modules/components/cdn-setup.php:45
msgid ""
"A Content Delivery Network - CDN - is a network of servers located around the "
"globe in fundamental spots with fast access. It takes a while for a web page to "
"load especially if the server is located far away from the user. So they are "
"designed to host and deliver copies of your site's static and dynamic content "
"such as images, CSS, JavaScript, audio and video streams."
msgstr ""

#: modules/components/cdn-setup.php:46
msgid "Sample CDN url:"
msgstr ""

#: modules/components/cdn-setup.php:48
msgid ""
"Enter a CDN Url to allow the plugin to process assets provided through CDN "
"service."
msgstr ""

#: modules/components/general-admin-bar.php:86
msgid ""
"The admin bar is a floating bar that contains useful administration screen "
"links such as add a new post, see pending comments, edit your profile etc. It "
"can be extended by plugins to add additional functionality for example SEO and "
"more."
msgstr ""

#: modules/components/general-admin-bar.php:88
#: modules/components/general-admin-bar.php:93
msgid "Remove WordPress Admin Bar for "
msgstr ""

#: modules/components/general-admin-bar.php:88
msgid "role"
msgstr ""

#: modules/components/general-admin-bar.php:92
#: modules/components/general-admin-bar.php:96
msgid "Remove Admin Bar for "
msgstr ""

#: modules/components/general-admin-bar.php:93
msgid "role, which is being displayed by default on front side of your website."
msgstr ""

#: modules/components/general-admin-bar.php:96
msgid "role."
msgstr ""

#: modules/components/general-block-detectors.php:44
msgid "Block Theme / Plugin detectors."
msgstr ""

#: modules/components/general-block-detectors.php:45
msgid "Block common Theme / Plugin detectors and scanners."
msgstr ""

#: modules/components/general-block-detectors.php:48
msgid "Block Theme / Plugin detectors"
msgstr ""

#: modules/components/general-block-detectors.php:49
msgid ""
"Enhance your website's privacy and security with the Block Theme Detectors "
"feature. This tool prevents known user agents and IP addresses associated with "
"popular theme detectors from accessing your site's design and theme-related "
"information. By doing so, it keeps your creative choices private and reduces "
"the risk of targeted attacks exploiting specific theme vulnerabilities."
msgstr ""

#: modules/components/general-block-detectors.php:50
msgid "Key Benefits"
msgstr ""

#: modules/components/general-block-detectors.php:52
msgid ""
"Privacy: Protect your website's theme details from being copied or analyzed"
msgstr ""

#: modules/components/general-block-detectors.php:53
msgid "Security: Minimize exposure to potential threats"
msgstr ""

#: modules/components/general-block-detectors.php:54
msgid "Performance: Optimize server resources by blocking unnecessary traffic"
msgstr ""

#: modules/components/general-block-detectors.php:55
msgid "Competitive Edge: Maintain a unique brand identity"
msgstr ""

#: modules/components/general-core.php:43 modules/components/general-core.php:47
msgid "Disabling Directory Listing"
msgstr ""

#: modules/components/general-core.php:44
msgid "Disabling Directory Listing for server folders."
msgstr ""

#: modules/components/general-core.php:48
msgid ""
"By leveraging a rewrite directive, this feature prevents unauthorized users "
"from browsing server directories, ensuring sensitive files remain inaccessible."
msgstr ""

#: modules/components/general-core.php:49
msgid ""
"Once enabled, the plugin injects the directive into your .htaccess / "
"configuration file ( depending on server type ), blocking directory index views "
"without manual edits. This simple addition fortifies your website by "
"eliminating potential exposure of directory contents, reducing vulnerabilities. "
"Protect assets and maintain a professional appearance by completely hiding file "
"listings."
msgstr ""

#: modules/components/general-core.php:50
msgid "Benefits:"
msgstr ""

#: modules/components/general-core.php:51
msgid "Enhances security by hiding directory structure"
msgstr ""

#: modules/components/general-core.php:52
msgid "Protects sensitive files and assets"
msgstr ""

#: modules/components/general-emulate.php:43
msgid ""
"Use the option to output specific CMSs HTML traces to mislead any peculiar "
"check."
msgstr ""

#: modules/components/general-emulate.php:47
msgid ""
"Using the option the system try to misguide the used WordPress by outputting "
"the wrong traces, of the selected CMS."
msgstr ""

#: modules/components/general-emulate.php:48
msgid ""
"Misleading and making a false lead provides an extra security, as the attacker "
"search and attempt to hack something which not exist."
msgstr ""

#: modules/components/general-emulate.php:49
msgid "The plugin can emulate systems like:"
msgstr ""

#: modules/components/general-emulate.php:50
msgid "- Drupal"
msgstr ""

#: modules/components/general-emulate.php:51
msgid "- Ghost"
msgstr ""

#: modules/components/general-emulate.php:52
msgid "- HubSpot"
msgstr ""

#: modules/components/general-emulate.php:53
msgid "- Joomla"
msgstr ""

#: modules/components/general-emulate.php:54
msgid "- TYPO3"
msgstr ""

#: modules/components/general-emulate.php:55
msgid "- Wix"
msgstr ""

#: modules/components/general-emulate.php:61
msgid "Drupal 8"
msgstr ""

#: modules/components/general-emulate.php:62
msgid "Drupal 9"
msgstr ""

#: modules/components/general-emulate.php:63
msgid "Ghost 4.15"
msgstr ""

#: modules/components/general-emulate.php:64
msgid "Ghost 4.31"
msgstr ""

#: modules/components/general-emulate.php:65
msgid "HubSpot"
msgstr ""

#: modules/components/general-emulate.php:66
msgid "Joomla"
msgstr ""

#: modules/components/general-emulate.php:67
msgid "TYPO3"
msgstr ""

#: modules/components/general-emulate.php:68
msgid "Wix"
msgstr ""

#: modules/components/general-feed.php:42 modules/components/general-feed.php:46
msgid "Remove feed|rdf|rss|rss2|atom links"
msgstr ""

#: modules/components/general-feed.php:43
msgid ""
"Remove feed|rdf|rss|rss2|atom links within head. Also block such content "
"functionality."
msgstr ""

#: modules/components/general-feed.php:47
msgid ""
"A feed is a function of special software that allows feedreaders to access a "
"site, automatically looking for new content and then posting the information "
"about new content and updates to another site. This provides a way for users to "
"keep up with the latest and hottest information posted on different blogging "
"sites."
msgstr ""

#: modules/components/general-feed.php:48
msgid ""
"There are several different kinds of feeds, read by different feedreaders. Some "
"feeds include RSS (alternately defined as 'Rich Site Summary' or 'Really Simple "
"Syndication'), Atom or RDF files."
msgstr ""

#: modules/components/general-feed.php:49 modules/components/general-meta.php:252
#: modules/components/general-meta.php:272 modules/components/general-meta.php:292
#: modules/components/general-meta.php:312 modules/components/general-meta.php:332
#: modules/components/general-meta.php:352
#: modules/components/general-scripts.php:48
msgid "Sample tag:"
msgstr ""

#: modules/components/general-feed.php:51
msgid "Set this option to Yes also disable the feed service."
msgstr ""

#: modules/components/general-headers.php:78
#: modules/components/security-add_headers.php:67
msgid ""
"Remove Link Header being set as default by WordPress which outputs the site "
"JSON url."
msgstr ""

#: modules/components/general-headers.php:82
#: modules/components/security-add_headers.php:71
msgid ""
"HTTP header fields are components of the header section of a request and "
"response messages in the Hypertext Transfer Protocol (HTTP). They define the "
"operating parameters of an HTTP transaction."
msgstr ""

#: modules/components/general-headers.php:83
#: modules/components/general-headers.php:102
#: modules/components/general-headers.php:121
#: modules/components/security-add_headers.php:72
#: modules/components/security-add_headers.php:91
msgid "Sample header:"
msgstr ""

#: modules/components/general-headers.php:97
#: modules/components/general-headers.php:101
#: modules/components/security-add_headers.php:86
#: modules/components/security-add_headers.php:90
msgid "Remove X-Powered-By Header"
msgstr ""

#: modules/components/general-headers.php:98
msgid "Remove X-Powered-By Header if set."
msgstr ""

#: modules/components/general-headers.php:116
#: modules/components/general-headers.php:120
msgid "Remove Server Header"
msgstr ""

#: modules/components/general-headers.php:117
msgid "Remove Server Header if set."
msgstr ""

#: modules/components/general-headers.php:136
#: modules/components/general-headers.php:140
#: modules/components/security-add_headers.php:105
#: modules/components/security-add_headers.php:109
msgid "Remove X-Pingback Header"
msgstr ""

#: modules/components/general-headers.php:137
#: modules/components/security-add_headers.php:106
msgid "Remove X-Pingback Header if being set."
msgstr ""

#: modules/components/general-headers.php:141
#: modules/components/security-add_headers.php:110
msgid ""
"Pingback is one of four types of linkback methods for Web authors to request "
"notification when somebody links to one of their documents. This enables "
"authors to keep track of who is linking to, or referring to their articles. "
"Pingback-enabled resources must either use an X-Pingback header or contain a "
"element to the XML-RPC script."
msgstr ""

#: modules/components/general-html.php:114
msgid "Remove comments from HTML source code."
msgstr ""

#: modules/components/general-html.php:131 modules/components/general-html.php:135
msgid "Minify"
msgstr ""

#: modules/components/general-html.php:132
msgid "Minify HTML, Inline Styles, Inline JavaScripts."
msgstr ""

#: modules/components/general-html.php:136
msgid ""
"When you minify HTML it removes the unnecessary characters and lines in the "
"source code. Indentation, comments, empty lines, etc. are not required in HTML. "
"They just make the file easier to read. Cutting out all this unnecessary stuff "
"can shave down your file size considerably. When you minify HTML code on your "
"website, the server will send a much smaller page to the client making your "
"website load quicker."
msgstr ""

#: modules/components/general-html.php:137
msgid "The Minify component include multiple options:"
msgstr ""

#: modules/components/general-html.php:142
msgid "Minify JavaScript might produce errors for specific plugins."
msgstr ""

#: modules/components/general-html.php:148
msgid "Html"
msgstr ""

#: modules/components/general-html.php:149
msgid "Html & Css"
msgstr ""

#: modules/components/general-html.php:150
msgid "Html & JavaScript"
msgstr ""

#: modules/components/general-html.php:151
#: modules/components/rewrite-json-rest.php:225
msgid "All"
msgstr ""

#: modules/components/general-html.php:158 modules/components/general-html.php:162
msgid "Remove general classes from body tag"
msgstr ""

#: modules/components/general-html.php:159 modules/components/general-html.php:163
msgid "Remove general classes from body tag."
msgstr ""

#: modules/components/general-html.php:164 modules/components/general-html.php:183
#: modules/components/general-html.php:202 modules/components/general-html.php:221
#: modules/components/general-html.php:240
msgid ""
"This can produce layout issues with certain themes, if something break this "
"should be turned off."
msgstr ""

#: modules/components/general-html.php:177 modules/components/general-html.php:181
msgid "Remove ID from Menu items"
msgstr ""

#: modules/components/general-html.php:178 modules/components/general-html.php:182
msgid "Remove ID attribute from all menu items."
msgstr ""

#: modules/components/general-html.php:196 modules/components/general-html.php:200
#: modules/components/general-html.php:215 modules/components/general-html.php:219
msgid "Remove class from Menu items"
msgstr ""

#: modules/components/general-html.php:197
msgid "Remove class attribute from all menu items."
msgstr ""

#: modules/components/general-html.php:201
msgid ""
"Remove class attribute from all menu items. Any classes which include a "
"'current' prefix or contain 'has-children' will be preserved."
msgstr ""

#: modules/components/general-html.php:216 modules/components/general-html.php:220
msgid "Remove general classes from post."
msgstr ""

#: modules/components/general-html.php:234 modules/components/general-html.php:238
msgid "Remove general classes from images"
msgstr ""

#: modules/components/general-html.php:235 modules/components/general-html.php:239
msgid "Remove general classes from media tags."
msgstr ""

#: modules/components/general-meta.php:164 modules/components/general-meta.php:184
msgid "Tag example:"
msgstr ""

#: modules/components/general-meta.php:198
msgid "Remove Shortlink Meta"
msgstr ""

#: modules/components/general-meta.php:199
msgid "Remove shortlink tags within head."
msgstr ""

#: modules/components/general-meta.php:210 modules/components/general-meta.php:214
msgid "Remove DNS Prefetch"
msgstr ""

#: modules/components/general-meta.php:211
msgid "Remove DNS Prefetch meta generated tag."
msgstr ""

#: modules/components/general-meta.php:215
msgid ""
"DNS prefetching allows you to resolve domain names (perform a DNS lookup in the "
"background) before a user clicks on a link, which in turn can help improve "
"performance."
msgstr ""

#: modules/components/general-meta.php:228 modules/components/general-meta.php:232
msgid "Remove Resource Hints"
msgstr ""

#: modules/components/general-meta.php:229
msgid ""
"Remove Resource Hints meta generated tags within head (eg dns-prefetch, "
"preconnect)."
msgstr ""

#: modules/components/general-meta.php:233
msgid ""
"DNS prefetching and preconect allows you to resolve domain names before a user "
"clicks on a link, which in turn can help and slightly improve performance."
msgstr ""

#: modules/components/general-meta.php:247
msgid "Remove the wlwmanifest tag within head."
msgstr ""

#: modules/components/general-meta.php:251
msgid ""
"The above link is actually used by Windows Live Writer. If you don't te "
"application, this is just unnecessary code."
msgstr ""

#: modules/components/general-meta.php:266 modules/components/general-meta.php:270
#: modules/components/rewrite-json-rest.php:232
msgid "Disable output the REST API link tag into page header"
msgstr ""

#: modules/components/general-meta.php:267
#: modules/components/rewrite-json-rest.php:233
msgid "By default a REST API link tag is being append to HTML."
msgstr ""

#: modules/components/general-meta.php:271
msgid "This option disable the tag output with the JSON API url."
msgstr ""

#: modules/components/general-meta.php:286 modules/components/general-meta.php:290
msgid "Remove rsd_link Meta"
msgstr ""

#: modules/components/general-meta.php:287
msgid "Remove the rsd_link tag within head."
msgstr ""

#: modules/components/general-meta.php:291
msgid ""
"This helps to hide the link to the Really Simple Discovery service endpoint."
msgstr ""

#: modules/components/general-meta.php:306 modules/components/general-meta.php:310
#: modules/components/general-meta.php:330 modules/components/general-meta.php:350
msgid "Remove adjacent_posts_rel Meta"
msgstr ""

#: modules/components/general-meta.php:307
msgid "Remove the adjacent_posts_rel tag within head."
msgstr ""

#: modules/components/general-meta.php:311
msgid "This helps to hide the post adjacent tags."
msgstr ""

#: modules/components/general-meta.php:326
msgid "Remove profile link"
msgstr ""

#: modules/components/general-meta.php:327
msgid "Remove profile link meta tag within head."
msgstr ""

#: modules/components/general-meta.php:331
msgid "This helps to hide the profile tags."
msgstr ""

#: modules/components/general-meta.php:346
msgid "Remove canonical link"
msgstr ""

#: modules/components/general-meta.php:347
msgid "Remove canonical link meta tag within head."
msgstr ""

#: modules/components/general-meta.php:351
msgid ""
"The rel=canonical element, often called the 'canonical link', is an HTML "
"element that helps webmasters prevent duplicate content issues. It does this by "
"specifying the 'canonical URL', the 'preferred' version of a web page - the "
"original source, even."
msgstr ""

#: modules/components/general-oembed.php:40
#: modules/components/general-oembed.php:44
msgid "Remove Oembed"
msgstr ""

#: modules/components/general-oembed.php:41
msgid "Remove Oembed tags from header."
msgstr ""

#: modules/components/general-oembed.php:45
msgid ""
"WordPress oEmbed recognizes URLs to a number of services, for example Youtube "
"videos. When WordPress sees the URL it will connect to the external service "
"(Youtube) and ask for the relevant HTML code to embed the video into the page "
"or post."
msgstr ""

#: modules/components/general-robots-txt.php:42
#: modules/components/general-robots-txt.php:46
msgid "Change the default urls within Robots.txt"
msgstr ""

#: modules/components/general-robots-txt.php:43
msgid ""
"Change any default url which is being automatically generated by WordPress when "
"called robots.txt."
msgstr ""

#: modules/components/general-robots-txt.php:47
msgid ""
"The robots.txt file plays a major role in search engine ranking. It blocks "
"search engine bots and helps index and crawl important parts of your site."
msgstr ""

#: modules/components/general-robots-txt.php:48
msgid ""
"As default the robots.txt also includes an allow clause to admin URL and admin-"
"ajax.php url. Once customized those areas, the new slugs might not want to be "
"show to anyone. Turn this option to Yes removed any reference to new wp-admin "
"and admin-ajax.php."
msgstr ""

#: modules/components/general-robots-txt.php:49
msgid "Sample robots.txt url:"
msgstr ""

#: modules/components/general-scripts.php:41
#: modules/components/general-scripts.php:45
#: modules/components/general-styles.php:52
#: modules/components/general-styles.php:56
#: modules/components/security-add_headers.php:70
msgid "Remove Version"
msgstr ""

#: modules/components/general-scripts.php:42
msgid "Remove version number from enqueued script files."
msgstr ""

#: modules/components/general-scripts.php:46
msgid ""
"This provide a method to remove the JavaScript version number which is being "
"append at the end of every script file. Generally this is intended to be a "
"plain information upon the JavaScript code version, however not being used "
"within any functionality or code run."
msgstr ""

#: modules/components/general-scripts.php:47
msgid ""
"Keeping version number for scripts provide additional information to hackers "
"which try to identify specific JavaScript code and version which know as being "
"vulnerable."
msgstr ""

#: modules/components/general-scripts.php:50
msgid "Once option set to Yes the tag becomes:"
msgstr ""

#: modules/components/general-styles.php:53
msgid "Remove version number from enqueued style files."
msgstr ""

#: modules/components/general-styles.php:57
msgid ""
"This provide a method to remove the Style file version number which is being "
"append at the end of every style tag. Generally this is intended to be a plain "
"information upon the style code version, however not being used within any "
"functionality or code run."
msgstr ""

#: modules/components/general-styles.php:58
msgid ""
"Keeping version number for styles provide additional information to hackers "
"which try to identify specific code and version which know as being vulnerable."
msgstr ""

#: modules/components/general-styles.php:71
#: modules/components/general-styles.php:75
msgid "Remove ID from link tags"
msgstr ""

#: modules/components/general-styles.php:72
msgid "Remove ID attribute from all link tags which include a stylesheet."
msgstr ""

#: modules/components/general-styles.php:76
msgid ""
"This provide a method to remove the Style file ID attribute which generally has "
"no usage."
msgstr ""

#: modules/components/general-user-interactions.php:148
msgid "Disable Mouse right click"
msgstr ""

#: modules/components/general-user-interactions.php:149
msgid "Disable mouse right click on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:152
msgid "Disable right Mouse click"
msgstr ""

#: modules/components/general-user-interactions.php:153
msgid ""
"Disable right mouse click on your pages can protect your site content from "
"being copied."
msgstr ""

#: modules/components/general-user-interactions.php:154
msgid ""
"Some plugins, mainly visual editors, use mouse right-click, if use such code "
"this option should be set to No."
msgstr ""

#: modules/components/general-user-interactions.php:167
#: modules/components/general-user-interactions.php:171
msgid "Disable Text Selection"
msgstr ""

#: modules/components/general-user-interactions.php:168
msgid "Disable Text Selection on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:172
msgid "When the option is active, the text selection on pages is not possible."
msgstr ""

#: modules/components/general-user-interactions.php:173
msgid "This is useful when don't want the site texts to be copied."
msgstr ""

#: modules/components/general-user-interactions.php:186
#: modules/components/general-user-interactions.php:190
msgid "Disable Copy"
msgstr ""

#: modules/components/general-user-interactions.php:187
msgid "Disable text copy on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:191
msgid "Through this option, the browser copy functionality is disabled."
msgstr ""

#: modules/components/general-user-interactions.php:204
#: modules/components/general-user-interactions.php:208
msgid "Disable Cut"
msgstr ""

#: modules/components/general-user-interactions.php:205
msgid "Disable text cut on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:209
msgid "Through this option, the browser cut functionality is disabled."
msgstr ""

#: modules/components/general-user-interactions.php:222
#: modules/components/general-user-interactions.php:226
msgid "Disable Paste"
msgstr ""

#: modules/components/general-user-interactions.php:223
msgid "Disable text paste on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:227
msgid "Through this option, the browser paste functionality is disabled."
msgstr ""

#: modules/components/general-user-interactions.php:240
#: modules/components/general-user-interactions.php:244
msgid "Disable Print"
msgstr ""

#: modules/components/general-user-interactions.php:241
msgid "Disable Print function on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:245
msgid ""
"When using the option, the browser Print dialogue is not available so a site "
"print is disabled."
msgstr ""

#: modules/components/general-user-interactions.php:258
#: modules/components/general-user-interactions.php:262
msgid "Disable Print Screen"
msgstr ""

#: modules/components/general-user-interactions.php:259
msgid "Disable Print Screen function on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:263
msgid ""
"The Print Screen function captures an image of the entire screen and copies it "
"to the Clipboard in the computer's memory."
msgstr ""

#: modules/components/general-user-interactions.php:264
msgid "If the functionality is not required, the option helps to disable it."
msgstr ""

#: modules/components/general-user-interactions.php:277
#: modules/components/general-user-interactions.php:281
msgid "Disable Developer Tools"
msgstr ""

#: modules/components/general-user-interactions.php:278
msgid "Disable the browser Developr Tools on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:282
msgid ""
"Every modern web browser includes a powerful tool called Developer Tools. "
"Through the application, a user can inspect currently-loaded HTML, CSS and "
"JavaScript."
msgstr ""

#: modules/components/general-user-interactions.php:283
msgid ""
"To prevent the user from deeply checking into your site architecture, the "
"browser Inspect can be disabled through this option. "
msgstr ""

#: modules/components/general-user-interactions.php:296
#: modules/components/general-user-interactions.php:300
msgid "Disable View Source"
msgstr ""

#: modules/components/general-user-interactions.php:297
msgid "Disable the browser view source on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:301
msgid ""
"The page source is an HTML set of tags code. An HTML tag is an element that, "
"along with CSS and JavaScript, tells the Web browser what to do and how to "
"display the text and images."
msgstr ""

#: modules/components/general-user-interactions.php:315
#: modules/components/general-user-interactions.php:319
msgid "Disable Drag / Drop"
msgstr ""

#: modules/components/general-user-interactions.php:316
msgid "Disable the browser drag and drop for images on your pages."
msgstr ""

#: modules/components/general-user-interactions.php:320
msgid ""
"The Drag and Drop operation describes the action o selecting an object or text "
"on the page and moving it to a different area."
msgstr ""

#: modules/components/general-wpemoji.php:54
#: modules/components/general-wpemoji.php:58
msgid "Disable Emoji"
msgstr ""

#: modules/components/general-wpemoji.php:55
msgid "Disable the Emoji icon library from being loaded."
msgstr ""

#: modules/components/general-wpemoji.php:59
msgid ""
"Not everyone use Emoji. Since WordPress load the dependencies as default, it "
"decrease the overall site speed. Disabling this will remove any code and "
"related resources from being loaded on front side."
msgstr ""

#: modules/components/general-wpemoji.php:72
#: modules/components/general-wpemoji.php:76
msgid "Disable TinyMCE Emoji"
msgstr ""

#: modules/components/general-wpemoji.php:73
msgid "Disable the TinyMCE Emoji icons library from being loaded into TinyMC."
msgstr ""

#: modules/components/general-wpemoji.php:77
msgid ""
"Disable TinyMCE Emoji This is also loaded along the WordPress default TinyMCE "
"editor, but it can be disabled through this option."
msgstr ""

#: modules/components/login_2fa.php:151
msgid "Unable to create a login nonce."
msgstr ""

#: modules/components/login_2fa.php:255
msgid ""
"You must also complete the setup for the following options before logging in:"
msgstr ""

#: modules/components/login_2fa.php:283
msgid "Or use other available options:"
msgstr ""

#: modules/components/login_2fa.php:407
msgid "Failed to locate the 2FA Option."
msgstr ""

#: modules/components/login_2fa.php:426
msgid "Failed to create a login nonce."
msgstr ""

#: modules/components/login_2fa.php:493
msgid "Cheatin&#8217; uh?"
msgstr ""

#: modules/components/login_2fa.php:710
msgid "2FA Available Options"
msgstr ""

#: modules/components/login_2fa.php:715 modules/components/login_2fa.php:744
msgid "Primary"
msgstr ""

#: modules/components/login_2fa.php:716 modules/components/login_2fa.php:745
msgid "Option Name"
msgstr ""

#: modules/components/login_2fa_app.php:46 modules/components/login_2fa_app.php:50
msgid "Activate Authenticator app (TOTP)"
msgstr ""

#: modules/components/login_2fa_app.php:47
msgid ""
"Authenticator App (Google Authenticator, Microsoft Authenticator, and Similar "
"Apps)"
msgstr ""

#: modules/components/login_2fa_app.php:51
msgid ""
"Enhance your account security with an Authenticator App that generates time-"
"based one-time passcodes for Two-Factor Authentication (2FA)"
msgstr ""

#: modules/components/login_2fa_app.php:53
msgid ""
"For a secure and reliable method of Two-Factor Authentication (2FA), you can "
"use any of the popular authenticator apps. These apps generate time-based, one-"
"time passcodes (TOTP) that are used to verify your identity. To set up this "
"method, the user simply scan the QR code provided, then enter the verification "
"code generated by your authenticator app into the 'Verification Code' field and "
"click 'Verify' to complete the setup process."
msgstr ""

#: modules/components/login_2fa_app.php:55
msgid "Some of the most widely supported authenticator apps include:"
msgstr ""

#: modules/components/login_2fa_app.php:57
msgid "Google Authenticator"
msgstr ""

#: modules/components/login_2fa_app.php:58
msgid "Microsoft Authenticator"
msgstr ""

#: modules/components/login_2fa_app.php:59
msgid "FreeOTP"
msgstr ""

#: modules/components/login_2fa_app.php:60
msgid "Duo Mobile"
msgstr ""

#: modules/components/login_2fa_app.php:61
msgid "Authy"
msgstr ""

#: modules/components/login_2fa_app.php:62
msgid "LastPass Authenticator"
msgstr ""

#: modules/components/login_2fa_app.php:63
msgid ""
"These apps are available for download on both Android and iOS devices, ensuring "
"users can securely authenticate their logins from their smartphones. "
msgstr ""

#: modules/components/login_2fa_app.php:64
#: modules/components/login_2fa_email.php:56
#: modules/components/login_2fa_recovery_codes.php:56
msgid "Users can manage this option in the Profile section of their account."
msgstr ""

#: modules/components/login_2fa_app.php:99
msgid "Authenticator APP"
msgstr ""

#: modules/components/login_2fa_app.php:104
msgid "Login Code using APP"
msgstr ""

#: modules/components/login_2fa_app.php:123
#: modules/components/login_2fa_app.php:353
msgid "The APP authentication setup is not yet complete."
msgstr ""

#: modules/components/login_2fa_app.php:124
#: modules/components/login_2fa_app.php:354
msgid ""
"Use any of the following authentication applications to scan the QR code above. "
"Then, enter the verification code from the app in the Verification Code field, "
"and click Verify to complete the process."
msgstr ""

#: modules/components/login_2fa_app.php:132
#: modules/components/login_2fa_app.php:154
#: modules/components/login_2fa_app.php:362
#: modules/components/login_2fa_recovery_codes.php:187
msgid "Verification Code:"
msgstr ""

#: modules/components/login_2fa_app.php:135
#: modules/components/login_2fa_app.php:365
#: modules/components/login_2fa_email.php:137
#: modules/components/login_2fa_recovery_codes.php:190
msgid "Verify"
msgstr ""

#: modules/components/login_2fa_app.php:147
msgid "APP security Code"
msgstr ""

#: modules/components/login_2fa_app.php:148
msgid ""
"Open your authentication application, retrieve the verification code, and enter "
"it into the Verification Code field."
msgstr ""

#: modules/components/login_2fa_app.php:149
#: modules/components/login_2fa_recovery_codes.php:182
msgid "Once entered, click Verify to proceed."
msgstr ""

#: modules/components/login_2fa_app.php:157
#: modules/components/login_2fa_template_login_header.php:25
msgid "Log In"
msgstr ""

#: modules/components/login_2fa_app.php:245
#: modules/components/login_2fa_email.php:296
msgid "ERROR: Invalid inpput code."
msgstr ""

#: modules/components/login_2fa_app.php:251
#: modules/components/login_2fa_email.php:301
msgid "ERROR: Invalid user or empty code."
msgstr ""

#: modules/components/login_2fa_app.php:259
#: modules/components/login_2fa_email.php:306
msgid "ERROR: Invalid verification code."
msgstr ""

#: modules/components/login_2fa_app.php:374
msgid ""
"The authenticator app is currently configured. If you reset it, you'll need to "
"re-scan the QR code on all your devices to restore access. Ensure you have the "
"necessary QR code or recovery details ready before proceeding to avoid "
"disruptions to your account security or accessibility."
msgstr ""

#: modules/components/login_2fa_app.php:375
msgid "Reset Authentication APP"
msgstr ""

#: modules/components/login_2fa_app.php:438
#: modules/components/login_2fa_recovery_codes.php:316
msgid "Error: Invalid verification code."
msgstr ""

#: modules/components/login_2fa_defaults.php:96
#: modules/components/login_2fa_defaults.php:100
msgid "Enable 2FA"
msgstr ""

#: modules/components/login_2fa_defaults.php:97
msgid "Enable 2FA for extra account protection."
msgstr ""

#: modules/components/login_2fa_defaults.php:101
msgid ""
"Two-factor authentication (2FA) adds an extra layer of security by requiring "
"two different forms of verification to access your accounts. This means even if "
"someone steals your password, they'll still need a second factor, like a code "
"from your phone, to gain entry."
msgstr ""

#: modules/components/login_2fa_defaults.php:103
msgid ""
"Two-Factor Authentication (2FA) enhances account security by requiring a second "
"authentication method in addition to the primary password. This extra layer of "
"protection helps safeguard accounts from unauthorized access, even if the "
"primary password is compromised. To activate 2FA, users can enable one or more "
"additional authentication methods for enhanced security. Three supported "
"options can be used selectively or combined for maximum protection:"
msgstr ""

#: modules/components/login_2fa_defaults.php:105
msgid ""
"<b>Email Verification Code</b>: A unique code is sent to the user's registered "
"email, required during the login process."
msgstr ""

#: modules/components/login_2fa_defaults.php:106
msgid ""
"<b>Authenticator App</b>: Applications like Google Authenticator or Microsoft "
"Authenticator, available on iOS and Android, generate time-based, one-time "
"passcodes (TOTP) for secure login."
msgstr ""

#: modules/components/login_2fa_defaults.php:107
msgid ""
"<b>Recovery Codes</b>: Pre-generated one-time-use codes provided during the 2FA "
"setup. These can be securely stored and used as a backup when other methods are "
"unavailable."
msgstr ""

#: modules/components/login_2fa_defaults.php:108
msgid ""
"Enabling 2FA significantly reduces the risk of unauthorized access by adding a "
"robust secondary verification step."
msgstr ""

#: modules/components/login_2fa_defaults.php:122
#: modules/components/login_2fa_defaults.php:126
msgid "Enable the 2FA for specific roles"
msgstr ""

#: modules/components/login_2fa_defaults.php:123
msgid "Enable the 2FA functions for the specified roles."
msgstr ""

#: modules/components/login_2fa_defaults.php:127
msgid ""
"This option allows you to enforce Two-Factor Authentication (2FA) for selected "
"user roles within your WordPress site. By enabling this feature, users assigned "
"to the specified roles must authenticate using an additional verification step, "
"enhancing account security. You can define which roles require 2FA, ensuring an "
"extra layer of protection for administrators, editors, or other user groups as "
"needed."
msgstr ""

#: modules/components/login_2fa_defaults.php:135
#: modules/components/login_2fa_defaults.php:139
msgid "Enforce User to Configure 2FA"
msgstr ""

#: modules/components/login_2fa_defaults.php:136
#: modules/components/login_2fa_defaults.php:140
msgid ""
"Mandate the user to configure Two-Factor Authentication (2FA) during their "
"first login."
msgstr ""

#: modules/components/login_2fa_defaults.php:142
msgid ""
"Require users to set up Two-Factor Authentication (2FA) during their initial "
"login for enhanced security. Until the setup is completed, access to the "
"dashboard will be restricted.  Users can configure the active 2FA methods, such "
"as email verification codes, authenticator apps, or recovery codes. Once 2FA is "
"successfully enabled, the user can access the dashboard and manage their "
"account securely. "
msgstr ""

#: modules/components/login_2fa_defaults.php:143
msgid ""
"If needed, users can update or modify their 2FA settings anytime from their "
"account settings within the dashboard."
msgstr ""

#: modules/components/login_2fa_defaults.php:144
msgid ""
"Activating this option ensures straightforward stronger protection against "
"unauthorized access by requiring users to establish an additional verification "
"layer before accessing their account. This proactive approach enhances security "
"and minimizes risks associated with compromised passwords."
msgstr ""

#: modules/components/login_2fa_defaults.php:158
#: modules/components/login_2fa_defaults.php:162
msgid "Primary Two-Factor option"
msgstr ""

#: modules/components/login_2fa_defaults.php:159
msgid "Primary Two-Factor Authentication Method."
msgstr ""

#: modules/components/login_2fa_defaults.php:163
msgid ""
"Select the Primary Two-Factor Authentication Method, which will be presented to "
"the user when they reach the 2FA step during login. This method will be the "
"first authentication option, the user can also pick others."
msgstr ""

#: modules/components/login_2fa_defaults.php:165
msgid "The available 2FA methods include:"
msgstr ""

#: modules/components/login_2fa_defaults.php:167
msgid ""
"<b>Email Verification</b>: A unique code is sent to the user's registered email "
"address, which must be entered during login for authentication."
msgstr ""

#: modules/components/login_2fa_defaults.php:168
msgid ""
"<b>Authenticator App</b>: Use apps like Google Authenticator or Microsoft "
"Authenticator to generate time-based one-time passcodes (TOTP) that the user "
"will need to enter during login."
msgstr ""

#: modules/components/login_2fa_defaults.php:169
msgid ""
"<b>Recovery Codes</b>: Pre-generated one-time-use codes provided during 2FA "
"setup, which can be used as a backup if other methods are unavailable or "
"inaccessible."
msgstr ""

#: modules/components/login_2fa_defaults.php:170
msgid ""
"You can choose the most convenient or secure method for your users, ensuring an "
"additional layer of protection for their accounts."
msgstr ""

#: modules/components/login_2fa_defaults.php:176
#: modules/components/login_2fa_email.php:79
msgid "Email"
msgstr ""

#: modules/components/login_2fa_defaults.php:177
msgid "Auth APP"
msgstr ""

#: modules/components/login_2fa_defaults.php:178
#: modules/components/login_2fa_recovery_codes.php:91
msgid "Recovery Codes"
msgstr ""

#: modules/components/login_2fa_defaults.php:185
#: modules/components/login_2fa_defaults.php:189
msgid "Disable 2FA when using Temporary Login"
msgstr ""

#: modules/components/login_2fa_defaults.php:186
msgid ""
"Disable 2FA when using wordpress plugins like Temporary Login Without Password."
msgstr ""

#: modules/components/login_2fa_defaults.php:190
msgid ""
"When enabled, this option bypasses Two-Factor Authentication (2FA) for users "
"accessing the site via a temporary login URL, such as those generated by the "
"Temporary Login Without Password plugin. This ensures seamless access without "
"additional authentication steps."
msgstr ""

#: modules/components/login_2fa_defaults.php:192
msgid ""
"The new 'Disable 2FA when using Temporary Login' option in the WP Hide plugin "
"enhances site accessibility by allowing temporary bypassing of Two-Factor "
"Authentication (2FA) for specific login scenarios. When activated, if 2FA is "
"enabled, users who access the site via temporary login URLs, generated by "
"plugins such as Temporary Login Without Password, can log in without undergoing "
"the usual 2FA process. This feature simplifies the user experience during "
"temporary access, ensuring a seamless transition while maintaining robust "
"security measures for standard login procedures. It is an ideal solution for "
"administrators who require controlled, temporary access without compromising "
"overall security."
msgstr ""

#: modules/components/login_2fa_email.php:46
#: modules/components/login_2fa_email.php:50
msgid "Activate Email"
msgstr ""

#: modules/components/login_2fa_email.php:47
msgid "Authentication codes will be sent to user e-mail address."
msgstr ""

#: modules/components/login_2fa_email.php:51
msgid ""
"Authentication codes will be sent directly to the user's registered email "
"address as part of the Two-Factor Authentication (2FA) process."
msgstr ""

#: modules/components/login_2fa_email.php:53
msgid ""
"Upon reaching the 2FA step during login, the user will receive a unique, time-"
"sensitive code in their inbox. This code must be entered promptly to verify the "
"user's identity and gain access to their account. The email-based "
"authentication method offers an added layer of security by ensuring that only "
"users with access to the registered email can proceed. It is a reliable method "
"for users who prefer not to rely on third-party applications for authentication."
msgstr ""

#: modules/components/login_2fa_email.php:55
msgid ""
"For the best experience with the Two-Factor Authentication (2FA) - Email "
"option, it is highly recommended to use an SMTP plugin. An SMTP (Simple Mail "
"Transfer Protocol) plugin ensures that authentication messages are sent "
"securely and reliably from your server, helping to avoid issues with email "
"delivery. By configuring an SMTP plugin, you can improve the chances of the 2FA "
"email reaching the user's inbox instead of being mistakenly filtered into the "
"spam or bulk folders. ."
msgstr ""

#: modules/components/login_2fa_email.php:89
msgid "Send a code to your email"
msgstr ""

#: modules/components/login_2fa_email.php:105
#, php-format
msgid "Here is your login confirmation code for %s"
msgstr ""

#: modules/components/login_2fa_email.php:106
#, php-format
msgid ""
"Use the following code to securely log in to your account: %s \n"
"Please ensure you enter this code correctly to access your account. \n"
" \n"
"\n"
"If you did not request this code, please contact support for assistance."
msgstr ""

#: modules/components/login_2fa_email.php:131
msgid "Email security Code"
msgstr ""

#: modules/components/login_2fa_email.php:132
msgid ""
"A verification code has been sent to the email address linked to your account. "
"Please check your inbox and enter the code to proceed."
msgstr ""

#: modules/components/login_2fa_email.php:134
msgid "Authentication Code:"
msgstr ""

#: modules/components/login_2fa_email.php:277
msgid ""
"A new code has been sent. Please check your email inbox, including the spam or "
"junk folder."
msgstr ""

#: modules/components/login_2fa_email.php:309
msgid "ERROR: Expired verification code."
msgstr ""

#: modules/components/login_2fa_email.php:340
#, php-format
msgid ""
"Authentication codes will be securely sent to the email address ( %s ) "
"associated with your account. This added layer of security ensures that only "
"you can access your account, even if your password is compromised. Make sure "
"your email address is up-to-date to receive these important codes promptly."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:46
#: modules/components/login_2fa_recovery_codes.php:50
msgid "Activate Recovery Codes"
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:47
msgid "Recovery Codes."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:51
msgid ""
"Generate 10 one-time-use recovery codes as a backup for Two-Factor "
"Authentication (2FA) to securely access your dashboard."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:53
msgid ""
"The 2FA Recovery Codes method generates 10 unique, one-time-use codes that act "
"as a secure backup for accessing your dashboard. These codes provide an "
"alternative way to authenticate your login if you are unable to use your "
"primary 2FA method, such as an email code or authenticator app. Each code can "
"only be used once, ensuring added security and preventing unauthorized access. "
"It is crucial to store these recovery codes in a safe and secure location, such "
"as an encrypted password manager or physical safe, to avoid loss or misuse."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:55
msgid ""
"While this method is primarily intended as a backup solution, it can also be "
"used as the primary 2FA method if necessary. Recovery codes offer a reliable "
"and easy-to-use fallback, ensuring you can always regain access to your account "
"when needed, even if other 2FA options are unavailable."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:97
msgid "Use a pre-saved recovery code"
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:110
msgid ""
"The setup process generated 10 Recovery Codes, which serve as a secure backup "
"method to access your dashboard. Each code can only be used once."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:122
#: modules/components/login_2fa_recovery_codes.php:453
msgid ""
"Be sure to store these codes in a safe location to prevent loss or unauthorized "
"access."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:165
msgid "The Recovery Code setup is not yet completed."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:166
msgid ""
"The setup process will generate 10 Recovery Codes, which serve as a secure "
"backup method to access your dashboard. Each code can only be used once."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:180
msgid "Recovery Code"
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:181
msgid "Enter a recovery code from the list you saved when setup the option."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:295
msgid "Error: Invalid inpput code."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:300
msgid "Error: Invalid user or empty code."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:304
msgid ""
"Error: This option is unavailable as the internal list is exhausted. Please "
"choose a different option and visit your Profile to generate a new Recovery "
"Codes list. "
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:405
msgid "The Recovery Code setup is not yet complete."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:418
#, php-format
msgid "You have %s recovery codes remaining, each of which can be used once."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:423
msgid "To generate a new list of recovery codes, click the button below."
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:424
msgid "Generate Recovery Codes"
msgstr ""

#: modules/components/login_2fa_recovery_codes.php:453
msgid "After leaving this page, you will no longer be able to view these codes !"
msgstr ""

#: modules/components/login_2fa_template_login_footer.php:74
#: modules/components/login_captcha-google-v2.php:42
msgid "Language"
msgstr ""

#: modules/components/login_2fa_template_login_header.php:56
#, php-format
msgid "%1$s &lsaquo; %2$s &#8212; WordPress"
msgstr ""

#: modules/components/login_2fa_template_login_header.php:60
#, php-format
msgid "Recovery Mode &#8212; %s"
msgstr ""

#: modules/components/login_2fa_template_login_header.php:135
msgid ""
"Usage of the title attribute on the login logo is not recommended for "
"accessibility reasons. Use the link text instead."
msgstr ""

#: modules/components/login_2fa_template_login_header.php:138
msgid "Powered by WordPress"
msgstr ""

#: modules/components/login_captcha-google-v2.php:26
#: modules/components/login_captcha-google-v3.php:26
msgid "Site Key"
msgstr ""

#: modules/components/login_captcha-google-v2.php:30
#: modules/components/login_captcha-google-v3.php:30
msgid "Secret Key"
msgstr ""

#: modules/components/login_captcha-google-v2.php:34
msgid "Theme"
msgstr ""

#: modules/components/login_captcha-google-v2.php:37
msgid "Light"
msgstr ""

#: modules/components/login_captcha-google-v2.php:38
msgid "Dark"
msgstr ""

#: modules/components/login_captcha-google-v2.php:45
msgid "Auto Detect"
msgstr ""

#: modules/components/login_captcha-google-v2.php:46
msgid "Arabic"
msgstr ""

#: modules/components/login_captcha-google-v2.php:47
msgid "German"
msgstr ""

#: modules/components/login_captcha-google-v2.php:48
msgid "English"
msgstr ""

#: modules/components/login_captcha-google-v2.php:49
msgid "Spanish"
msgstr ""

#: modules/components/login_captcha-google-v2.php:50
msgid "Farsi/Persian"
msgstr ""

#: modules/components/login_captcha-google-v2.php:51
msgid "French"
msgstr ""

#: modules/components/login_captcha-google-v2.php:52
msgid "Indonesian"
msgstr ""

#: modules/components/login_captcha-google-v2.php:53
msgid "Italian"
msgstr ""

#: modules/components/login_captcha-google-v2.php:54
msgid "Japanese"
msgstr ""

#: modules/components/login_captcha-google-v2.php:55
msgid "Korean"
msgstr ""

#: modules/components/login_captcha-google-v2.php:56
msgid "Dutch"
msgstr ""

#: modules/components/login_captcha-google-v2.php:57
msgid "Polish"
msgstr ""

#: modules/components/login_captcha-google-v2.php:58
msgid "Portuguese"
msgstr ""

#: modules/components/login_captcha-google-v2.php:59
msgid "Portuguese (Brazil)"
msgstr ""

#: modules/components/login_captcha-google-v2.php:60
msgid "Romania"
msgstr ""

#: modules/components/login_captcha-google-v2.php:61
msgid "Russian"
msgstr ""

#: modules/components/login_captcha-google-v2.php:62
msgid "Turkish"
msgstr ""

#: modules/components/login_captcha-google-v2.php:63
msgid "Ukrainian"
msgstr ""

#: modules/components/login_captcha-google-v2.php:64
msgid "Chinese"
msgstr ""

#: modules/components/login_captcha-google-v2.php:65
msgid "Chinese (Simplified)"
msgstr ""

#: modules/components/login_captcha-google-v2.php:66
msgid "Chinese (Traditional)"
msgstr ""

#: modules/components/login_captcha-google-v2.php:125
#: modules/components/login_captcha-google-v3.php:106
msgid "Test API"
msgstr ""

#: modules/components/login_captcha-google-v2.php:126
#: modules/components/login_captcha-google-v3.php:108
msgid "The captcha will not show on the front side until the Test is successful."
msgstr ""

#: modules/components/login_captcha-google-v2.php:140
msgid "The Google Captcha V2 integration is completed."
msgstr ""

#: modules/components/login_captcha-google-v2.php:158
#: modules/components/login_captcha-google-v3.php:140
msgid "You can get your site key and secret key from"
msgstr ""

#: modules/components/login_captcha-google-v2.php:159
#: modules/components/login_captcha-google-v3.php:141
msgid ""
"After filling in and saving the options, remember to click the <b "
"class=\"important\">Test API</b> button located at the top of this section. The "
"CAPTCHA won't appear on the front end until the test is successfully completed"
msgstr ""

#: modules/components/login_captcha-google-v2.php:183
#: modules/components/login_captcha-google-v3.php:170
msgid "The API returned an error"
msgstr ""

#: modules/components/login_captcha-google-v2.php:274
#: modules/components/login_captcha-google-v2.php:295
#: modules/components/login_captcha-google-v2.php:316
#: modules/components/login_captcha-google-v3.php:288
#: modules/components/login_captcha-google-v3.php:309
#: modules/components/login_captcha-google-v3.php:330
msgid "Unable to verify that you are human."
msgstr ""

#: modules/components/login_captcha-google-v2.php:295
#: modules/components/login_captcha-google-v2.php:316
#: modules/components/login_captcha-google-v3.php:309
#: modules/components/login_captcha-google-v3.php:330
msgid "Error!"
msgstr ""

#: modules/components/login_captcha-google-v3.php:34
msgid "Required Score to validate ( range 0.0 - 1.0 ). Default 0.5 "
msgstr ""

#: modules/components/login_captcha-google-v3.php:107
msgid ""
"If the Test API button is not triggering, check the Google badge message on the "
"bottom-right corner of your screen. The provided site key may be invalid for "
"this domain."
msgstr ""

#: modules/components/login_captcha-google-v3.php:122
msgid "The Google Captcha V3 integration is completed."
msgstr ""

#: modules/components/login_captcha-google-v3.php:142
msgid ""
"reCAPTCHA v3 returns a score for each request without user friction. The score "
"is based on interactions with your site and enables you to take an appropriate "
"action for your site."
msgstr ""

#: modules/components/login_captcha-google-v3.php:143
msgid ""
"The default score is 0.5 which is considered a safe value to distinguish "
"between bots and real users. "
msgstr ""

#: modules/components/login_captcha-google-v3.php:144
msgid "Warning"
msgstr ""

#: modules/components/login_captcha-google-v3.php:145
msgid ""
"Setting an excessively high value may result in being locked out of your site's "
"login. Conversely, using an extremely low value can validate bots. The optimal "
"value is 0.5."
msgstr ""

#: modules/components/login_captcha.php:98
#: modules/components/login_captcha.php:104
msgid "Captcha Type"
msgstr ""

#: modules/components/login_captcha.php:100
msgid ""
"Select the required CAPTCHA type to protect the Login, Registration page, "
"Password Forget etc."
msgstr ""

#: modules/components/login_captcha.php:105
msgid ""
"CAPTCHA, short for \"Completely Automated Public Turing test to tell Computers "
"and Humans Apart,\" is a critical cybersecurity tool. It distinguishes human "
"users from automated bots by presenting challenges like distorted characters or "
"image recognition tasks. CAPTCHA safeguards websites, login pages, and online "
"services from unwanted intrusion, spam, and fraud. Its evolution includes "
"advanced variants and innovations like reCAPTCHA, continually enhancing digital "
"security."
msgstr ""

#: modules/components/login_captcha.php:106
msgid ""
"While it's a robust defense, adversaries are adapting, making CAPTCHA's ongoing "
"development crucial in the fight against online threats."
msgstr ""

#: modules/components/login_captcha.php:172
msgid "Disabled"
msgstr ""

#: modules/components/login_captcha.php:173
msgid "Google Captcha V2"
msgstr ""

#: modules/components/login_captcha.php:174
msgid "Google Captcha V3"
msgstr ""

#: modules/components/login_captcha.php:175
msgid "CloudFlare Turnstile <span class=\"wph-pro\">PRO</span>"
msgstr ""

#: modules/components/rewrite-author.php:65
#: modules/components/rewrite-author.php:69
msgid "New Author Path"
msgstr ""

#: modules/components/rewrite-author.php:66
msgid "The default path is set to /author/"
msgstr ""

#: modules/components/rewrite-author.php:70
msgid ""
"An author URL display all posts associated to a particular author. The default "
"URL format is:"
msgstr ""

#: modules/components/rewrite-author.php:72
msgid "By using a value of 'contributor' this become:"
msgstr ""

#: modules/components/rewrite-author.php:81
#: modules/components/rewrite-author.php:85
msgid "Prevent Access to Author Archives"
msgstr ""

#: modules/components/rewrite-author.php:82
msgid "Prevent Access to Author Archives via User IDs"
msgstr ""

#: modules/components/rewrite-author.php:86
msgid "By default, WordPress generates author archive pages using URLs like "
msgstr ""

#: modules/components/rewrite-author.php:88
msgid ""
". This behavior can be exploited by attackers who repeatedly request URLs such "
"as "
msgstr ""

#: modules/components/rewrite-author.php:90
msgid ""
". and so on, until they find valid user IDs—revealing active usernames on your "
"site."
msgstr ""

#: modules/components/rewrite-author.php:91
msgid ""
"To enhance security, it's best to completely disable access to these types of "
"URLs, especially since author archive pages often serve little or no purpose on "
"many sites."
msgstr ""

#: modules/components/rewrite-author.php:92
msgid ""
"Even if your permalink settings are not set to the default (i.e., 'Plain'), "
"WordPress will still redirect ?author=ID URLs to the corresponding author "
"archive page, if it exists. Therefore, additional measures are necessary to "
"block these redirects and prevent username enumeration."
msgstr ""

#: modules/components/rewrite-author.php:106
#: modules/components/rewrite-author.php:110
#: modules/components/rewrite-search.php:71
#: modules/components/rewrite-search.php:75
msgid "Block default"
msgstr ""

#: modules/components/rewrite-author.php:107
msgid "Block default /author/ when using custom one."
msgstr ""

#: modules/components/rewrite-author.php:107
#: modules/components/rewrite-search.php:72
msgid "Apply only if "
msgstr ""

#: modules/components/rewrite-author.php:107
#: modules/components/rewrite-search.php:72
msgid "is not empty."
msgstr ""

#: modules/components/rewrite-author.php:111
msgid ""
"After changing the default author, the old url is still accessible, this "
"provide a way to block it.<br />The functionality apply only if <b>New Author "
"Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-comments.php:55
msgid "The default path is set to wp-comments-post.php"
msgstr ""

#: modules/components/rewrite-comments.php:59
msgid "As default the form data is being sent and processed at:"
msgstr ""

#: modules/components/rewrite-comments.php:61
msgid ""
"This makes it easy to recognise as WordPress form. Boots always search for such "
"file ( wp-comments-post.php ) and automatically submit spam messages."
msgstr ""

#: modules/components/rewrite-comments.php:62
msgid "Though this option a new file slug can replace the default."
msgstr ""

#: modules/components/rewrite-comments.php:71
#: modules/components/rewrite-comments.php:75
msgid "Block wp-comments-post.php"
msgstr ""

#: modules/components/rewrite-comments.php:72
msgid "Block default wp-comments-post.php."
msgstr ""

#: modules/components/rewrite-comments.php:76
msgid ""
"After changing the default wp-comments-post.php, the old url is still "
"accessible, this provide a way to block the old.<br />The functionality apply "
"only if <b>New wp-comments-post.php</b> option is filled in."
msgstr ""

#: modules/components/rewrite-json-rest.php:133
msgid ""
"As default, when calling the REST API base route ( e.g. /wp-json/ ) the service "
"outputs all available namespaces and routes."
msgstr ""

#: modules/components/rewrite-json-rest.php:137
msgid ""
"When calling the site REST API base route ( e.g. /wp-json/ or ?rest_route=/ ) "
"the service outputs all available namespaces and routes for current site. This "
"can be a breach for the system, as outputs important information regarding "
"certain used theme and plugins. "
msgstr ""

#: modules/components/rewrite-json-rest.php:138
msgid ""
"Recommended selection for this option is Yes, to ensure no inside data is being "
"exposed. "
msgstr ""

#: modules/components/rewrite-json-rest.php:151
#: modules/components/rewrite-json-rest.php:155
msgid "Disable JSON REST V1 service"
msgstr ""

#: modules/components/rewrite-json-rest.php:152
#: modules/components/rewrite-json-rest.php:178
msgid "An API service for WordPress which is active by default."
msgstr ""

#: modules/components/rewrite-json-rest.php:156
#: modules/components/rewrite-json-rest.php:182
msgid ""
"The WordPress REST API is an easy-to-use set of HTTP endpoints which allows "
"access a site data in simple JSON format. That including users, posts, "
"taxonomies and more. Retrieving or updating is as simple as sending a HTTP "
"request."
msgstr ""

#: modules/components/rewrite-json-rest.php:157
#: modules/components/rewrite-json-rest.php:183
msgid ""
"A REST API can be consumed everywhere. On mobile applications, on front-end "
"(web apps) or any other devices that have access on the net, practically "
"everything can connect from anywhere to your site and interact though JSON REST "
"API service."
msgstr ""

#: modules/components/rewrite-json-rest.php:158
msgid ""
"V1 was the first development version of API, which currently is deprecated. To "
"disable the usage of it, simply chose Yes."
msgstr ""

#: modules/components/rewrite-json-rest.php:164
msgid ""
"This can break specific functionality. Some plugins might use this API. Once "
"active test it thoroughly.<br />If not working, set to <b>No</b> to revert."
msgstr ""

#: modules/components/rewrite-json-rest.php:177
#: modules/components/rewrite-json-rest.php:181
msgid "Disable JSON REST V2 service"
msgstr ""

#: modules/components/rewrite-json-rest.php:184
msgid ""
"V2 is the current development version of API, which is included into WordPress "
"as default. To disable the usage of it, simply chose Yes."
msgstr ""

#: modules/components/rewrite-json-rest.php:185
msgid ""
"This might be required by specific plugins, including the new WordPress editor "
"Gutenberg, JetPack etc."
msgstr ""

#: modules/components/rewrite-json-rest.php:191
#: modules/components/rewrite-json-rest.php:218
msgid ""
"This can break specific functionality. Some plugins like Gutenberg editor use "
"this API. Once active test it thoroughly.<br />If not working, set to <b>No</b> "
"to revert."
msgstr ""

#: modules/components/rewrite-json-rest.php:204
#: modules/components/rewrite-json-rest.php:208
msgid "Block any JSON REST calls"
msgstr ""

#: modules/components/rewrite-json-rest.php:205
msgid "Any call for JSON REST API service will be blocked."
msgstr ""

#: modules/components/rewrite-json-rest.php:209
msgid "This blocks the JSON REST API service."
msgstr ""

#: modules/components/rewrite-json-rest.php:210
msgid ""
"When selecting the <b>Non logged-in</b> the service is blocked for all non-"
"authenticated users."
msgstr ""

#: modules/components/rewrite-json-rest.php:211
msgid "When selecting the <b>All</b> the service is blocked for everyone."
msgstr ""

#: modules/components/rewrite-json-rest.php:212
msgid ""
"This might be required by specific plugins, including the new WordPress editor "
"Gutenberg, JetPack etc. So if required to block the API, the <b>Non logged-in</"
"b> is the appropriate option to use."
msgstr ""

#: modules/components/rewrite-json-rest.php:224
msgid "Non logged-in"
msgstr ""

#: modules/components/rewrite-json-rest.php:236
msgid "disable_json_rest_wphead_link"
msgstr ""

#: modules/components/rewrite-json-rest.php:237
msgid ""
"As default the API url is being append into the front html head tag. Using this "
"option, it will be replaced."
msgstr ""

#: modules/components/rewrite-json-rest.php:250
msgid "Disable JSON REST WP RSD endpoint from XML-RPC responses"
msgstr ""

#: modules/components/rewrite-json-rest.php:251
msgid "By default a WP RSD endpoint is being append to the XML respose."
msgstr ""

#: modules/components/rewrite-json-rest.php:254
msgid "disable_json_rest_xmlrpc_rsd"
msgstr ""

#: modules/components/rewrite-json-rest.php:255
msgid "Disable any RSD endpoint from a XML-RPC response."
msgstr ""

#: modules/components/rewrite-json-rest.php:268
msgid "Disable Sends a Link header for the REST API"
msgstr ""

#: modules/components/rewrite-json-rest.php:269
msgid "On template_redirect, disable Sends a Link header for the REST API."
msgstr ""

#: modules/components/rewrite-json-rest.php:272
msgid "disable_json_rest_template_redirect"
msgstr ""

#: modules/components/rewrite-json-rest.php:273
msgid "Disable Sends a Link header for the REST API, on template_redirect"
msgstr ""

#: modules/components/rewrite-new_include_path.php:51
#: modules/components/rewrite-new_include_path.php:55
msgid "New Includes Path"
msgstr ""

#: modules/components/rewrite-new_include_path.php:52
msgid "Change default /wp-includes/ path."
msgstr ""

#: modules/components/rewrite-new_include_path.php:56
msgid ""
"By default, a WordPress installation contains a 'wp-includes' folder that "
"stores files and resources utilized by the WordPress core, themes, and plugins. "
"The 'wp-includes' directory serves as a common fingerprint, making it easy for "
"anyone to identify the site as being built on WordPress."
msgstr ""

#: modules/components/rewrite-new_include_path.php:58
msgid "After filling in this option e.g. resources the links will change to this:"
msgstr ""

#: modules/components/rewrite-new_include_path.php:63
msgid "e.g. my_includes"
msgstr ""

#: modules/components/rewrite-new_include_path.php:69
#: modules/components/rewrite-new_include_path.php:73
msgid "Block wp-includes URL"
msgstr ""

#: modules/components/rewrite-new_include_path.php:70
msgid ""
"Block /wp-includes/ files from being accesible through default urls. <br /"
">Apply only if <b>New Includes Path</b> is not empty."
msgstr ""

#: modules/components/rewrite-new_include_path.php:74
msgid ""
"This blocks the default wp-includes urls only for non loged-in users.<br />The "
"functionality apply only if <b>New Includes Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-new_include_path.php:80
msgid ""
"This can break the layout if server not supporting the feature. Ensure `New "
"Includes Path` option works fine before activate this. Once active test it "
"thoroughly.<br />If not working, set to <b>No</b> to revert."
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:90
msgid "The default plugins path is set to"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:94
msgid ""
"Use any alphanumeric symbols for this field which will be used as the new slug "
"for the plugins folder. Presuming the `apps` slug is being used, all plugins "
"urls become to something like this:"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:105
#: modules/components/rewrite-new_plugin_path.php:109
msgid "Block plugins URL"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:106
msgid ""
"Block default /wp-content/plugins/ files from being accesible through default "
"urls."
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:110
msgid ""
"This blocks the default wp-content/plugins/ url.<br />The functionality apply "
"only if <b>New Plugins Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:116
msgid ""
"This can break the layout if server not supporting the feature. Ensure `New "
"Plugins Path` option works fine before activate this. Once active test it "
"thoroughly.<br />If not working, set to <b>No</b> to revert."
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:150
#: modules/components/rewrite-new_plugin_path.php:154
msgid "New Path for"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:150
msgid "plugin"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:151
msgid "This setting if set, overwrites the"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:151
msgid "New Plugin Path"
msgstr ""

#: modules/components/rewrite-new_plugin_path.php:151
msgid "value for this plugin."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:124
msgid "Change theme url, which as default the path is set to"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:128
msgid ""
"This option helps to change the theme url to a custom one. As default all theme "
"assets ( styles, JavaScript etc ) are loaded using the theme url and appear on "
"front side html source like this:"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:130
msgid ""
"When using this option, if filling with `template`, all urls on front side "
"become as follow:"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:135
#: modules/components/rewrite-new_theme_path.php:152
#: modules/components/rewrite-new_theme_path.php:201
#: modules/components/rewrite-new_theme_path.php:218
msgid "Example"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:141
#: modules/components/rewrite-new_theme_path.php:145
#: modules/components/rewrite-new_theme_path.php:207
#: modules/components/rewrite-new_theme_path.php:211
msgid "New Style File Path"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:142
msgid "Change default theme style file style.css, current path is set to"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:146
msgid ""
"This allow to change the default style.css filename to something else e.g. "
"template-style.css. Per this example, on front side the main style link change "
"from /style.css to /template-style.css"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:158
#: modules/components/rewrite-new_theme_path.php:165
#: modules/components/rewrite-new_theme_path.php:224
#: modules/components/rewrite-new_theme_path.php:231
msgid "Remove description header from Style file"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:161
msgid "Strip out all meta data from style file."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:166
#: modules/components/rewrite-new_theme_path.php:232
msgid ""
"Strip out all meta data from style file as Theme Name, Theme URI, Author etc. "
"Those are important informations for hackers to find out possible theme "
"security breaches. A list of headers can e found at"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:166
#: modules/components/rewrite-new_theme_path.php:232
msgid "Theme Headers"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:167
#: modules/components/rewrite-new_theme_path.php:233
msgid ""
"This feature may fail if style file url not available on html ( being "
"concatenated )."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:173
msgid ""
"This can break the layout if server not supporting the feature. Once active "
"test it thoroughly.<br />If not working, set to No to revert."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:182
#: modules/components/rewrite-new_theme_path.php:248
msgid ""
"This functionality use caching! If active, cache clear is recommended on styles "
"updates."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:182
#: modules/components/rewrite-new_theme_path.php:248
msgid "Cache Clear"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:190
msgid "Change child theme url, which as default the path is set to"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:194
msgid ""
"This option helps to change the child theme url to a custom one. As default all "
"theme assets ( styles, JavaScript etc ) are loaded using the theme url and "
"appear on front side html source like this:"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:196
msgid ""
"When using this option, if filling with `template-child`, all urls on front "
"side become as follow:"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:208
msgid "Change default child theme style file style.css, current path is set to"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:212
msgid ""
"This allow to change the default style.css filename to something else e.g. "
"template-style.css. Per this example, on front side the main style link change "
"from /style.css to /child-style.css"
msgstr ""

#: modules/components/rewrite-new_theme_path.php:227
msgid "Strip out all meta data from child theme style file."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:239
msgid ""
"This can break the layout if server not supporting the feature. Ensure all "
"regular options works fine before activate this. Once active test it thoroughly."
"<br />If not working, set to No to revert."
msgstr ""

#: modules/components/rewrite-new_theme_path.php:876
msgid ""
"When changing the Child Theme Path it is recommended to also change the Main "
"Theme Path to avoid relative paths issues within style files and layout break."
msgstr ""

#: modules/components/rewrite-new_upload_path.php:53
#: modules/components/rewrite-new_upload_path.php:57
msgid "New Uploads Path"
msgstr ""

#: modules/components/rewrite-new_upload_path.php:54
msgid "The default uploads path is set to"
msgstr ""

#: modules/components/rewrite-new_upload_path.php:58
msgid ""
"Use any alphanumeric symbols for this field which will be used as the new slug "
"for the uploads folder. Using this option the default media folder can be "
"mapped to another path. Filling with a slug like 'media' the links become like "
"this:"
msgstr ""

#: modules/components/rewrite-new_upload_path.php:63
msgid "e.g. media"
msgstr ""

#: modules/components/rewrite-new_upload_path.php:69
#: modules/components/rewrite-new_upload_path.php:73
msgid "Block default uploads URL"
msgstr ""

#: modules/components/rewrite-new_upload_path.php:70
msgid ""
"Block default /wp-content/uploads/ media folder from being accesible through "
"default urls."
msgstr ""

#: modules/components/rewrite-new_upload_path.php:74
msgid ""
"This blocks the default wp-content/uploads/ url.<br />The functionality apply "
"only if <b>New Plugins Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-new_upload_path.php:80
msgid ""
"This can break the layout if server not supporting the feature. Ensure `New "
"Uploads Path` option works fine before activate this. Once active test it "
"thoroughly.<br />If not working, set to <b>No</b> to revert."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:71
#: modules/components/rewrite-new_xml-rpc-path.php:75
msgid "New XML-RPC Path"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:72
msgid "The default XML-RPC path is set to xmlrpc.php."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:77
msgid "As default the path to XML-RPC file is:"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:79
msgid ""
"Through this option it can be changed to anything else. This ensure the "
"protocol will not be called by anyone who don't know the actual path."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:84
msgid "e.g. my-xml-rpc.php"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:90
#: modules/components/rewrite-new_xml-rpc-path.php:93
msgid "Block default xmlrpc.php"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:91
msgid "Block the default xmlrpc.php XML-RPC service."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:94
msgid ""
"This blocks the default XML-RPC service. The functionality applies if <b>New "
"XML-RPC Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:95
msgid ""
"Keep in mind that some third-party services, like Jetpack, rely on XML-RPC to "
"connect to WordPress sites for features such as monitoring, statistics, and "
"site management."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:100
msgid ""
"This can break specific functionality. Some plugins like Jetpack use this API. "
"Once active, test it thoroughly.<br />If not working, set to <b>No</b> to "
"revert."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:111
#: modules/components/rewrite-new_xml-rpc-path.php:114
msgid "Disable XML-RPC methods requiring authentication"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:112
msgid ""
"Filter XML-RPC methods requiring authentication, such as for publishing "
"purposes, are enabled."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:115
msgid ""
"Activating the option, methods requiring authentication will be blocked through "
"a call."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:116
msgid ""
"Brute force attacks often target the XML-RPC service. Therefore, it's advisable "
"to enable this option unless you are using the service for specific purposes, "
"such as with a remote mobile app."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:128
#: modules/components/rewrite-new_xml-rpc-path.php:131
msgid "Disable XML-RPC service"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:129
msgid ""
"When the XML-RPC service is deactivated, any calls to it result in the server "
"returning a default 404 Not Found error page."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:132
msgid ""
"Before disabling the XML-RPC, ensure the service is not used for any of the "
"following:"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:133
msgid ""
"Mobile Apps: XML-RPC allows users to manage their WordPress sites via mobile "
"apps."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:145
#: modules/components/rewrite-new_xml-rpc-path.php:148
msgid "Remove pingback"
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:146
msgid "Remove pingback link tag from theme."
msgstr ""

#: modules/components/rewrite-new_xml-rpc-path.php:149
msgid ""
"This enables removing pingback functionality, which is used to notify authors "
"of links to their posts."
msgstr ""

#: modules/components/rewrite-root-files.php:115
msgid "Block access to license.txt root file"
msgstr ""

#: modules/components/rewrite-root-files.php:133
msgid "Block access to readme.html root file"
msgstr ""

#: modules/components/rewrite-root-files.php:150
#: modules/components/rewrite-root-files.php:154
msgid "Block wp-activate.php"
msgstr ""

#: modules/components/rewrite-root-files.php:151
msgid "Block access to wp-activate.php file."
msgstr ""

#: modules/components/rewrite-root-files.php:155
msgid ""
"Block access to wp-activate.php file. Through this file new users confirms that "
"the activation key that is received in the email after signs up for a new blog, "
"matches the key for that user."
msgstr ""

#: modules/components/rewrite-root-files.php:156
msgid "If anyone can register on your site, you should keep this no NO."
msgstr ""

#: modules/components/rewrite-root-files.php:173
msgid ""
"Unable to identify site domain IP, blocking wp-cron.php will stop the site "
"internal WordPress cron functionality."
msgstr ""

#: modules/components/rewrite-root-files.php:177
msgid "Site domain rezolved to IP"
msgstr ""

#: modules/components/rewrite-root-files.php:177
msgid ""
"If blocked, all internal calls to cron will continue to run fine. All calls "
"from a different IP are blocked, including direct calls."
msgstr ""

#: modules/components/rewrite-root-files.php:178
msgid ""
"On certain servers, different ip's can be used to call the cron internally. If "
"the Cron service apepars to not trigger anymore, this option should be  "
"disabled."
msgstr ""

#: modules/components/rewrite-root-files.php:182
#: modules/components/rewrite-root-files.php:186
msgid "Block wp-cron.php"
msgstr ""

#: modules/components/rewrite-root-files.php:187
msgid ""
"The file wp-cron.php is the portion of WordPress that handles scheduled events "
"within a WordPress site. If remote cron calls not being used this can be set to "
"Yes.."
msgstr ""

#: modules/components/rewrite-root-files.php:194
msgid ""
"The Cron service is how WordPress handles scheduling time-based tasks in "
"WordPress. If not working correctly, some core features such as checking for "
"updates and publishing scheduled will fail."
msgstr ""

#: modules/components/rewrite-root-files.php:207
#: modules/components/rewrite-root-files.php:211
msgid "Block wp-signup.php"
msgstr ""

#: modules/components/rewrite-root-files.php:208
msgid "Block default wp-signup.php file."
msgstr ""

#: modules/components/rewrite-root-files.php:212
msgid ""
"The wp-signup.php allow for anyone to register to your site. If the "
"registration functionality is turned off, is safe to block the  wp-signup.php."
msgstr ""

#: modules/components/rewrite-root-files.php:225
#: modules/components/rewrite-root-files.php:229
msgid "Block wp-register.php"
msgstr ""

#: modules/components/rewrite-root-files.php:226
msgid "Block default wp-register.php file."
msgstr ""

#: modules/components/rewrite-root-files.php:230
msgid ""
"This is a deprecated file but still present in many WordPress installs.  When "
"called the user is redirected to /register page. Is safe to block the wp-"
"register.php."
msgstr ""

#: modules/components/rewrite-root-files.php:243
#: modules/components/rewrite-root-files.php:247
msgid "Block other wp-*.php files"
msgstr ""

#: modules/components/rewrite-root-files.php:244
msgid "Block other wp-*.php files in the root."
msgstr ""

#: modules/components/rewrite-root-files.php:248
msgid ""
"Block other wp-*.php files. E.g. wp-blog-header.php, wp-config.php, wp-cron."
"php. Those files are used internally, blocking those will not affect any "
"functionality. Other root files (wp-activate.php, wp-login.php, wp-signup.php) "
"are ignored, they can be controlled through own setting."
msgstr ""

#: modules/components/rewrite-search.php:53
#: modules/components/rewrite-search.php:57
msgid "New Search Path"
msgstr ""

#: modules/components/rewrite-search.php:54
msgid "The default path is set to /search/"
msgstr ""

#: modules/components/rewrite-search.php:58
msgid ""
"The /search/ is the default slug used to display the results for the search "
"page. The default URL format is:"
msgstr ""

#: modules/components/rewrite-search.php:60
msgid "By using a value of 'find' this become:"
msgstr ""

#: modules/components/rewrite-search.php:72
msgid "Block default /search/ when using custom one."
msgstr ""

#: modules/components/rewrite-search.php:76
msgid ""
"After changing the default author, the old url is still accessible, this "
"provide a way to block it.<br />The functionality apply only if <b>New Search "
"Path</b> option is filled in."
msgstr ""

#: modules/components/rewrite-slash.php:41 modules/components/rewrite-slash.php:45
msgid "URL's add Slash"
msgstr ""

#: modules/components/rewrite-slash.php:42
msgid "Add an end slash to all links which does not include one."
msgstr ""

#: modules/components/rewrite-slash.php:46
msgid "As default the WordPress url's format include an ending slash. "
msgstr ""

#: modules/components/rewrite-slash.php:47
msgid ""
"There are situations when this slash is not being append. Turning on this "
"option, all links will get a slash if not included as default. Disguise the "
"existence of files and folders, since they will not be slashed as deafault, all "
"receive an ending slashed."
msgstr ""

#: modules/components/rewrite-slash.php:48
msgid "For example the following link:"
msgstr ""

#: modules/components/rewrite-slash.php:50
msgid "will be redirected to:"
msgstr ""

#: modules/components/rewrite-slash.php:52
msgid ""
"On certain servers this can produce a small lag measured in milliseconds, for "
"each url."
msgstr ""

#: modules/components/rewrite-slash.php:53
msgid "If produce endless redirects, turn this option off."
msgstr ""

#: modules/components/rewrite-wp_content_path.php:51
#: modules/components/rewrite-wp_content_path.php:55
msgid "New Content Path"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:52
msgid "Change default /wp-content/"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:52
msgid "Your default wp-content path is set to"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:56
msgid ""
"By default, a WordPress installation includes a 'wp-content' folder that stores "
"files and resources utilized by themes and plugins. The 'wp-content' directory "
"serves as a distinctive fingerprint, making it easy for anyone to identify the "
"site as being built on the WordPress platform."
msgstr ""

#: modules/components/rewrite-wp_content_path.php:58
msgid "After filling in this option e.g. data the links become:"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:63
msgid "e.g. my_content"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:69
#: modules/components/rewrite-wp_content_path.php:73
msgid "Block wp-content URL"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:70
msgid "Block default /wp-content/ path. Your default wp-content path is set to"
msgstr ""

#: modules/components/rewrite-wp_content_path.php:74
msgid ""
"This restricts access to the default wp-content URLs exclusively for non-logged-"
"in users.<br />The functionality apply only if <b>New Content Path</b> option "
"is filled in."
msgstr ""

#: modules/components/rewrite-wp_content_path.php:80
msgid ""
"This can break the layout if server not supporting the feature. Ensure New "
"Content Path options works fine before activate this. Once active test it "
"thoroughly.<br />If not working, set to <b>No</b> to revert."
msgstr ""

#: modules/components/security-add_headers.php:87
msgid "Remove X-Powered-By Header if being set."
msgstr ""

#: modules/components/security-check_headers.php:48
msgid "Allows a server to declare an embedder policy for a given document."
msgstr ""

#: modules/components/security-check_headers.php:54
msgid "Prevents other domains from opening/controlling a window."
msgstr ""

#: modules/components/security-check_headers.php:60
msgid ""
"Prevents other domains from reading the response of the resources to which this "
"header is applied."
msgstr ""

#: modules/components/security-check_headers.php:66
msgid "Controls resources the user agent is allowed to load for a given page."
msgstr ""

#: modules/components/security-check_headers.php:72
msgid ""
"Allows web developers to experiment with policies by monitoring, but not "
"enforcing, their effects. These violation reports consist of JSON documents "
"sent via an HTTP POST request to the specified URI."
msgstr ""

#: modules/components/security-check_headers.php:78
msgid ""
"Provides a mechanism to allow and deny the use of browser features in its own "
"frame, and in iframes that it embeds."
msgstr ""

#: modules/components/security-check_headers.php:84
msgid ""
"A policy that controls how much information is shared through the HTTP referrer "
"header. Helps to protect user privacy."
msgstr ""

#: modules/components/security-check_headers.php:90
msgid "Force communication using HTTPS instead of HTTP."
msgstr ""

#: modules/components/security-check_headers.php:96
msgid ""
"Disables MIME sniffing and forces browser to use the type given in Content-Type."
msgstr ""

#: modules/components/security-check_headers.php:102
msgid ""
"The X-Download-Options HTTP header indicates that the browser (Internet "
"Explorer) should not display the option to \"Open\" a file that has been "
"downloaded from an application, to prevent phishing attacks as the file "
"otherwise would gain access to execute in the context of the application."
msgstr ""

#: modules/components/security-check_headers.php:108
msgid ""
"Indicates whether a browser should be allowed to render a page in a &#60;"
"frame&#62;, &#60;iframe&#62;, &#60;embed&#62; or &#60;object&#62;"
msgstr ""

#: modules/components/security-check_headers.php:114
msgid ""
"Specifies if a cross-domain policy file (crossdomain.xml) is allowed. The file "
"may define a policy to grant clients, such as Adobe's Flash Player (now "
"obsolete), Adobe Acrobat, Microsoft Silverlight (now obsolete), or Apache Flex, "
"permission to handle data across domains that would otherwise be restricted due "
"to the Same-Origin Policy. See the Cross-domain Policy File Specification for "
"more information."
msgstr ""

#: modules/components/security-check_headers.php:120
msgid ""
"Created for browsers equipped with XSS filters, this non-standard header was "
"intended as a way to control the filtering functionality."
msgstr ""

#: modules/components/security-check_headers.php:139
msgid "Check Headers"
msgstr ""

#: modules/components/security-check_headers.php:142
msgid ""
"HTTP Response Headers are a powerful tool to Harden Your Website.<br />Misusing "
"the headers, can easily break the site layout and functionality. Ensure you "
"understand the proper usage for each option before configuring. Once the "
"Headers setup completed, a thorough check for the front side is recommended."
msgstr ""

#: modules/components/security-check_headers.php:145
msgid ""
"Copy the following link to a safe place. You can use it to reset the header "
"options if something goes wrong:"
msgstr ""

#: modules/components/security-check_headers.php:148
msgid ""
"Create a sample setup for Headers. That will overwrite any Headers settings "
"previously created through the plugin options. The sample setup creates a basic "
"Headers implementation that is commonly safe on any site. For better "
"performances, further manual adjustments are necesarelly."
msgstr ""

#: modules/components/security-check_headers.php:148
msgid "Create Sample Setup"
msgstr ""

#: modules/components/security-check_headers.php:150
msgid ""
"The Hypertext Transfer Protocol (HTTP) is based on a client-server "
"architecture, in which the client ( typically a web browser application ) "
"establishes a connection with the server through a destination URL and waits "
"for a response."
msgstr ""

#: modules/components/security-check_headers.php:151
msgid ""
"The HTTP Headers allow the client and the server send additional pieces of "
"information with the HTTP request or response."
msgstr ""

#: modules/components/security-check_headers.php:152
msgid ""
"The HTTP Headers are categorised by their purpose: Authentication, Caching, "
"Client hints, Conditionals, Connection management, Content negotiation, "
"Controls, Cookies, CORS, Downloads, Message body information, Proxies, "
"Redirects, Request context, Response context, Range requests, <b>Security</b>, "
"Server-sent events, Transfer coding, WebSockets, Other"
msgstr ""

#: modules/components/security-check_headers.php:153
msgid "This area provides support for the <b>"
msgstr ""

#: modules/components/security-check_headers.php:153
msgid ""
" type. Those are the ones responsible for the security implementation for any "
"page."
msgstr ""

#: modules/components/security-check_headers.php:180
msgid "The current protection level is"
msgstr ""

#: modules/components/security-check_headers.php:192
msgid "Check Current Headers"
msgstr ""

#: modules/components/security-check_headers.php:215
msgid ""
"<br />Unable to parse the site Headers. The wp_remote_head() returned an "
"invalid Response, check with your host support for more details.  Unable to "
"identify your site Headers."
msgstr ""

#: modules/components/security-check_headers.php:227
msgid ""
"<br />Invalid WP_HTTP_Requests_Response object. The wp_remote_head() returned "
"an invalid Response, check with your host support for more details."
msgstr ""

#: modules/components/security-check_headers.php:236
msgid ""
"<br />Unable to parse the site Headers. The wp_remote_head() returns invalid "
"Response Code, check with your host support for more details."
msgstr ""

#: modules/components/security-check_headers.php:246
msgid ""
"<br />Unable to parse the site Headers. The wp_remote_head() returns a 401 "
"error code, the request could not be authenticated. Does the site use an httpd "
"password?"
msgstr ""

#: modules/components/security-check_headers.php:253
msgid ""
"<br />Unable to parse the site Headers. The wp_remote_head() returns wrong "
"Response Code"
msgstr ""

#: modules/components/security-check_headers.php:253
msgid ", check with your host support for more details."
msgstr ""

#: modules/components/security-check_headers.php:269
msgid "Header"
msgstr ""

#: modules/components/security-check_headers.php:343
msgid "Warning! The following headers could not be found:"
msgstr ""

#: modules/components/security-check_headers.php:344
msgid "Ensure the server mod_headers module is active."
msgstr ""

#: modules/components/security-check_headers.php:351
msgid "Consider adding more security headers:"
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:45
msgid "Cross-Origin-Embedder-Policy (COEP)"
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:48
msgid "Cross-Origin-Embedder-Policy"
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:49
msgid ""
"The HTTP Cross-Origin-Embedder-Policy (COEP) response header prevents a "
"document from loading any cross-origin resources that don't explicitly grant "
"the document permission (using CORP or CORS)."
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:50
#: modules/components/security-header-cross-origin-opener-policy.php:53
#: modules/components/security-header-referrer-policy.php:51
#: modules/components/security-header-x-content-type-options.php:53
#: modules/components/security-header-x-frame-options.php:55
#: modules/components/security-header-x-permitted-cross-domain-policies.php:53
#: modules/components/security-header-x-xss-protection.php:51
msgid "Options:"
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:51
msgid ""
"This is the default value. Allows the document to fetch cross-origin resources "
"without giving explicit permission through the CORS protocol or the Cross-"
"Origin-Resource-Policy header."
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:52
msgid ""
"A document can only load resources from the same origin, or resources "
"explicitly marked as loadable from another origin. If a cross origin resource "
"supports CORS, the crossorigin attribute or the Cross-Origin-Resource-Policy "
"header must be used to load it without being blocked by COEP."
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:91
#: modules/components/security-header-cross-origin-opener-policy.php:95
#: modules/components/security-header-cross-origin-resource-policy.php:92
#: modules/components/security-header-referrer-policy.php:98
#: modules/components/security-header-x-content-type-options.php:91
#: modules/components/security-header-x-download-options.php:90
#: modules/components/security-header-x-frame-options.php:97
#: modules/components/security-header-x-permitted-cross-domain-policies.php:97
#: modules/components/security-header-x-xss-protection.php:96
msgid "Enable Header"
msgstr ""

#: modules/components/security-header-cross-origin-embedder-policy.php:102
#: modules/components/security-header-cross-origin-opener-policy.php:106
#: modules/components/security-header-cross-origin-resource-policy.php:103
#: modules/components/security-header-referrer-policy.php:109
#: modules/components/security-header-x-content-type-options.php:102
#: modules/components/security-header-x-download-options.php:101
#: modules/components/security-header-x-frame-options.php:108
#: modules/components/security-header-x-permitted-cross-domain-policies.php:108
#: modules/components/security-header-x-xss-protection.php:107
msgid "Header Options"
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:46
msgid "Cross-Origin-Opener-Policy (COOP)"
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:49
msgid "Cross-Origin-Opener-Policy"
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:50
msgid ""
"The HTTP Cross-Origin-Opener-Policy (COOP) response header allows you to ensure "
"a top-level document does not share a browsing context group with cross-origin "
"documents."
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:51
msgid ""
"COOP will process-isolate your document and potential attackers can't access "
"your global object if they were to open it in a popup, preventing a set of "
"cross-origin attacks dubbed XS-Leaks."
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:52
msgid ""
"If a cross-origin document with COOP is opened in a new window, the opening "
"document will not have a reference to it, and the window.opener property of the "
"new window will be null. This allows you to have more control over references "
"to a window than rel=noopener, which only affects outgoing navigations."
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:54
msgid ""
"This is the default value. Allows the document to be added to its opener's "
"browsing context group unless the opener itself has a COOP of same-origin or "
"same-origin-allow-popups."
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:55
msgid ""
"Retains references to newly opened windows or tabs that either don't set COOP "
"or that opt out of isolation by setting a COOP of unsafe-none."
msgstr ""

#: modules/components/security-header-cross-origin-opener-policy.php:56
msgid ""
"Isolates the browsing context exclusively to same-origin documents. Cross-"
"origin documents are not loaded in the same browsing context."
msgstr ""

#: modules/components/security-header-cross-origin-resource-policy.php:49
msgid "Cross-Origin-Resource-Policy (CORP)"
msgstr ""

#: modules/components/security-header-cross-origin-resource-policy.php:52
msgid "Cross-Origin-Resource-Policy"
msgstr ""

#: modules/components/security-header-cross-origin-resource-policy.php:53
msgid ""
"The HTTP Content-Security-Policy response header allows web site administrators "
"to control resources the user agent is allowed to load for a given page. With a "
"few exceptions, policies mostly involve specifying server origins and script "
"endpoints. This helps guard against cross-site scripting attacks (Cross-"
"site_scripting). "
msgstr ""

#: modules/components/security-header-referrer-policy.php:46
#: modules/components/security-header-referrer-policy.php:49
msgid "Referrer-Policy"
msgstr ""

#: modules/components/security-header-referrer-policy.php:50
msgid ""
"The Referrer-Policy HTTP header determines the amount of referral information "
"(sent through the Referer header) that should accompany requests. In addition "
"to the HTTP header, this policy can also be set in HTML"
msgstr ""

#: modules/components/security-header-referrer-policy.php:52
msgid ""
"The Referer header will be omitted: sent requests do not include any referrer "
"information."
msgstr ""

#: modules/components/security-header-referrer-policy.php:53
msgid ""
"Send the origin, path, and querystring in Referer when the protocol security "
"level stays the same or improves (HTTP→HTTP, HTTP→HTTPS, HTTPS→HTTPS). Don't "
"send the Referer header for requests to less secure destinations (HTTPS→HTTP, "
"HTTPS→file)."
msgstr ""

#: modules/components/security-header-referrer-policy.php:54
msgid ""
"Send only the origin in the Referer header. For example, a document at https://"
"example.com/page.html will send the referrer https://example.com/."
msgstr ""

#: modules/components/security-header-referrer-policy.php:55
msgid ""
"When performing a same-origin request to the same protocol level (HTTP→HTTP, "
"HTTPS→HTTPS), send the origin, path, and query string. Send only the origin for "
"cross origin requests and requests to less secure destinations (HTTPS→HTTP)."
msgstr ""

#: modules/components/security-header-referrer-policy.php:56
msgid ""
"Send the origin, path, and query string for same-origin requests. Don't send "
"the Referer header for cross-origin requests."
msgstr ""

#: modules/components/security-header-referrer-policy.php:57
msgid ""
"Send only the origin when the protocol security level stays the same "
"(HTTPS→HTTPS). Don't send the Referer header to less secure destinations "
"(HTTPS→HTTP)."
msgstr ""

#: modules/components/security-header-referrer-policy.php:58
msgid ""
"Send the origin, path, and querystring when performing a same-origin request. "
"For cross-origin requests send the origin (only) when the protocol security "
"level stays same (HTTPS→HTTPS). Don't send the Referer header to less secure "
"destinations (HTTPS→HTTP)."
msgstr ""

#: modules/components/security-header-referrer-policy.php:59
msgid ""
"Send the origin, path, and query string when performing any request, regardless "
"of security."
msgstr ""

#: modules/components/security-header-x-content-type-options.php:46
#: modules/components/security-header-x-content-type-options.php:49
msgid "X-Content-Type-Options"
msgstr ""

#: modules/components/security-header-x-content-type-options.php:50
msgid ""
"The X-Content-Type-Options response HTTP header is a marker used by the server "
"to indicate that the MIME types advertised in the Content-Type headers should "
"be followed and not be changed. The header allows you to avoid MIME type "
"sniffing by saying that the MIME types are deliberately configured."
msgstr ""

#: modules/components/security-header-x-content-type-options.php:51
msgid ""
"This header was introduced by Microsoft in IE 8 as a way for webmasters to "
"block content sniffing that was happening and could transform non-executable "
"MIME types into executable MIME types. Since then, other browsers have "
"introduced it, even if their MIME sniffing algorithms were less aggressive."
msgstr ""

#: modules/components/security-header-x-content-type-options.php:52
msgid ""
"Starting with Firefox 72, top-level documents also avoid MIME sniffing (if "
"Content-type is provided). This can cause HTML web pages to be downloaded "
"instead of being rendered when they are served with a MIME type other than text/"
"html. Make sure to set both headers correctly."
msgstr ""

#: modules/components/security-header-x-content-type-options.php:54
msgid ""
"Blocks a request if the request destination is of type style and the MIME type "
"is not text/css, or of type script and the MIME type is not a JavaScript MIME "
"type."
msgstr ""

#: modules/components/security-header-x-download-options.php:46
#: modules/components/security-header-x-download-options.php:49
msgid "X-Download-Options"
msgstr ""

#: modules/components/security-header-x-download-options.php:50
msgid ""
"The X-Download-Options is specific to IE 8, and is related to how IE 8 handles "
"downloaded HTML files. Turns out if you download an HTML file from a web page "
"and chooses to \"Open\" it in IE, it will execute in the context of the web "
"site. That means that any scripts in that file will also execute with the "
"origin of the web site."
msgstr ""

#: modules/components/security-header-x-frame-options.php:49
msgid "X-Frame-Options (XFO)"
msgstr ""

#: modules/components/security-header-x-frame-options.php:52
msgid "X-Frame-Options"
msgstr ""

#: modules/components/security-header-x-frame-options.php:53
msgid ""
"The X-Frame-Options HTTP response header can be used to indicate whether or not "
"a browser should be allowed to render a page in a &#60;frame&#62;, &#60;"
"iframe&#62;, &#60;embed&#62; or &#60;object&#62;. Sites can use this to avoid "
"click-jacking attacks, by ensuring that their content is not embedded into "
"other sites."
msgstr ""

#: modules/components/security-header-x-frame-options.php:54
msgid ""
"The added security is provided only if the user accessing the document is using "
"a browser that supports X-Frame-Options."
msgstr ""

#: modules/components/security-header-x-frame-options.php:56
msgid ""
"The page cannot be displayed in a frame, regardless of the site attempting to "
"do so."
msgstr ""

#: modules/components/security-header-x-frame-options.php:57
msgid ""
"The page can only be displayed in a frame on the same origin as the page "
"itself. The spec leaves it up to browser vendors to decide whether this option "
"applies to the top level, the parent, or the whole chain, although it is argued "
"that the option is not very useful unless all ancestors are also in the same "
"origin."
msgstr ""

#: modules/components/security-header-x-frame-options.php:58
msgid ""
"If you specify DENY, not only will the browser attempt to load the page in a "
"frame fail when loaded from other sites, attempts to do so will fail when "
"loaded from the same site. On the other hand, if you specify SAMEORIGIN, you "
"can still use the page in a frame as long as the site including it in a frame "
"is the same as the one serving the page."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:46
#: modules/components/security-header-x-permitted-cross-domain-policies.php:49
msgid "X-Permitted-Cross-Domain-Policies"
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:50
msgid ""
"A cross-domain policy file is an XML document that grants a web client, such as "
"Adobe Flash Player or Adobe Acrobat (though not necessarily limited to these), "
"permission to handle data across domains."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:51
msgid ""
"When clients request content hosted on a particular source domain and that "
"content makes requests directed towards a domain other than its own, the remote "
"domain needs to host a cross-domain policy file that grants access to the "
"source domain, allowing the client to continue the transaction."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:52
msgid ""
"Normally a meta-policy is declared in the master policy file, but for those who "
"can’t write to the root directory, they can also declare a meta-policy using "
"the X-Permitted-Cross-Domain-Policies HTTP response header."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:54
msgid ""
"No policy files are allowed anywhere on the target server, including this "
"master policy file."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:55
msgid "Only this master policy file is allowed."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:56
msgid ""
"[HTTP/HTTPS only] Only policy files served with Content-Type: text/x-cross-"
"domain-policy are allowed."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:57
msgid ""
"[FTP only] Only policy files whose file names are crossdomain.xml (i.e. URLs "
"ending in /crossdomain.xml) are allowed."
msgstr ""

#: modules/components/security-header-x-permitted-cross-domain-policies.php:58
msgid "All policy files on this target domain are allowed."
msgstr ""

#: modules/components/security-header-x-xss-protection.php:46
#: modules/components/security-header-x-xss-protection.php:49
msgid "X-XSS-Protection"
msgstr ""

#: modules/components/security-header-x-xss-protection.php:50
msgid ""
"The HTTP X-XSS-Protection response header is a feature of Internet Explorer, "
"Chrome and Safari that stops pages from loading when they detect reflected "
"cross-site scripting (XSS) attacks. These protections are largely unnecessary "
"in modern browsers when sites implement a strong Content-Security-Policy that "
"disables the use of inline JavaScript ('unsafe-inline')."
msgstr ""

#: modules/components/security-header-x-xss-protection.php:52
msgid "Disables XSS filtering."
msgstr ""

#: modules/components/security-header-x-xss-protection.php:53
msgid ""
"Enables XSS filtering (usually default in browsers). If a cross-site scripting "
"attack is detected, the browser will sanitize the page (remove the unsafe "
"parts)."
msgstr ""

#: modules/components/security-header-x-xss-protection.php:54
msgid ""
"Enables XSS filtering. Rather than sanitizing the page, the browser will "
"prevent rendering of the page if an attack is detected."
msgstr ""

#: modules/components/security-header-x-xss-protection.php:55
msgid ""
"Chromium only. Enables XSS filtering. If a cross-site scripting attack is "
"detected, the browser will sanitize the page and report the violation. This "
"uses the functionality of the CSP report-uri directive to send a report."
msgstr ""

#: modules/module-2fa.php:54
msgid "<span class=\"wph-info\">Security&rarr;</span> 2FA"
msgstr ""

#: modules/module-2fa.php:70
msgid "WP Hide & Security Enhancer - Login 2FA"
msgstr ""

#: modules/module-admin.php:44
msgid "<span class=\"wph-info\">Hide&rarr;</span> Login / Admin"
msgstr ""

#: modules/module-admin.php:60
msgid "WP Hide & Security Enhancer - Admin"
msgstr ""

#: modules/module-captcha.php:43
msgid "<span class=\"wph-info\">Security&rarr;</span> Captcha"
msgstr ""

#: modules/module-captcha.php:59
msgid "WP Hide & Security Enhancer - Login"
msgstr ""

#: modules/module-cdn.php:43
msgid "<span class=\"wph-info\">Settings&rarr;</span> CDN"
msgstr ""

#: modules/module-cdn.php:59
msgid "WP Hide & Security Enhancer - CDN"
msgstr ""

#: modules/module-general.php:81
msgid "<span class=\"wph-info\">Hide&rarr;</span> General / Html"
msgstr ""

#: modules/module-general.php:97
msgid "WP Hide & Security Enhancer - General / Html"
msgstr ""

#: modules/module-rewrite.php:78
msgid "<span class=\"wph-info\">Hide&rarr;</span> Rewrite / URLs"
msgstr ""

#: modules/module-rewrite.php:94
msgid "WP Hide & Security Enhancer"
msgstr ""

#: modules/module-rewrite.php:94
msgid "Rewrites"
msgstr ""

#: modules/module-security_headers.php:69
msgid "<span class=\"wph-info\">Security&rarr;</span> Headers"
msgstr ""

#: modules/module-security_headers.php:86
msgid "WP Hide & Security Enhancer - Security Headers"
msgstr ""
