Set up a continuous, automated, and streamlined localization process for your multi language WordPress websites and blogs. By integrating WordPress and Lokalise, you gain access to a modern translation management system with robust functionalities.
Using Lokalise to manage localization processes leads to faster launches, fewer errors, and savings on translation budgets. Here are some of the features that make this possible:
- Machine translation suggestions for rapid results
- Translation memory (TM) that stores your previous translations and helps improve consistency, as well as reducing translation costs and turnaround time
- Comments and chat for the whole project or a particular translation
- Powerful filter and search functionalities on multiple levels (string, status, language, etc.)
- Automated notifications when certain actions are completed
- And many more.
Lokalise is a collaborative translation platform which means you can work with your team and external partners, creating a single source of truth for all your translation projects.
This plugin is relying on a 3rd party as a service. In order to use the plugin, you are required to have an account on http://app.lokalise.com. Once you have a paying account, you can configure the WordPress plugin in Lokalise environment by following the documentation. After the plugin is configured, you can import & export the content between Lokalise & WordPress. No personal data or any other sensitive information is sent to 3rd parties.
For a detailed explanation of how the integration works and how to set it up, take a look at our WordPress integration tutorial.
There are no reviews for this plugin.
Contributors & Developers
“Lokalise Companion Plugin” is open source software. The following people have contributed to this plugin.Contributors
- Enable Lokalise to access supported ACF fields from ACF Pro plugin
- Fixed default locale for polylang translation provider
- Fixed plugin version
- Fixed default locale
- Removed Guard Cookie
- Generate full auth page URL
- Fixed fatal error for caused by getallheaders()
- Added missing get_footer() call at end of authorization view
- Inform administrators that more than one supported i18n plugin is enabled
- Added multisite support
- Added support for Advanced Custom Fields
- Added support for Polylang
- Added authorization independent from standard login page
- Added support for custom post types
- Added authorization header validation to environment rest
- Added apache_request_headers as base if possible
- Changed readme.txt
- Added readme.txt, ReadmeOSS
- Fixed hard-coded table prefix
- Added list of post types that can be edited by current user to environment REST
- Dependency to process request headers
1.0.3 – 2020-07-02
- Added CHANGELOG.md
- Changed correct link to documentation
1.0.2 – 2020-07-02
- Fixed authorization secret regeneration
1.0.1 – 2020-07-01
- Added default locale to environment REST
1.0.0 – 2020-06-19
- Added plugin code