New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Smart, efficient cache solution for WordPress. Use DB, HDD, Redis or Memcached for storing your blog pages. Make WordPress faster! | You have to log in to add a translation. | Details |
Original untranslated
Smart, efficient cache solution for WordPress. Use DB, HDD, Redis or Memcached for storing your blog pages. Make WordPress faster!
You have to log in to edit this translation. |
|||
| ↑ | Cachify | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Redis (optional, via the phpredis module) | You have to log in to add a translation. | Details | |
Original untranslated
Redis (optional, via the phpredis module)
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| A complete documentation is available in the <a href="https://cachify.pluginkollektiv.org/documentation/">online handbook</a>. | You have to log in to add a translation. | Details | |
Original untranslated
A complete documentation is available in the <a href="https://cachify.pluginkollektiv.org/documentation/">online handbook</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| To ensure that Google and other search engines do not index the static contents of the cache folder (otherwise there could be duplicate content), the robots.txt file which is located in the main directory of a WordPress installation should be expanded by disabling the path to the cache file (disallow). This issue should only happen if you use a <em>static robots.txt</em> or you changed the <em>wp-content</em> location. And so might look a robots.txt: | You have to log in to add a translation. | Details | |
Original untranslated
To ensure that Google and other search engines do not index the static contents of the cache folder (otherwise there could be duplicate content), the robots.txt file which is located in the main directory of a WordPress installation should be expanded by disabling the path to the cache file (disallow). This issue should only happen if you use a <em>static robots.txt</em> or you changed the <em>wp-content</em> location. And so might look a robots.txt:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Currently the caching plugin for WordPress has no connection to a CDN provider. Although the Buzzword CDN (Content Delivery Network) is praised as a performance factor, CDN makes little sense for WordPress websites with a national audience. In this case, a home host could provide the requested files faster than a worldwide CDN service provider because the next node could be far away. | You have to log in to add a translation. | Details | |
Original untranslated
Currently the caching plugin for WordPress has no connection to a CDN provider. Although the Buzzword CDN (Content Delivery Network) is praised as a performance factor, CDN makes little sense for WordPress websites with a national audience. In this case, a home host could provide the requested files faster than a worldwide CDN service provider because the next node could be far away.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you use Cachify to store the cache on HDD there is no PHP to run. In the case of misconfigured servers, this can lead to incorrect display of the special characters on web pages. The error can be corrected by an extension of the system file .htaccess: <em>AddDefaultCharset UTF-8</em> | You have to log in to add a translation. | Details | |
Original untranslated
If you use Cachify to store the cache on HDD there is no PHP to run. In the case of misconfigured servers, this can lead to incorrect display of the special characters on web pages. The error can be corrected by an extension of the system file .htaccess: <em>AddDefaultCharset UTF-8</em>
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Please make sure there is no issue that caused by the Cache minify feature. Just deactivate it or use HTML only. If the issue still exist please feel free to report it at the <a href="https://wordpress.org/support/plugin/cachify/">support forums</a>. With this feature any unnecessary characters such as breaks and HTML comments are removed from the source code. | You have to log in to add a translation. | Details | |
Original untranslated
Please make sure there is no issue that caused by the Cache minify feature. Just deactivate it or use HTML only. If the issue still exist please feel free to report it at the <a href="https://wordpress.org/support/plugin/cachify/">support forums</a>. With this feature any unnecessary characters such as breaks and HTML comments are removed from the source code.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| This error message may occur after commissioning the caching plugin. The hint appears because there are no cache files on the HDD for output. This is probably due to the fact that Cachify could not store files in the cache folder. Please check the write-permissions for the cache folder (found in the WordPress directory <em>wp-content</em>) and set them if necessary. | You have to log in to add a translation. | Details | |
Original untranslated
This error message may occur after commissioning the caching plugin. The hint appears because there are no cache files on the HDD for output. This is probably due to the fact that Cachify could not store files in the cache folder. Please check the write-permissions for the cache folder (found in the WordPress directory <em>wp-content</em>) and set them if necessary.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The cache expiration can not be considered due to technical reasons. If the cache stock has to be emptied at certain time intervals, then it is recommended to call a prepared PHP file by a cronjob. | You have to log in to add a translation. | Details | |
Original untranslated
The cache expiration can not be considered due to technical reasons. If the cache stock has to be emptied at certain time intervals, then it is recommended to call a prepared PHP file by a cronjob.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Error pages | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Search | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Mobile-themes (WP-Touch, Carrington, Jetpack Mobile) | You have to log in to add a translation. | Details | |
Original untranslated
Mobile-themes (WP-Touch, Carrington, Jetpack Mobile)
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Previews | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Robots | You have to log in to add a translation. | Details | |
Original untranslated |
|||
Export as
Comment
Short description.