New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development (trunk): Malayalam

Filter ↓ • Sort ↓ • All (1,121) • Translated (550) • Untranslated (553) • Waiting (18) • Changes requested (0) • Fuzzy (0) • Warnings (2)
← 1 2 3 … 75
Prio Original string Translation —
No Varnish address is set. You have to log in to add a translation. Details
No Varnish address is set.

You have to log in to edit this translation.

The spool folder cannot be written. You have to log in to add a translation. Details
The spool folder cannot be written.

You have to log in to edit this translation.

nginx runs where WordPress cannot read its cache; purges are handed to the host through the spool folder. You have to log in to add a translation. Details
nginx runs where WordPress cannot read its cache; purges are handed to the host through the spool folder.

You have to log in to edit this translation.

That folder does not look like an nginx cache, so nothing in it was deleted. You have to log in to add a translation. Details
That folder does not look like an nginx cache, so nothing in it was deleted.

You have to log in to edit this translation.

The nginx cache folder cannot be read. You have to log in to add a translation. Details
The nginx cache folder cannot be read.

You have to log in to edit this translation.

Emptying the whole nginx cache needs the "delete cache files" method, or your host. Single pages are still purged. You have to log in to add a translation. Details
Emptying the whole nginx cache needs the "delete cache files" method, or your host. Single pages are still purged.

You have to log in to edit this translation.

The cache answered HTTP %d. You have to log in to add a translation. Details
The cache answered HTTP %d.
Comment

%d: HTTP status code.

References

You have to log in to edit this translation.

The purge address reached WordPress, not the cache. Check the purge address setting and the server configuration. You have to log in to add a translation. Details
The purge address reached WordPress, not the cache. Check the purge address setting and the server configuration.

You have to log in to edit this translation.

This cache runs on the server, where WordPress cannot read its size. You have to log in to add a translation. Details
This cache runs on the server, where WordPress cannot read its size.

You have to log in to edit this translation.

Cloudflare answered HTTP %1$d. %2$s You have to log in to add a translation. Details
Cloudflare answered HTTP %1$d. %2$s
Comment

1: HTTP status code, 2: Cloudflare’s error message.

References

You have to log in to edit this translation.

Cloudflare is rate-limiting purges; the rest are retried shortly. You have to log in to add a translation. Details
Cloudflare is rate-limiting purges; the rest are retried shortly.

You have to log in to edit this translation.

Cloudflare’s own hit ratio is in your Cloudflare dashboard, under Caching. You have to log in to add a translation. Details
Cloudflare’s own hit ratio is in your Cloudflare dashboard, under Caching.

You have to log in to edit this translation.

Emptying the whole Cloudflare zone is switched off in the settings. Single pages are still purged. You have to log in to add a translation. Details
Emptying the whole Cloudflare zone is switched off in the settings. Single pages are still purged.

You have to log in to edit this translation.

Cloudflare needs a zone id and an API token. You have to log in to add a translation. Details
Cloudflare needs a zone id and an API token.

You have to log in to edit this translation.

Apache stores every page under the address /index.php here, because its cache module runs in the same server as the WordPress rewrite rules. Every address can then be served the same cached page. Put the cache in a reverse-proxy virtual host in front of WordPress (ProxyPass, CacheEnable) instead. You have to log in to add a translation. Details
Apache stores every page under the address /index.php here, because its cache module runs in the same server as the WordPress rewrite rules. Every address can then be served the same cached page. Put the cache in a reverse-proxy virtual host in front of WordPress (ProxyPass, CacheEnable) instead.

You have to log in to edit this translation.

Legend:
Current
Waiting
Rejected
Fuzzy
Old
Changes requested
With warnings
← 1 2 3 … 75

Export as