Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Bug fixes:
- Make tokens in Entity parent work again.
UI:
- Improve descriptions of views.argTitle plugins.
- Improve descriptions of menu plugins.
Tweaks:
- text field plugin: Filter the field instances. Only consider those that have text_processing enabled.
- Add more cache keys, to make plugin caching work again.
Clean-up:
- Flatten TokenEnabled plugin class.
API:
- Introduce setRoutes() method in describe() method.
Architecture:
- Turn entityreference_prepopulate into mono plugins
- Bug fix: Check for unique wildcard paths "*" in either existing oe the addition of projects was not validating correctly
- Bug fix: Check for valid paths that included wildcards "*" not validating correctly
- Bug fix: Logic in hook_init function not supporting wildcards "*"
- Bug fix: Added support for parameters in project paths
- Bug Fix: Added check for unique path within new project path submission
- Bug fix: Prevented Default project from being enabled from the project listing page when the project ID / Optimizely account ID is not set.
- Added support for complete alias lookups when adding / editing project paths to all for entries using both alias and source values
- Added support for https (secure pages) to Optimizely snippet calls
- Added path alias details to project listing when path setting is < front >, includes the display of the actual path to < front >
- Added support for < front > to also check related alias and source values
- Added support for parameters "?" in project path setting
- Added support for optional slave data base connections on SELECT queries to help performance
- Removed project setting validation to allow more than one project entry using the default project ID - regression from previous 2.1x version
Added translation-agent functionality to identify the origin of a given translation
Improved interoperability (e.g., fixed OAuth conflict experienced by some users, improved Navbar integration, OpenPublic and DemoFramework ready)
Added flexibility for config translation (e.g., added ability to choose a custom workflow, enable/disable any config type)
Other minor bug fixes, optimizations, and improvements (e.g., links added to translate interface and config settings)
This recommended version 4 release of the Lingotek Translation module includes many features, improvements and bug fixes highlighted in our last release. Specifically,
Translation of the following:
built-in interface strings
taxonomies
blocks
views
menus
Comments Improvements
comments (now available to all users)
more efficient api interactions
Workbench Moderation
ability to select the transition for uploading content for translation
ability to select the transition for completed translations