Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated job to keep the index up to date. See also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/1.6/ref/databases/] Creating

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/1.6/ref/databases/] Creating

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated job to keep the index up to date. See also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/1.8/ref/databases/] Creating

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/stable/ref/databases/]

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/stable/ref/databases/]

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/stable/ref/databases/]

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/stable/ref/databases/]

Weblate can also automatically fix some common errors in translated strings. This can be quite powerful feature to prevent common mistakes in translations, however use it with caution as it can cause Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s databases [https://docs.djangoproject.com/en/stable/ref/databases/]