New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Permalinks (URLs) leading to Posts/Pages on your site (based on your WordPress Permalink Settings) | You have to log in to add a translation. | Details | |
Original untranslated
Permalinks (URLs) leading to Posts/Pages on your site (based on your WordPress Permalink Settings)
You have to log in to edit this translation. |
|||
| Or, you can update your configuration manually: [<a href="#" data-toggle-target=". | You have to log in to add a translation. | Details | |
Original untranslated
Or, you can update your configuration manually: [<a href="#" data-toggle-target=".
You have to log in to edit this translation. |
|||
| This includes the following: <code style="white-space:normal; word-wrap:break-word;"> | You have to log in to add a translation. | Details | |
Original untranslated
This includes the following: <code style="white-space:normal; word-wrap:break-word;">
You have to log in to edit this translation. |
|||
| To review your configuration, please see: <a href="%2$s">%1$s → Plugin Options</a>. | You have to log in to add a translation. | Details | |
Original untranslated
To review your configuration, please see: <a href="%2$s">%1$s → Plugin Options</a>.
ReferencesYou have to log in to edit this translation. |
|||
| NOTE: Your ZenCache options were preserved by %1$s (for more details, visit the <a href="%2$s" target="_blank">Migration FAQ</a>). | You have to log in to add a translation. | Details | |
Original untranslated
NOTE: Your ZenCache options were preserved by %1$s (for more details, visit the <a href="%2$s" target="_blank">Migration FAQ</a>).
ReferencesYou have to log in to edit this translation. |
|||
| because the PHP constant `REST_REQUEST` has been set to a boolean-ish `TRUE` value at runtime. REST requests are never cached, as they are often very dynamic in nature. | You have to log in to add a translation. | Details | |
Original untranslated
because the PHP constant `REST_REQUEST` has been set to a boolean-ish `TRUE` value at runtime. REST requests are never cached, as they are often very dynamic in nature.
ReferencesYou have to log in to edit this translation. |
|||
| because the PHP constant `XMLRPC_REQUEST` has been set to a boolean-ish `TRUE` value at runtime. XML-RPC requests are never cached, as they are often very dynamic in nature. | You have to log in to add a translation. | Details | |
Original untranslated
because the PHP constant `XMLRPC_REQUEST` has been set to a boolean-ish `TRUE` value at runtime. XML-RPC requests are never cached, as they are often very dynamic in nature.
ReferencesYou have to log in to edit this translation. |
|||
| <strong>To enforce an exact hostname:</strong> Create or edit the <code>.htaccess</code> file in your WordPress installation directory and add the following lines to the top: | You have to log in to add a translation. | Details | |
Original untranslated
<strong>To enforce an exact hostname:</strong> Create or edit the <code>.htaccess</code> file in your WordPress installation directory and add the following lines to the top:
You have to log in to edit this translation. |
|||
| By enforcing an exact hostname you avoid duplicate cache files, which saves disk space and improves cache performance. For example, if a bot or crawler accesses your site using your server's IP address instead of using your domain name (e.g., <code>http://123.456.789/path</code>), this results in duplicate cache files, because the host was an IP address. The 'host' being an important factor in any cache storage system. The same would be true if a visitor attempted to access your site using a made-up sub-domain; e.g., <code>http://foo.bar.%1$s/path</code>. This sort of thing can be avoided by explicitly enforcing an exact hostname in the request. One that matches exactly what you've configured in <strong>WordPress Settings → General</strong>. | You have to log in to add a translation. | Details | |
Original untranslated
By enforcing an exact hostname you avoid duplicate cache files, which saves disk space and improves cache performance. For example, if a bot or crawler accesses your site using your server's IP address instead of using your domain name (e.g., <code>http://123.456.789/path</code>), this results in duplicate cache files, because the host was an IP address. The 'host' being an important factor in any cache storage system. The same would be true if a visitor attempted to access your site using a made-up sub-domain; e.g., <code>http://foo.bar.%1$s/path</code>. This sort of thing can be avoided by explicitly enforcing an exact hostname in the request. One that matches exactly what you've configured in <strong>WordPress Settings → General</strong>.
You have to log in to edit this translation. |
|||
| No, don't clear any associated Date archive views. | You have to log in to add a translation. | Details | |
Original untranslated
No, don't clear any associated Date archive views.
ReferencesYou have to log in to edit this translation. |
|||
| Yes, but only clear the associated Day archive view. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, but only clear the associated Day archive view.
ReferencesYou have to log in to edit this translation. |
|||
| Yes, but only clear the associated Day and Month archive views. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, but only clear the associated Day and Month archive views.
ReferencesYou have to log in to edit this translation. |
|||
| Yes, if any single Post is cleared/reset, also clear the associated Date archive views. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, if any single Post is cleared/reset, also clear the associated Date archive views.
ReferencesYou have to log in to edit this translation. |
|||
| Date-Based Archives allow visitors to browse Posts by the year, month, or day they were originally published. If a single Post (of any type) is changed in some way; and %1$s clears/resets the cache for that Post, would you like %1$s to also clear any existing cache files for Dated-Based Archives that match the publication time? | You have to log in to add a translation. | Details | |
Original untranslated
Date-Based Archives allow visitors to browse Posts by the year, month, or day they were originally published. If a single Post (of any type) is changed in some way; and %1$s clears/resets the cache for that Post, would you like %1$s to also clear any existing cache files for Dated-Based Archives that match the publication time?
ReferencesYou have to log in to edit this translation. |
|||
| Auto-Clear "Date-Based Archives" Too? | You have to log in to add a translation. | Details | |
Original untranslated |
|||
Export as