New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Premium WordPress Security - 100% FREE: Firewall, 2FA, Security Headers, Login and Malware Protection, File Monitor, Security Audit & more | You have to log in to add a translation. | Details |
Original untranslated
Premium WordPress Security - 100% FREE: Firewall, 2FA, Security Headers, Login and Malware Protection, File Monitor, Security Audit & more
You have to log in to edit this translation. |
|||
| ↑ | Vigilant - 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner… | You have to log in to add a translation. | Details |
Original untranslated
Vigilant - 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner…
CommentPlugin name. You have to log in to edit this translation. |
|||
| You can require users to change their passwords after a set number of days (30, 60, 90, etc.). Users are warned before it expires. Once it does, they are taken to their profile to set a new one before they can do anything else. Password history prevents reusing recent passwords. | You have to log in to add a translation. | Details | |
Original untranslated
You can require users to change their passwords after a set number of days (30, 60, 90, etc.). Users are warned before it expires. Once it does, they are taken to their profile to set a new one before they can do anything else. Password history prevents reusing recent passwords.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Nowhere on the server. The configuration backup (wp-config.php, .htaccess and robots.txt) is a ZIP built on the fly and sent to your browser, and Vigilant keeps no copy of those files, because they hold your database password and other secrets. A database backup you download is generated as a temporary ZIP with an unguessable name and removed right after the download. | You have to log in to add a translation. | Details | |
Original untranslated
Nowhere on the server. The configuration backup (wp-config.php, .htaccess and robots.txt) is a ZIP built on the fly and sent to your browser, and Vigilant keeps no copy of those files, because they hold your database password and other secrets. A database backup you download is generated as a temporary ZIP with an unguessable name and removed right after the download.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You can configure automatic scans to run daily or weekly. You can also run manual scans at any time. Email notifications support three levels: every finding, serious findings only (suspicious and extra files, changes in wp-config.php or .htaccess and closed plugins), or disabled. The email goes out when a scan finds something new, so a finding you were already told about is not repeated. | You have to log in to add a translation. | Details | |
Original untranslated
You can configure automatic scans to run daily or weekly. You can also run manual scans at any time. Email notifications support three levels: every finding, serious findings only (suspicious and extra files, changes in wp-config.php or .htaccess and closed plugins), or disabled. The email goes out when a scan finds something new, so a finding you were already told about is not repeated.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Not on a very large one. A scan runs for 60 seconds at most and starts from the beginning each time. With many plugins, a large uploads folder or a large cache, it may not reach every plugin and theme, and it is the same part that is left out on every scan. | You have to log in to add a translation. | Details | |
Original untranslated
Not on a very large one. A scan runs for 60 seconds at most and starts from the beginning each time. With many plugins, a large uploads folder or a large cache, it may not reach every plugin and theme, and it is the same part that is left out on every scan.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Vigilant writes these blocks when you save its settings and after it updates, not in between. If another plugin or a person removes one, save that tab again to write it back. | You have to log in to add a translation. | Details | |
Original untranslated
Vigilant writes these blocks when you save its settings and after it updates, not in between. If another plugin or a person removes one, save that tab again to write it back.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| In wp-config.php, one block between <code>/* BEGIN Vigilante Security Constants */</code> and <code>/* END Vigilante Security Constants */</code>, and the prefix <code>// [VIGILANTE_ORIGINAL]</code> on any line of yours that defined one of the same constants. | You have to log in to add a translation. | Details | |
Original untranslated
In wp-config.php, one block between <code>/* BEGIN Vigilante Security Constants */</code> and <code>/* END Vigilante Security Constants */</code>, and the prefix <code>// [VIGILANTE_ORIGINAL]</code> on any line of yours that defined one of the same constants.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| On Apache and LiteSpeed, two blocks in .htaccess, between the lines <code># BEGIN Vigilante Protection</code> and <code># END Vigilante Protection</code>, and <code># BEGIN Vigilante Security Headers</code> and <code># END Vigilante Security Headers</code>. While Under Attack mode is on there is a third one, <code># BEGIN Vigilante Under Attack</code>. | You have to log in to add a translation. | Details | |
Original untranslated
On Apache and LiteSpeed, two blocks in .htaccess, between the lines <code># BEGIN Vigilante Protection</code> and <code># END Vigilante Protection</code>, and <code># BEGIN Vigilante Security Headers</code> and <code># END Vigilante Security Headers</code>. While Under Attack mode is on there is a third one, <code># BEGIN Vigilante Under Attack</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You get that email once per change, not after every scan. The change stays listed in File Integrity until you approve it. | You have to log in to add a translation. | Details | |
Original untranslated
You get that email once per change, not after every scan. The change stays listed in File Integrity until you approve it.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Open File Integrity, press Review changes and read the lines. If they belong to a plugin you use, press Approve: that records the current content as the reference and does not touch the file. Lines you cannot explain need a closer look, above all the ones that load a file (auto_prepend_file, include) or send requests to a PHP file. | You have to log in to add a translation. | Details | |
Original untranslated
Open File Integrity, press Review changes and read the lines. If they belong to a plugin you use, press Approve: that records the current content as the reference and does not touch the file. Lines you cannot explain need a closer look, above all the ones that load a file (auto_prepend_file, include) or send requests to a PHP file.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Usually not. Cache, security and redirection plugins rewrite their own blocks in those files, often on every update, and Vigilant reports every change it did not make itself. | You have to log in to add a translation. | Details | |
Original untranslated
Usually not. Cache, security and redirection plugins rewrite their own blocks in those files, often on every update, and Vigilant reports every change it did not make itself.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The results name what could not be compared. For those, a clean result means no hidden code was found, not that every file is the original one. A PHP file too large to be searched (over 8 MB) is listed as not searched. | You have to log in to add a translation. | Details | |
Original untranslated
The results name what could not be compared. For those, a clean result means no hidden code was found, not that every file is the original one. A PHP file too large to be searched (over 8 MB) is listed as not searched.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It checks: | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Every event is logged as Info, Warning or Critical. By email you get: | You have to log in to add a translation. | Details | |
Original untranslated
Every event is logged as Info, Warning or Critical. By email you get:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.