What's new in Loco Translate
Version 2 is a complete rebuild of version 1. Although many features will appear much the same, we started from scratch to ensure more solid foundations for continued development and improvement. Here's a quick run down of the biggest changes introduced in version 2.0.
The new dashboard splits themes, plugins and core translations into separate lists. It was a common complaint of version 1 that these lists were too long and often slow to render. Clicking a bundle displays all its translations grouped into subsets.
You may find there are more clicks to reach to the specific file you need, but we're working on ways to surface recently used items while still keeping things organized.
Although many themes and plugins only have a single set of translations, version 2 can support any number of sets. By way of example, WordPress core translations are comprised of four sets of translations (three of which are in the same text domain). Loco's new configuration model can support all the core translations as a single "bundle".
The single biggest problem with version 1 was that a bundle would only be translatable if it was set up in a standard way. This limitation was compounded by a lack of configuration tools. Quite simply if it didn't work, you were more-or-less stuck.
Version 2 has a flexible configuration model so if a bundle is set up in a strange way, you can tell Loco how to make sense of all the files. We're also experimenting with our own registry of bundle descriptions so Loco can configure unconventional bundles automatically for non-technical users.
Safe languages folder
wp-content/languages/* directories are not safe for storing your custom translations. Auto-updates are known to overwrite files in this location with community translations.
Version 2 can now save files in a 'protected' directory at
wp-content/languages/loco. A runtime helper is included in the plugin to ensure themes and plugins can load translations from this folder.
Remote file system access
Because WordPress stores translations in regular files, Loco can't save translations unless the web server can write to disk. This poses technical issues for anyone who can't make the required file permission changes. Version 2 can now save files over a remote file system connection. This works like the WordPress update system, by entering FTP or SSH credentials.
Version 2 introduces some control over which WordPress roles have access to translation screens. Currently this is limited to a single
"loco_admin" capability providing full access to Loco admin screens. This is likely to be expanded in future releases to provide more fine-grained access control. The plugin also defines a
"translator" role which can be assigned to users without giving them access to any other part of your WordPress. This role automatically inherits the
"loco_admin" capability only.
Managing roles is done from the Loco Translate settings screen. This is the only screen that doesn't observe the
"loco_admin" capability. Altering plugin settings requires the
"manage_options" capability, which site administrators should already have.
By popular request, version 2.0 provides a delete function for removing unwanted PO, MO or POT files.
For advanced users and developers, you can now view PO and POT highlighted source code with clickable file references that display the related PHP source. This helps identify whether POT files are in sync with the source code.
The original version 1 of this plugin is no longer maintained, and completely unsupported.
It is available for manual installation only, via the Git archive.