Releases: Jumoo/Jumoo.TranslationManager.Issues
v8.7.6 - Empty set fixes.
This is a patch release of Translation manager, it contains some fixes for error messages that can occur when sending to multiple sets and when some items don't have translatable content.
Fixes
- Fix for "Error one or more nodes could not be created" message - when using a loopback set.
- Spelling fixes in language file
- better logging for errors when you attempt to send languages to multiple sets.
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.6
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.6 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v9.0.1 - Linux casing release
This is a minor patch release to the v9 (Umbraco v9/v8) version of Translation Manager. It contains file casing fixes that mean the package will work better in Linux environments.
Fixes
- Linux casing issues on views and components for Translation Manager.
Getting Translation Manager
Translation Manager 9 is distributed as a nuget package and can be added to your site in a couple of ways.
via dotnet add
via a command line you can add Translation Manager
dotnet add package Jumoo.TranslationManager --version 9.0.1
as a package reference
You can add the dependency directly to your projects .csproj file.
<ItemGroup>
<PackageReference Include="Jumoo.TranslationManager" Version="9.0.1" />
</ItemGroup>via Visual Studio package manager console
If you are old school . install-package still works
install-package Jumoo.TranslationManager -version 9.0.1.
v8.7.5 - Xliff 1.2 updates + tidy
This is a patch release of Translation Manager - it contains some minor fixes for XLIFF 1.2 file support when using nested macros, and some spelling and grammar fixes.
Fixes
- Content sort can be slow - when translation manager is checking each item. #16
- XLIFF data lost when items html items are grouped inside more html #17
- Fixes for spellings etc across pages, by @leekelleher
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.5
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.5-FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
Contributors
Assets 6
v8.7.4 - Nested Nested content fixes.
This is a patch release of Translation manager - it contains fixes for content escaping when you have nested content inside nested content.
Fixes
- Nested content within nested content is not being escaped #15
- after updating to 8.7.2 See exception "The relative virtual path '[xliffpath]' is not allowed here." #14
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.4
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.4-FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v8.7.2 - Blob Path Fixes for Umbraco cloud
This is a patch release of Translation Manager for Umbraco 8 it contains fixes for blob storage on Umbraco cloud.
Fixes
- When files are are stored om blob storage on Umbraco cloud you cannot include the "/media" element of the path - this update removes the /media from file names before requesting them from the blob storage providers - the community provider supports both /media and non-media paths - so will continue to work with this update.
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.2
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.2 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
8.7.1 - Blob Fixes
This is a patch release for Translation manager it fixes a few issues with blob storage urls and the RegEx Ignore parameters we introduced in v8.7.0
Fixes
- #12 Fixes media path is not correct on download using blob provider with a VirtualPathProvider that is disabled
- Fix for RegEx ignore path 'Value cannot be null` error.
- Fix for Json detection in MultiListValueMapper (when list items start end with
[]but are not json)
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.1
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.1 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v8.7.0 - Media / RegEx Properties
This is a major.minor release of Translation Manager for Umbraco v8. It contains support for Azure Blob storage, regex pattern matching in property settings and custom xliff inline splitting.
Azure blob storage
The Xliff Connector will now honour any Blob storage settings you might have for your media folder. (Finally fixing #9). This means the default translations folder of /media/xliff_translations will now be stored and read from the blob storage for your media if it is set. - this change does not affect anything if you are not using blob storage or if you have moved the translation folder out of the media folder..
Breaking: this change will mean that the connector will now look in the media folder on blob storage, if you have had blob storage set, previous files will have been on the web server disk - you will need to move the xliff_translations folder from the local media folder to your blob storage for existing job files to be found.
Xliff custom inline splitting
by default when generating xliff - the html is split by all non-formatting blocks (e.g p, table, span not split on strong, em, u, etc) - there are sometimes when people migh want content not to be split by a html
(see https://our.umbraco.com/packages/backoffice-extensions/translation-manager/translation-manager-feedback/106533-overriding-default-mappers)
Adding the following setting to the xliff provider settings element of the translations.config file will allow you to specifiy custom tags to not split on
<provider name="xliffFile">
<!-- other settings will be here -->
<add key="inlineCodes" value="span" />
</provider>
Before:
<group id="u1219-1-g" name="h2">
<unit id="u1219-1-1" name="#text">
<segment>
<source>Run your shipments </source>
</segment>
</unit>
<unit id="u1219-1-2" name="span">
<mda:metadata>
<mda:metaGroup id="span_attributes">
<mda:meta type="class">underline</mda:meta>
</mda:metaGroup>
</mda:metadata>
<segment>
<source>smoothly</source>
</segment>
</unit>
<unit id="u1219-1-3" name="#text">
<segment>
<source> from port to port.</source>
</segment>
</unit>
</group>
After:
<unit id="u3-1" name="h2">
<originalData>
<data id="d1"><span class="underline"></data>
<data id="d2"></span></data>
</originalData>
<segment>
<source>Run your shipments <pc dataRefEnd="d2" dataRefStart="d1" id="1" type="fmt">smoothly</pc> from port to port.</source>
</segment>
</unit>
RegEx Pattern matching
As of this update you can now tell translation manager to ignore properties based on a regex pattern. In short this enables us to ignore properties that might be inside a nested content element (e.g in the grid, nested content or a block list #11)
Upon update the set settings will have a new option (use regex pattrern)
with this value selected - Translation Manager will attempt to find a property based on regEx values of the property path.
Almost always just putting the property name of the nested property will work.
but if you want to be more granular in control this allows you to do this.
Every translated item will have a property path value which you can see when it is sent to translation:
In the example above:
features/feature/featureName is
- the path name of a property that is inside a
featuresproperty on the main page - this then has a
featuredoctype as a nested doctype - within this nested type 'featureName` is the property.
to exclude featureNameproperty from translations (with RegEx Option turned on)
| setting | note |
|---|---|
-featureName |
will exclude featureName whenever it is used |
| `-/featureName' | will exclude featureName whenever it is used inside another content type |
-/features/featureName |
will exclude featureName only when its used in the features doctype |
| `-/feature/.+/featureName | will exclude featureName when it is used in a nested content type of a feature property |
| `-/features/' | will exclude all properties from the features doctype when it is used nested inside parent content. |
note the - in front of a property name.
this is a very powerful feature - but can be quite complicated! - you should use caution and test throughly when setting regex patterns on your property exclusions
--
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.7.0
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.7.0 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.7) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v8.6.2 - Xliff Blank target improvments
This is a patch release update for Translation Manager for Umbraco v8.x - for more info see https://jumoo.co.uk/translate
Is contains a fix for detecting blank target elements in xliff when the target starts with or contains a spanning element.
Fixes
#10 - Xliff target is reported as blank, when it sometimes isn't
All changes are listed under the release/8.6.2 label
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.6.2
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.6.2 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.6) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v8.6.1 - Permissions tweaks.
This is a patch release update for Translation Manager for Umbraco v8.x - for more info see https://jumoo.co.uk/translate
it contains some UI and dictionart item fixes, for issues introduced in 8.6.0 when we added the permission checks.
Fixes
- #7 Approval of Dictionary items fails - with object not found
- #8 User can still see "Save and Review" when they don't have permissions (action then fails).
All changes are listed under the release/8.6.1 label
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.6.1
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.6.1 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.6) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.
v8.6.0 - Translation check updates
This is a Minor release update for Translation Manager for Umbraco v8.x - for more info see https://jumoo.co.uk/translate
Fixes
- #1 Translating Dictionary fails with "The element must contain one or more Containers" when submitting job directly
- #2 Error "github" button points to wrong Repo
- #4 Bug: View button for target doesn't show variant language on loop-back.
- #5 Save and Publish and Save and Approve buttons don't obey content privileges
- #6 Rouge "Licence is correct but not for this domain" message
Updates
- #3 Feature: Warn when target nodes cannot be found because pages are not linked.
All changes are listed under the release/8.6.0 label
Installing Translation Manager.
We recommend you install Translation Manager via NuGet / Visual Studio Package Manager
PM>install-package Jumoo.TranslationManager -version 8.6.0
you can install the Umbraco Package from the Umbraco back office or the our.umbraco.org package page.
Upgrading
via nuget:
PM>update-package Jumoo.TranslationManager -version 8.6.0 -FileConflictAction Ignore
There should be no issues upgrading between patch versions of Translation Manager (e.g 8.5.3 -> 8.5.4).
We recommend you do not have open translation jobs when upgrading minor versions (e.g 8.4 -> 8.6) - In general there should be no issue upgrading with open jobs - but this reduces any risks if data structures are altered during a upgrade.