lingotek 7.x-5.10

This release adds significant flexibility and more consistent controls for sites using Lingotek Translation, Entity Translation, and Content Translation concurrently. Sites that use Lingotek for translation of some languages or fields, while leaving others to be translated using other means are now able to make changes within Drupal while protecting the languages or fields managed by Lingotek. This field-level protection is now uniformly applied across both Entity Translation and Content Translation.

This release also introduces a hook that gives module developers the ability modify aspects of a translation's source document such as its title, before it is uploaded to the Lingotek TMS.

Version 7.x-5.10 also includes numerous other new features and enhancements, improved support for purely node-based translation sites, as well as bug fixes. Below is the complete list of changes for this version:

• by bisle: fixed crowdsourcing error when node enabled for Lingotek has language not enabled.
• by bisle: fixed disabled node-based translations to not display the crowdsourcing link.
• by robertdbailey: fixed the managed-by-Lingotek warning to be displayed only on the initial node form load, not on subsequent ajax calls.
• by robertdbailey: removed the restriction on saving changes to unmanaged fields of nodes managed by Lingotek.
• by bisle: fixed dependency on entity translation for node tab access.
• by bisle: fixed bug in node view page not showing the Help Make It Better link.
• by bisle: fixed Lingotek Translation Management tab to show setup message if the module has not been set up yet.
• by bisle: fixed bug causing downloaded node-based translations to be set to language-specific if using the automatic profile.
• by bisle: fixed Lingotek node-view hook to run only if the node is managed by Lingotek.
• by bisle: fixed the changes to the node form to show only when the node is being managed by Lingotek.
• by clarticus, smithworx, robertdbailey: added hook that runs prior to uploading documents to the Lingotek TMS, which can be used to modify the document title or make other changes to the document.
• by robertdbailey: renamed lingotek.api.inc to be lingotek.remote.inc, in preparation for creation of Lingotek hooks.
• by clarticus: fixed the creation of translated nodes under node-based translation to include the untranslated fields.
• by robertdbailey: added back setting the default language of a new node to be the site default language.
• by robertdbailey: fixed bug causing new node creation to be disabled initially.
• by robertdbailey: fixed bug in node-creation form when node ID is missing.
• by robertdbailey: added preference to always show non-Lingotek translate tabs.
• by robertdbailey: consolidated use of form_alter into node_form_alter to make the node form-loading code uniform for both entity translation and node-based translation.
• by clarticus: fixed node form to allow edits to unmanaged nodes.
• by bisle: fixed problem loading settings page in Commons installs when no target nodes exist.
• by bisle: fixed node form hook to not set the target status of any translations at the time the form is loaded.
• by bradydowling: one-off nodes can now be changed in bulk to conform with their content type's translation profile
• by bisle: fixed editing of entity translations in Drupal where the language is not enabled by Lingotek.
• #2297173 by gaurav.goyal: Fixed bug causing menu link translations to be removed when updating a node.
• by robertdbailey: removed unused language-retrieval functions
• by robertdbailey: fixed bug in marking downloaded translations to be language-specific when using node-based translation.
• #2510876 by joe_wood: added checks for permission and Lingotek profile to comment-view hook
• #2295637 by gaurav.goyal: fixed bug causing fatal error caused by overuse of field-collection-specific code