instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous translation Licensing translations Translation Optional Weblate modules Customizing Weblate Django admin interface Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently files YAML files DTD files Windows RC files Excel Open XML Others Adding new translations Version control integration Accessing repositories Git GitHub Gerrit Mercurial Subversion Weblate’s Web API REST

instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous translation Licensing translations Translation Component Lists Optional Weblate modules Django admin interface Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently files YAML files DTD files Windows RC files Excel Open XML Others Adding new translations Version control integration Accessing repositories Git GitHub Mercurial Subversion Weblate’s Web API REST API

authorization will likely need changes. You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for for controlling the order in which the authorization directives are applied. Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This port your configuration to use Require dbm-group ... in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests

Quick setup guide Installation instructions Weblate deployments Upgrading Weblate Authentication Access control Translation projects Language definitions Continuous translation Translation process Checks and Whiteboard messages Component Lists Optional Weblate modules Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently JSON .Net Resource files CSV files YAML files DTD files Others Adding new translations Version control integration Accessing repositories Git GitHub Mercurial Subversion Weblate’s Web API REST API

Quick setup guide Installation instructions Weblate deployments Upgrading Weblate Authentication Access control Translation projects Language definitions Continuous translation Translation process Checks and Whiteboard messages Component Lists Optional Weblate modules Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently JSON .Net Resource files CSV files YAML files DTD files Others Adding new translations Version control integration Accessing repositories Git GitHub Mercurial Subversion Weblate’s Web API REST API

Quick setup guide Installation instructions Weblate deployments Upgrading Weblate Authentication Access control Translation projects Language definitions Continuous translation Translation process Checks and Whiteboard messages Component Lists Optional Weblate modules Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently JSON .Net Resource files CSV files YAML files DTD files Others Adding new translations Version control integration Accessing repositories Git GitHub Mercurial Subversion Weblate’s Web API REST API

authorization will likely need changes. You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for for controlling the order in which the authorization directives are applied. Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This port your configuration to use Require dbm-group ... in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests

instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous localization Licensing translations Translation Optional Weblate modules Customizing Weblate Django admin interface Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently Windows RC files App store metadata files Excel Open XML Others Adding new translations Version control integration Accessing repositories Git GitHub Gerrit Mercurial Subversion Weblate’s Web API REST

instructions Weblate deployments Upgrading Weblate Backing up and moving Weblate Authentication Access control Translation projects Language definitions Continuous localization Licensing translations Translation Optional Weblate modules Customizing Weblate Django admin interface Translation workflows Translation access Translation states Direct translation Peer review Dedicated reviewers Enabling reviews Frequently Windows RC files App store metadata files Excel Open XML Others Adding new translations Version control integration Accessing repositories Git GitHub Gerrit Mercurial Subversion Weblate’s Web API REST

authorization will likely need changes. You should review the Authentication, Authorization and Access Control Howto, especially the section Beyond just authorization which explains the new mechanisms for for controlling the order in which the authorization directives are applied. Directives that control how authorization modules respond when they don't match the authenticated user have been removed: This port your configuration to use Require dbm-group ... in place of Require group .... Access control In 2.2, access control based on client hostname, IP address, and other characteristics of client requests