New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | A very fast caching engine for WordPress that produces static html files. | موتور سریع کش برای وردپرس که از پرونده های ثابت html تهیه شده است. | Details |
Original current
A very fast caching engine for WordPress that produces static html files.
You have to log in to edit this translation. Meta |
|||
| ↑ | WP Super Cache | افزونه WP Super Cache | Details |
Original currentMeta |
|||
| WordPress should redirect to the canonical URL of your site but if it doesn't, add this to your .htaccess above the Supercache and WordPress rules. Change example.com to your own hostname.↵ RewriteCond %{HTTP_HOST} www.example.com$ [NC]↵ RewriteRule ^(.*)$ https://example.com/$1 [L,R=301] | WordPress should redirect to the canonical URL of your site but if it doesn't, add this to your .htaccess above the Supercache and WordPress rules. Change example.com to your own hostname. RewriteCond %{HTTP_HOST} www.example.com$ [NC] RewriteRule ^(.*)$ https://example.com/$1 [L,R=301] | Details | |
Original current
WordPress should redirect to the canonical URL of your site but if it doesn't, add this to your .htaccess above the Supercache and WordPress rules. Change example.com to your own hostname.↵
RewriteCond %{HTTP_HOST} www.example.com$ [NC]↵
RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Development | توسعه | Details | |
Original currentMeta |
|||
| WP-Cache vs Supercache files | WP-Cache یا فایل های Supercache | Details | |
Original current
WP-Cache vs Supercache files
CommentFound in faq header. You have to log in to edit this translation. Meta |
|||
| How do I disable Supercaching? | چگونه Supercaching را غیرفعال کنم؟ | Details | |
Original current
How do I disable Supercaching?
CommentFound in faq header. You have to log in to edit this translation. Meta |
|||
| Simple caching. | ذخیره‌سازی ساده | Details | |
Original current
Simple caching.
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| The static html files will be served to the vast majority of your users: | فایل های HTML ایستا به اکثریت قریب به اتفاق کاربران شما خدمت می کنند: | Details | |
Original current
The static html files will be served to the vast majority of your users:
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| Preloading | پیش بارگیری | Details | |
Original currentMeta |
|||
| Garbage Collection | مجموعه زباله | Details | |
Original current
Garbage Collection
CommentFound in description header. You have to log in to edit this translation. Meta |
|||
| If that doesn't work, add this line to your wp-config.php: | اگر این کار نمی کند، این خط کد را به wp-config.php اضافه کنید: | Details | |
Original current
If that doesn't work, add this line to your wp-config.php:
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
| If your server is running into trouble because of the number of semaphores used by the plugin it's because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it. | If your server is running into trouble because of the number of semaphores used by the plugin it's because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it. | Details | |
Original current
If your server is running into trouble because of the number of semaphores used by the plugin it's because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.
CommentFound in description list item. You have to log in to edit this translation. Meta |
|||
| Go to Settings -> WP Super Cache and look for the "Cache Tester" form on the easy settings page. Click "Test Cache" and the plugin will request the front page of the site twice, comparing a timestamp on each to make sure they match. | Go to Settings -> WP Super Cache and look for the "Cache Tester" form on the easy settings page. Click "Test Cache" and the plugin will request the front page of the site twice, comparing a timestamp on each to make sure they match. | Details | |
Original current
Go to Settings -> WP Super Cache and look for the "Cache Tester" form on the easy settings page. Click "Test Cache" and the plugin will request the front page of the site twice, comparing a timestamp on each to make sure they match.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching. | Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching. | Details | |
Original current
Install like any other plugin, directly from your plugins page but make sure you have custom permalinks enabled. Go to the plugin settings page at Settings->WP Super Cache and enable caching.
CommentFound in installation paragraph. You have to log in to edit this translation. Meta |
|||
| There is one regular WordPress filter too. Use the "do_createsupercache" filter↵ to customize the checks made before caching. The filter accepts one parameter.↵ The output of WP-Cache's wp_cache_get_cookies_values() function. | There is one regular WordPress filter too. Use the "do_createsupercache" filter to customize the checks made before caching. The filter accepts one parameter. The output of WP-Cache's wp_cache_get_cookies_values() function. | Details | |
Original current
There is one regular WordPress filter too. Use the "do_createsupercache" filter↵
to customize the checks made before caching. The filter accepts one parameter.↵
The output of WP-Cache's wp_cache_get_cookies_values() function.
CommentFound in description paragraph. You have to log in to edit this translation. Meta |
|||
Export as
Comment
Short description.