Reviewing and testing proposed fix
Fixed on version 8x-2.28
Patch planned for future version 2.28, to be released on monday Jan 15th, 2024. The patch removes the validation altogether, as it's not intended to happen within the connector, but rather in Content API, which is part of the Lionbridge Translation Services integration platform. This change not only solves the same issue, but will reduce complexity within the connector implementation
Exceptions are expected when trying to use the connector without configuring it, the item lacks details about the exceptions, logs, or stack trace information, is not following the installation and configuration guides, and is expressed using curse language.
For all those reasons, this reported issue is not to be fixed.
If this issue has any impact on production or staging environments, after following the installation and configuration guides, please report it back again with the details mentioned above.
This is as designed. The connector is not meant to support multiple Drupal Lionbridge Providers on the same instance. Instead, the Lionbridge provider offers a list of Lionbridge Translation Providers, within the same configured Drupal Lionbridge Provider. Also, the connector is not designed to offer dual staging and production connectivity. This is also per design, to avoid mixing up experimental translations, that don't incur in costs, and production translations which incurs in costs