New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| If you need more information than the following, you can have a look at <a href="https://github.com/Automattic/wp-super-cache/wiki">the wiki</a> or the <a href="https://odd.blog/wp-super-cache-developers/">Developer documentation</a>. | Si vous avez besoin de plus d’informations, vous pouvez consulter <a href="https://github.com/Automattic/wp-super-cache/wiki">le wiki</a> ou la <a href="https://odd.blog/wp-super-cache-developers/">documentation du développeur</a>. | Details | |
Original current
If you need more information than the following, you can have a look at <a href="https://github.com/Automattic/wp-super-cache/wiki">the wiki</a> or the <a href="https://odd.blog/wp-super-cache-developers/">Developer documentation</a>.
You have to log in to edit this translation. |
|||
| WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either: | WP Super Cache a son propre système d’extension. Ce code est chargé lorsque WP Super Cache se charge et peut être utilisé pour modifier la façon dont la mise en cache s’opère. Cela se produit avant que WordPress ne soit chargé. Certaines fonctionnalités peuvent, de ce fait, être indisponibles. Les extensions peuvent se situer à différents endroits où PHP peut les charger. Ajoutez votre propre extension : | Details | |
Original current
WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| I can see that the www version of my site is cached separately. How do I stop that? | Je constate que la version www de mon site est mise en cache séparément. Comment puis-je arrêter cela ? | Details | |
Original current
I can see that the www version of my site is cached separately. How do I stop that?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Development | Développement | Details | |
Original current |
|||
| Documentation | Documentation | Details | |
Original current |
|||
| Active development of this plugin is handled <a href="https://github.com/Automattic/wp-super-cache">on GitHub</a>. | Le développement actif de cette extension est pris en charge sur <a href="https://github.com/Automattic/wp-super-cache">GitHub</a>. | Details | |
Original current
Active development of this plugin is handled <a href="https://github.com/Automattic/wp-super-cache">on GitHub</a>.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Translation of the plugin into different languages is on the <a href="https://translate.wordpress.org/projects/wp-plugins/wp-super-cache">translation page</a>. | La traduction de l’extension dans différentes langues se trouve sur la <a href="https://translate.wordpress.org/projects/wp-plugins/wp-super-cache">page de traduction</a>. | Details | |
Original current
Translation of the plugin into different languages is on the <a href="https://translate.wordpress.org/projects/wp-plugins/wp-super-cache">translation page</a>.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Sometimes a category page is cached as the homepage of the site instead of the static page. I can't <a href="https://wordpress.org/support/topic/237415/page/2?replies=38">replicate the problem</a> but a simple solution is to use the "Simple" mode. You can also enable "Extra homepage checks" on the Advanced Settings page. | Il arrive qu’une page de catégorie soit mise en cache en tant que page d’accueil du site au lieu d’une page statique. Je ne peux pas <a href="https://wordpress.org/support/topic/237415/page/2?replies=38">reproduire le problème</a> mais une solution simple consiste à utiliser le mode « Simple ». Vous pouvez également activer l’option « Vérifications supplémentaires de la page d’accueil » sur la page des réglages avancés. | Details | |
Original current
Sometimes a category page is cached as the homepage of the site instead of the static page. I can't <a href="https://wordpress.org/support/topic/237415/page/2?replies=38">replicate the problem</a> but a simple solution is to use the "Simple" mode. You can also enable "Extra homepage checks" on the Advanced Settings page.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| All cache files are stored in wp-content/cache/supercache/HOSTNAME/ where HOSTNANE is your domain name. The files are stored in directories matching your site's permalink structure. Supercache files are index.html or some variant of that, depending on what type of visitor hit the blog. Other files are named wp-cache-XXXXXXXXXXXXXXXXX.php. Associated meta filesnames start with "meta". Those files contain information about the cached file. These files are generated by the "WPCache caching" engine in the plugin. | Tous les fichiers de cache sont stockés dans wp-content/cache/supercache/HOSTNAME/ où HOSTNANE est votre nom de domaine. Les fichiers sont stockés dans des répertoires correspondant à la structure de permalien de votre site. Les fichiers Supercache sont index.html ou une variante de celui-ci, en fonction du type de visiteur qui a accédé au site. Les autres fichiers sont nommés wp-cache-XXXXXXXXXXXXXXXXX.php. Les noms des fichiers méta associés commencent par « meta ». Ces fichiers contiennent des informations sur le fichier mis en cache. Ces fichiers sont générés par le moteur « WPCache caching » de l’extension. | Details | |
Original current
All cache files are stored in wp-content/cache/supercache/HOSTNAME/ where HOSTNANE is your domain name. The files are stored in directories matching your site's permalink structure. Supercache files are index.html or some variant of that, depending on what type of visitor hit the blog. Other files are named wp-cache-XXXXXXXXXXXXXXXXX.php. Associated meta filesnames start with "meta". Those files contain information about the cached file. These files are generated by the "WPCache caching" engine in the plugin.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you only want to use the WP-Cache engine then edit your wp-config.php or create an mu-plugin that sets the constant 'DISABLE_SUPERCACHE' to 1. | Si vous ne voulez utiliser que le moteur WP-Cache, modifiez votre wp-config.php ou créez une extension indispensable qui fixe la constante « DISABLE_SUPERCACHE » à 1. | Details | |
Original current
If you only want to use the WP-Cache engine then edit your wp-config.php or create an mu-plugin that sets the constant 'DISABLE_SUPERCACHE' to 1.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| How do I disable Supercaching? | Comment désactiver le Supercaching ? | Details | |
Original current
How do I disable Supercaching?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| WP-Cache vs Supercache files | Fichiers WP-Cache vs Supercache | Details | |
Original current
WP-Cache vs Supercache files
CommentFound in faq header. You have to log in to edit this translation. |
|||
| There are now REST API endpoints for accessing the settings of this plugin. You'll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the "rest" directory. | Il y a maintenant des points de terminaison de l’API REST pour accéder aux réglages de cette extension. Vous aurez besoin d’être authentifié en tant qu’utilisateur admin avec la permission de voir la page des réglages pour l’utiliser. Cela n’a pas encore été documenté, mais vous pouvez trouver tout le code de référence dans le répertoire « rest ». | Details | |
Original current
There are now REST API endpoints for accessing the settings of this plugin. You'll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the "rest" directory.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:↵ 1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.↵ 2. Scheduler. Setup how often garbage collection should be done.↵ 3. Notification emails. You can be informed on garbage collection job progress.↵ There's no right or wrong settings for garbage collection. It depends on your own site.↵ If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.↵ If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value. | Votre répertoire de cache se remplit au fil du temps, ce qui occupe de l’espace sur votre serveur. Si l’espace est limité ou facturé en fonction de la capacité, ou si vous craignez que les pages mises en cache de votre site ne deviennent périmées, il faut lancer le ramasse miettes. Il a lieu régulièrement et supprime les anciens fichiers dans le répertoire du cache. Sur la page des réglages avancés, vous pouvez spécifier : 1. Délai d’attente du cache. Durée pendant laquelle les fichiers du cache sont considérés comme frais. Passé ce délai, ils sont périmés et peuvent être supprimés. 2. Planificateur. Définit la fréquence à laquelle le ramasse miettes doit être lancé. 3. Courriels de notification. Vous pouvez être informé de l’avancement de la tâche du ramasse miettes. Il n’y a pas de bons ou de mauvais réglages pour le ramasse miettes. Tout dépend du site. S’il reçoit régulièrement des mises à jour ou des commentaires, réglez le délai d’attente à 1800 secondes et le minuteur à 600 secondes. Si votre site est principalement statique, vous pouvez désactiver le ramassage des ordures en saisissant 0 comme délai d’attente, ou utiliser une valeur de délai d’attente vraiment grande. | Details | |
Original current
Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:↵
1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.↵
2. Scheduler. Setup how often garbage collection should be done.↵
3. Notification emails. You can be informed on garbage collection job progress.↵
There's no right or wrong settings for garbage collection. It depends on your own site.↵
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.↵
If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.↵ To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling "Preload Mode" in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache. | Vous pouvez générer des fichiers en cache pour les articles, les cat��gories et les balises de votre site par préchargement. Le préchargement visite chaque page de votre site et génère une page en cache au fur et à mesure, comme n’importe quel autre visiteur du site. En raison de la nature séquentielle de cette fonction, le préchargement d’un site complet peut prendre du temps s’il y a beaucoup de pages. Pour rendre le préchargement plus efficace, il peut être utile de désactiver le ramasse miettes afin que les anciens fichiers de cache ne soient pas supprimés. Pour ce faire, il suffit d’activer le « mode préchargement » dans les réglages. Sachez toutefois que les pages finiront par être obsolètes, mais que les mises à jour effectuées en soumettant des commentaires ou en modifiant des articles effaceront des parties du cache. | Details | |
Original current
You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.↵
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling "Preload Mode" in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Found in description paragraph.