New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Provides SQLite cache storage that applied before WordPress core load.↵ Doesn't create multiple html files but stores all pages in one file. | You have to log in to add a translation. | Details |
Original untranslated
Provides SQLite cache storage that applied before WordPress core load.↵
Doesn't create multiple html files but stores all pages in one file.
You have to log in to edit this translation. |
|||
| ↑ | SQLite Cache | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Yes, but for subdomains mode only (blogname.example.com), not for↵ example.com/blogname. A superadmin of a multisite network has access to↵ the first setting form (cache location), blog admins have access to the↵ second form and purge form. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, but for subdomains mode only (blogname.example.com), not for↵
example.com/blogname. A superadmin of a multisite network has access to↵
the first setting form (cache location), blog admins have access to the↵
second form and purge form.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| The presence of <code>www.</code> prefix is defined in <code>Settings</code> - <code>General</code>.↵ The plugin stores <code>with_www</code> parameter in <code>domains/yourdomain.ini</code> file in the↵ cache directory and redirects requests correspondingly; these redirects are↵ being processed before cache usage. | You have to log in to add a translation. | Details | |
Original untranslated
The presence of <code>www.</code> prefix is defined in <code>Settings</code> - <code>General</code>.↵
The plugin stores <code>with_www</code> parameter in <code>domains/yourdomain.ini</code> file in the↵
cache directory and redirects requests correspondingly; these redirects are↵
being processed before cache usage.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| To get the plugin working you need to define the SQLite storage location in↵ the <code>index.php</code> of the wordpress installation directory (note, not in wp-config.php↵ but index.php). Besides of the SQLite file, this directory contains general↵ settings file (compression setting) and a subfolder for per domain settings.↵ In the admin area (plugin setting page) and to remember after deactivation where↵ the cache located, <code>litecache_path</code> WordPress option is used. | You have to log in to add a translation. | Details | |
Original untranslated
To get the plugin working you need to define the SQLite storage location in↵
the <code>index.php</code> of the wordpress installation directory (note, not in wp-config.php↵
but index.php). Besides of the SQLite file, this directory contains general↵
settings file (compression setting) and a subfolder for per domain settings.↵
In the admin area (plugin setting page) and to remember after deactivation where↵
the cache located, <code>litecache_path</code> WordPress option is used.
CommentFound in remaining content paragraph. You have to log in to edit this translation. |
|||
| Is it WordPress Multisite compatible? | You have to log in to add a translation. | Details | |
Original untranslated
Is it WordPress Multisite compatible?
CommentFound in remaining content header. You have to log in to edit this translation. |
|||
| How the plugin handles URLs with and without `www.` prefix? | You have to log in to add a translation. | Details | |
Original untranslated
How the plugin handles URLs with and without `www.` prefix?
CommentFound in remaining content header. You have to log in to edit this translation. |
|||
| As the cache script doesn't load the WordPress core where does it save it's settings? | You have to log in to add a translation. | Details | |
Original untranslated
As the cache script doesn't load the WordPress core where does it save it's settings?
CommentFound in remaining content header. You have to log in to edit this translation. |
|||
| Other notes | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Click on Deactivate link on the plugins list, then the settings file↵ (yourdomain.ini) will be deleted so cache engine will not be applied for↵ the current domain. However it stays working for other sites installed↵ in the same directory until it is included in the <code>index.php</code> and their↵ setting files exist. | You have to log in to add a translation. | Details | |
Original untranslated
Click on Deactivate link on the plugins list, then the settings file↵
(yourdomain.ini) will be deleted so cache engine will not be applied for↵
the current domain. However it stays working for other sites installed↵
in the same directory until it is included in the <code>index.php</code> and their↵
setting files exist.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The plugin caches <code>404 Not Found</code> HTTP status code with the same↵ expiration period as other pages as well as redirect codes 301 and 302↵ with Location header. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin caches <code>404 Not Found</code> HTTP status code with the same↵
expiration period as other pages as well as redirect codes 301 and 302↵
with Location header.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, it works by itself but additional functionalities such as CAPTHCHAs↵ might be not working. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, it works by itself but additional functionalities such as CAPTHCHAs↵
might be not working.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, you can define a list of URL patterns to exclude them from cache. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, you can define a list of URL patterns to exclude them from cache.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Cache entry of a single post page or page will be cleared automatically after↵ post/page update or publishing a comment. Also, the blog list page cache is↵ cleared on post updates. You need to purge cache after modifying menus, widgets,↵ switching theme, changes of theme options. | You have to log in to add a translation. | Details | |
Original untranslated
Cache entry of a single post page or page will be cleared automatically after↵
post/page update or publishing a comment. Also, the blog list page cache is↵
cleared on post updates. You need to purge cache after modifying menus, widgets,↵
switching theme, changes of theme options.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The result of a page after POST request method will isn't being cached↵ so you will see your comment or a notification about pending comment. Also,↵ see the previous question. | You have to log in to add a translation. | Details | |
Original untranslated
The result of a page after POST request method will isn't being cached↵
so you will see your comment or a notification about pending comment. Also,↵
see the previous question.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.