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, APC or Memcached for storing your blog pages. Make WordPress faster! | Solución de la caché inteligente y eficiente para WordPress. Usar BB.DD., HDD, APC o Memcached para almacenar las páginas del blog. ¡Hacer que WordPress sea más rápido! | Details |
Original current
Smart, efficient cache solution for WordPress. Use DB, HDD, APC or Memcached for storing your blog pages. Make WordPress faster!
You have to log in to edit this translation. Meta |
|||
| ↑ | Cachify | Cachify | Details |
Original currentMeta |
|||
| 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. Meta |
|||
| 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: | Para asegurar que Google y otros motores de búsqueda no indexen el contenido estático de la carpeta de la caché (de lo contrario, podría haber contenido duplicado), el archivo «robots.txt», que se encuentra en el directorio principal de una instalación de WordPress, debe ampliarse desactivando la ruta al archivo de la caché (disallow). Este problema solo debería ocurrir si usas un archivo <em>«robots.txt» estático</em> o si cambias la ubicación del directorio «<em>wp-content</em>». Y así podría ser el aspecto de «robots.txt»: | Details | |
Original current
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. Meta |
|||
| Compared to APC (Alternative PHP Cache), PHP OPcache is not able to contain content with custom keys and values. Because of this Cachify can not consider the PHP OPcache as a caching method. | En comparación con APC (caché PHP alternativa), PHP OPcache no puede contener contenido con claves y valores personalizados. Debido a esto, Cachify no puede considerar a PHP OPcache como un método de almacenamiento en la caché. | Details | |
Original current
Compared to APC (Alternative PHP Cache), PHP OPcache is not able to contain content with custom keys and values. Because of this Cachify can not consider the PHP OPcache as a caching method.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| 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. | Actualmente, el plugin de almacenamiento en caché para WordPress no tiene conexión con un proveedor de CDN. Aunque Buzzword CDN (Content Delivery Network) se elogia como un factor de rendimiento, CDN tiene poco sentido para las web de WordPress con una audiencia nacional. En este caso, un proveedor doméstico podría proporcionar los archivos solicitados más rápido que un proveedor de servicios CDN en todo el mundo porque el siguiente nodo podría estar muy lejos. | Details | |
Original current
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. Meta |
|||
| 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> | Si usas Cachify para almacenar la caché en el disco duro, no hay PHP para ejecutar. En el caso de servidores mal configurados, esto puede conducir a una visualización incorrecta de los caracteres especiales en las páginas web. El error se puede corregir con una extensión del archivo del sistema «.htaccess»: <em>AddDefaultCharset UTF-8</em> | Details | |
Original current
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. Meta |
|||
| 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. | Por favor, asegúrate de que no haya ningún problema causado por la característica de minimizar la caché. Simplemente desactivarlo o usar solo HTML. Si todavía existe el problema no dudes en reportarlo en los <a href="https://wordpress.org/support/plugin/cachify/">foros de soporte</a>. Con esta característica, los caracteres innecesarios, como saltos y comentarios HTML, se eliminan del código fuente. | Details | |
Original current
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. Meta |
|||
| 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. | Este mensaje de error puede aparecer después de poner en marcha el plugin de almacenamiento en caché. La sugerencia aparece porque no hay archivos de caché en el HDD para la salida. Esto probablemente se debe al hecho de que Cachify no ha podido almacenar archivos en la carpeta de caché. Por favor, comprueba los permisos de escritura para la carpeta de caché (que se encuentra en el directorio de WordPress <em>wp-content</em>) y establécelos si es necesario. | Details | |
Original current
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. Meta |
|||
| 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. | La caducidad de la caché no se puede considerar por razones técnicas. Si las existencias de la caché tienen que ser vaciadas en ciertos intervalos de tiempo, entonces se recomienda llamar a un archivo PHP preparado por una tarea programada. | Details | |
Original current
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. Meta |
|||
| Error pages | Páginas de error | Details | |
Original currentMeta |
|||
| Search | Buscar | Details | |
Original currentMeta |
|||
| Mobile-themes (WP-Touch, Carrington, Jetpack Mobile) | Temas para móviles (WP-Touch, Carrington, Jetpack Mobile) | Details | |
Original current
Mobile-themes (WP-Touch, Carrington, Jetpack Mobile)
CommentFound in faq list item. You have to log in to edit this translation. Meta |
|||
| Previews | Vistas previas | Details | |
Original currentMeta |
|||
| Robots | Robots | Details | |
Original currentMeta |
|||
Export as
Comment
Short description.