| Prio | Original string | Translation | — |
|---|---|---|---|
| Enable this option to log debug info. | Enable this option to log debug info. | Details | |
|
Enable this option to log debug info. Enable this option to log debug info.
You have to log in to edit this translation.
|
|||
| Enable this option to print debug info. | Enable this option to print debug info. | Details | |
|
Enable this option to print debug info. Enable this option to print debug info.
You have to log in to edit this translation.
|
|||
| Enable this option to turn on WordPress debugging. | Enable this option to turn on WordPress debugging. | Details | |
|
Enable this option to turn on WordPress debugging. Enable this option to turn on WordPress debugging.
You have to log in to edit this translation.
|
|||
| By default, WordPress creates a new set of images every time you edit image and restore the original. It leaves all the edits on the server. Enable this option to change this behaviour. | By default, WordPress creates a new set of images every time you edit an image and restore the original. It leaves all the edits on the server. Enable this option to change this behaviour. | Details | |
|
By default, WordPress creates a new set of images every time you edit image and restore the original. It leaves all the edits on the server. Enable this option to change this behaviour. By default, WordPress creates a new set of images every time you edit an image and restore the original. It leaves all the edits on the server. Enable this option to change this behaviour.
You have to log in to edit this translation.
|
|||
| This option will block users being able to use the plugin and theme installation/update functionality from the WordPress admin area. | This option will block users from being able to use the plugin and theme installation/update functionality from the WordPress admin area. | Details | |
|
This option will block users being able to use the plugin and theme installation/update functionality from the WordPress admin area. This option will block users from being able to use the plugin and theme installation/update functionality from the WordPress admin area.
You have to log in to edit this translation.
|
|||
| This option will completely disable the use of plugin and theme editor. If this option enabled, no plugins or theme file can be edited. | This option will completely disable the use of plugin and theme editor. If this option is enabled, no plugins or theme files can be edited. | Details | |
|
This option will completely disable the use of plugin and theme editor. If this option enabled, no plugins or theme file can be edited. This option will completely disable the use of plugin and theme editor. If this option is enabled, no plugins or theme files can be edited.
You have to log in to edit this translation.
|
|||
| This option allows you to change the number of days before WordPress permanently deletes posts, pages, attachments, and comments, from the trash bin. The default is 30 days. There is no confirmation alert when someone clicks on "Delete Permanently" if this option is set to "Disable Trash Bin". | This option allows you to change the number of days before WordPress permanently deletes posts, pages, attachments, and comments from the trash bin. The default is 30 days. There is no confirmation alert when someone clicks on 'Delete Permanently' if this option is set to 'Disable Trash Bin'. | Details | |
|
This option allows you to change the number of days before WordPress permanently deletes posts, pages, attachments, and comments, from the trash bin. The default is 30 days. There is no confirmation alert when someone clicks on "Delete Permanently" if this option is set to "Disable Trash Bin". This option allows you to change the number of days before WordPress permanently deletes posts, pages, attachments, and comments from the trash bin. The default is 30 days. There is no confirmation alert when someone clicks on 'Delete Permanently' if this option is set to 'Disable Trash Bin'.
You have to log in to edit this translation.
|
|||
| Post revision is a copy of each edit made to a post or page, allowing the possibility of reverting to a previous version. However, have a revision too much can create a bad impact on database performance. Changing this behaviour can reduce the usage of server resource. | Post revision is a copy of each edit made to a post or page, allowing the possibility of reverting to a previous version. However, having too many revisions can create a bad impact on database performance. Changing this behaviour can reduce the usage of server resources. | Details | |
|
Post revision is a copy of each edit made to a post or page, allowing the possibility of reverting to a previous version. However, have a revision too much can create a bad impact on database performance. Changing this behaviour can reduce the usage of server resource. Post revision is a copy of each edit made to a post or page, allowing the possibility of reverting to a previous version. However, having too many revisions can create a bad impact on database performance. Changing this behaviour can reduce the usage of server resources.
You have to log in to edit this translation.
|
|||
| WordPress by default automatically saves a draft every 1 minute when editing or create a new post. Changing this behaviour can reduce the usage of server resource. | WordPress by default automatically saves a draft every 1 minute when editing or creating a new post. Changing this behaviour can reduce the usage of server resources. | Details | |
|
WordPress by default automatically saves a draft every 1 minute when editing or create a new post. Changing this behaviour can reduce the usage of server resource. WordPress by default automatically saves a draft every 1 minute when editing or creating a new post. Changing this behaviour can reduce the usage of server resources.
You have to log in to edit this translation.
|
|||
| WordPress by default converts Transients as persistent object caching when available. Enable this option to persist Transients in the Database. | WordPress by default converts Transients as persistent object caching when available. Enable this option to persist Transients in the Database. | Details | |
|
WordPress by default converts Transients as persistent object caching when available. Enable this option to persist Transients in the Database. WordPress by default converts Transients as persistent object caching when available. Enable this option to persist Transients in the Database.
You have to log in to edit this translation.
|
|||
| Limit HTTP requests in WP Admin. | Limit HTTP requests in WP Admin. | Details | |
|
Limit HTTP requests in WP Admin. Limit HTTP requests in WP Admin.
You have to log in to edit this translation.
|
|||
| Enable this option to exclude empty caches from being stored on disk. Only enable it if you have an issue with inode limits. | Enable this option to exclude empty caches from being stored on disk. Only enable it if you have an issue with inode limits. | Details | |
|
Enable this option to exclude empty caches from being stored on disk. Only enable it if you have an issue with inode limits. Enable this option to exclude empty caches from being stored on disk. Only enable it if you have an issue with inode limits.
You have to log in to edit this translation.
|
|||
| Enable this option to exclude stale cache created by WordPress, WooCommerce, and others from being stored on disk. Only enable it if you have an issue with inode limits. | Enable this option to exclude stale cache created by WordPress, WooCommerce, and others from being stored on disk. Only enable it if you have an issue with inode limits. | Details | |
|
Enable this option to exclude stale cache created by WordPress, WooCommerce, and others from being stored on disk. Only enable it if you have an issue with inode limits. Enable this option to exclude stale cache created by WordPress, WooCommerce, and others from being stored on disk. Only enable it if you have an issue with inode limits.
You have to log in to edit this translation.
|
|||
| Enable this option to allow GC immediately remove the stale cache abandoned by WordPress, WooCommerce and others after doing cache invalidation. | Enable this option to allow the garbage collector to immediately remove stale cache abandoned by WordPress, WooCommerce, and others after cache invalidation. | Details | |
|
Enable this option to allow GC immediately remove the stale cache abandoned by WordPress, WooCommerce and others after doing cache invalidation. Enable this option to allow the garbage collector to immediately remove stale cache abandoned by WordPress, WooCommerce, and others after cache invalidation.
You have to log in to edit this translation.
|
|||
| Enable this option to chunk cache files into smaller directories to avoid an excessive number of cache files in one directory. Only enable it if you have difficulty clearing the cache manually or experience slowdowns when the cache becomes too large. | Enable this option to split cache files into smaller directories to avoid an excessive number of cache files in one directory. Only enable it if you have difficulty clearing the cache manually or experience slowdowns when the cache becomes too large. | Details | |
|
Enable this option to chunk cache files into smaller directories to avoid an excessive number of cache files in one directory. Only enable it if you have difficulty clearing the cache manually or experience slowdowns when the cache becomes too large. Enable this option to split cache files into smaller directories to avoid an excessive number of cache files in one directory. Only enable it if you have difficulty clearing the cache manually or experience slowdowns when the cache becomes too large.
You have to log in to edit this translation.
|
|||
Export as