New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| You may have the "clear all cached files when new posts are made" option set. Clearing those files can take time plus your visitors will now be visiting uncached pages. Are you using Google Analytics campaign tracking with utm_source in the url? Those pages aren't cached. See the question, "How should I best use the utm_source tracking tools in Google Analytics with this plugin" above for how to use them properly.↵ Cached pages have to be refreshed when posts are made. Perhaps your server just isn't up to the job of serving the amount of traffic you get. Enable the "cache rebuild" feature as that may help. | You may have the "clear all cached files when new posts are made" option set. Clearing those files can take time plus your visitors will now be visiting uncached pages. Are you using Google Analytics campaign tracking with utm_source in the url? Those pages aren't cached. See the question, "How should I best use the utm_source tracking tools in Google Analytics with this plugin" above for how to use them properly. Cached pages have to be refreshed when posts are made. Perhaps your server just isn't up to the job of serving the amount of traffic you get. Enable the "cache rebuild" feature as that may help. | Details | |
Original current
You may have the "clear all cached files when new posts are made" option set. Clearing those files can take time plus your visitors will now be visiting uncached pages. Are you using Google Analytics campaign tracking with utm_source in the url? Those pages aren't cached. See the question, "How should I best use the utm_source tracking tools in Google Analytics with this plugin" above for how to use them properly.↵
Cached pages have to be refreshed when posts are made. Perhaps your server just isn't up to the job of serving the amount of traffic you get. Enable the "cache rebuild" feature as that may help.
You have to log in to edit this translation. Meta |
|||
| "Your blog doesn't support client caching (no 304 response to If-modified-since)."↵ "Your feed doesn't support caching (no 304 response to If-modified-since)" | "Your blog doesn't support client caching (no 304 response to If-modified-since)." "Your feed doesn't support caching (no 304 response to If-modified-since)" | Details | |
Original current
"Your blog doesn't support client caching (no 304 response to If-modified-since)."↵
"Your feed doesn't support caching (no 304 response to If-modified-since)"
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| WP Super Cache 1.4 introduced a cacheaction filter called wpsc_cachedata. The cached page to be displayed goes through this filter and allows modification of the page. If the page contains a placeholder tag the filter can be used to replace that tag with your dynamically generated html.↵ The function that hooks on to the wpsc_cachedata filter should be put in a file in the WP Super Cache plugins folder unless you use the late_init feature. An example plugin is included. Edit <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> to see the example code.↵ There are two example functions there. There's a simple function that replaces a string (or tag) you define when the cached page is served. The other example function uses an output buffer to generate the dynamic content. Due to a limitation in how PHP works the output buffer code MUST run before the wpsc_cachedata filter is hit, at least for when a page is cached. It doesn't matter when serving cached pages. See <a href="https://odd.blog/y/6j">this post</a> for a more technical and longer explanation.↵ To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page. | WP Super Cache 1.4 introduced a cacheaction filter called wpsc_cachedata. The cached page to be displayed goes through this filter and allows modification of the page. If the page contains a placeholder tag the filter can be used to replace that tag with your dynamically generated html. The function that hooks on to the wpsc_cachedata filter should be put in a file in the WP Super Cache plugins folder unless you use the late_init feature. An example plugin is included. Edit <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> to see the example code. There are two example functions there. There's a simple function that replaces a string (or tag) you define when the cached page is served. The other example function uses an output buffer to generate the dynamic content. Due to a limitation in how PHP works the output buffer code MUST run before the wpsc_cachedata filter is hit, at least for when a page is cached. It doesn't matter when serving cached pages. See <a href="https://odd.blog/y/6j">this post</a> for a more technical and longer explanation. To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page. | Details | |
Original current
WP Super Cache 1.4 introduced a cacheaction filter called wpsc_cachedata. The cached page to be displayed goes through this filter and allows modification of the page. If the page contains a placeholder tag the filter can be used to replace that tag with your dynamically generated html.↵
The function that hooks on to the wpsc_cachedata filter should be put in a file in the WP Super Cache plugins folder unless you use the late_init feature. An example plugin is included. Edit <a href="http://svn.wp-plugins.org/wp-super-cache/trunk/plugins/dynamic-cache-test.php">dynamic-cache-test.php</a> to see the example code.↵
There are two example functions there. There's a simple function that replaces a string (or tag) you define when the cached page is served. The other example function uses an output buffer to generate the dynamic content. Due to a limitation in how PHP works the output buffer code MUST run before the wpsc_cachedata filter is hit, at least for when a page is cached. It doesn't matter when serving cached pages. See <a href="https://odd.blog/y/6j">this post</a> for a more technical and longer explanation.↵
To execute WordPress functions you must enable the 'Late init' feature on the advanced settings page.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Supercache doesn't support 304 header checks in Expert mode but does support it in Simple mode. This is caching done by your browser, not the server. It is a check your browser does to ask the server if an updated version of the current page is available. If not, it doesn't download the old version again. The page is still cached by your server, just not by your visitors' browsers.↵ Try the Cacheability Engine at http://www.ircache.net/cgi-bin/cacheability.py or https://redbot.org/ for further analysis. | Supercache doesn't support 304 header checks in Expert mode but does support it in Simple mode. This is caching done by your browser, not the server. It is a check your browser does to ask the server if an updated version of the current page is available. If not, it doesn't download the old version again. The page is still cached by your server, just not by your visitors' browsers. Try the Cacheability Engine at http://www.ircache.net/cgi-bin/cacheability.py or https://redbot.org/ for further analysis. | Details | |
Original current
Supercache doesn't support 304 header checks in Expert mode but does support it in Simple mode. This is caching done by your browser, not the server. It is a check your browser does to ask the server if an updated version of the current page is available. If not, it doesn't download the old version again. The page is still cached by your server, just not by your visitors' browsers.↵
Try the Cacheability Engine at http://www.ircache.net/cgi-bin/cacheability.py or https://redbot.org/ for further analysis.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.↵ Even with preload mode enabled cached files will still be deleted when posts are modified or comments made. | Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files. Even with preload mode enabled cached files will still be deleted when posts are modified or comments made. | Details | |
Original current
Preload as many posts as you can and enable "Preload Mode". Garbage collection of old cached files will be disabled. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.↵
Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| If you want to do it manually, enable debugging in the plugin settings page and load the log file in a new browser tab. Then view your blog while logged in and logged out. You should see activity in the log. View the source of any page on your site. When a page is first created, you'll see the text "Dynamic page generated in XXXX seconds." and "Cached page generated by WP-Super-Cache on YYYY-MM-DD HH:MM:SS" at the end of the source code. On reload, a cached page will show the same timestamp so wait a few seconds before checking.↵ If Supercaching is disabled and you have compression enabled, the text "Compression = gzip" will be added. If compression is disabled and the page is served as a static html file, the text "super cache" will be added. The only other way to check if your cached file was served by PHP script or from the static cache is by looking at the HTTP headers. PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". You should also check your cache directory in wp-content/cache/supercache/hostname/ for static cache files.↵ If the plugin rules are missing from your .htaccess file, the plugin will attempt to serve the super cached page if it's found. The header "WP-Super-Cache: Served supercache file from PHP" if this happens.↵ The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester. | If you want to do it manually, enable debugging in the plugin settings page and load the log file in a new browser tab. Then view your blog while logged in and logged out. You should see activity in the log. View the source of any page on your site. When a page is first created, you'll see the text "Dynamic page generated in XXXX seconds." and "Cached page generated by WP-Super-Cache on YYYY-MM-DD HH:MM:SS" at the end of the source code. On reload, a cached page will show the same timestamp so wait a few seconds before checking. If Supercaching is disabled and you have compression enabled, the text "Compression = gzip" will be added. If compression is disabled and the page is served as a static html file, the text "super cache" will be added. The only other way to check if your cached file was served by PHP script or from the static cache is by looking at the HTTP headers. PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". You should also check your cache directory in wp-content/cache/supercache/hostname/ for static cache files. If the plugin rules are missing from your .htaccess file, the plugin will attempt to serve the super cached page if it's found. The header "WP-Super-Cache: Served supercache file from PHP" if this happens. The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester. | Details | |
Original current
If you want to do it manually, enable debugging in the plugin settings page and load the log file in a new browser tab. Then view your blog while logged in and logged out. You should see activity in the log. View the source of any page on your site. When a page is first created, you'll see the text "Dynamic page generated in XXXX seconds." and "Cached page generated by WP-Super-Cache on YYYY-MM-DD HH:MM:SS" at the end of the source code. On reload, a cached page will show the same timestamp so wait a few seconds before checking.↵
If Supercaching is disabled and you have compression enabled, the text "Compression = gzip" will be added. If compression is disabled and the page is served as a static html file, the text "super cache" will be added. The only other way to check if your cached file was served by PHP script or from the static cache is by looking at the HTTP headers. PHP cached pages will have the header "WP-Super-Cache: Served supercache file from PHP". WPCache cached files will have the header, "WP-Super-Cache: Served WPCache cache file". You should also check your cache directory in wp-content/cache/supercache/hostname/ for static cache files.↵
If the plugin rules are missing from your .htaccess file, the plugin will attempt to serve the super cached page if it's found. The header "WP-Super-Cache: Served supercache file from PHP" if this happens.↵
The pagespeed module for Apache may cause problems when testing. Disable it if you notice any problems running the cache tester.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Three hooks are available: | Three hooks are available: | Details | |
Original current
Three hooks are available:
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| It is now possible to hook into the caching process using the add_cacheaction() function. | It is now possible to hook into the caching process using the add_cacheaction() function. | Details | |
Original current
It is now possible to hook into the caching process using the add_cacheaction() function.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| Configure this on the "CDN" tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN. | Configure this on the "CDN" tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN. | Details | |
Original current
Configure this on the "CDN" tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| To manually uninstall: | برای پاک کردن دستی: | Details | |
Original current
To manually uninstall:
CommentFound in installation paragraph. You have to log in to edit this translation. Meta |
|||
| 'cache_admin_page' - runs in the admin page. Use it to modify that page, perhaps by adding new configuration options. | 'cache_admin_page' - runs in the admin page. Use it to modify that page, perhaps by adding new configuration options. | Details | |
Original current
'cache_admin_page' - runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| 'add_cacheaction' - runs in phase2. Allows a plugin to add WordPress hooks. | 'add_cacheaction' - runs in phase2. Allows a plugin to add WordPress hooks. | Details | |
Original current
'add_cacheaction' - runs in phase2. Allows a plugin to add WordPress hooks.
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| 'wp_cache_get_cookies_values' - modify the key used by WP Cache. | 'wp_cache_get_cookies_values' - modify the key used by WP Cache. | Details | |
Original current
'wp_cache_get_cookies_values' - modify the key used by WP Cache.
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/. | Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/. | Details | |
Original current
Optionally delete advanced-cache.php, wp-cache-config.php and the cache folder in wp-content/.
CommentFound in installation list item. You have to log in to edit this translation. Meta |
|||
| A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a "poor man's CDN" by using a sub domain of your domain to serve static files too. | A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a "poor man's CDN" by using a sub domain of your domain to serve static files too. | Details | |
Original current
A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a "poor man's CDN" by using a sub domain of your domain to serve static files too.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
Export as
Comment
Found in faq paragraph.