Fixed an issue that prevented newly created Commerce content versions from being saved.

Fixed an issue that prevented newly created Commerce content versions from being saved.

Introduced new plugin version that supports Optimizely 13 running on .NET 10.

Internal improvement released.

Fix content types with only built-in/synthetic properties being excluded by includeUnlocalizable=false filter.

Added optional parameter xhtmlEditorRender that manages ingestion of content from XHTML string property. If parameter xhtmlEditorRender is set to true the connector will use the old rendering method (editorHtml) used prior to the change implemented in 1.3.0.

Introduced support of PropertyContentReferenceList type.

Plugin renders XHTML content with respect to local links. Optimizely team recommended to use ToString() / ToHtmlString() methods to take content of XHTML components. This causes the provider to respond to such components differently.
⚠️ Important: This update may cause the resubmission of content containing XHTML in the Smartling Dashboard. After upgrading to v1.3.0, previously translated XHTML content that contains links may be detected as changed internally, even though the actual content has not been modified.

If Automation of Prior Requests for Translation is set to Automatically request translation, the content will be automatically re-requested for translation. These requests will appear as jobs with no content to translate, since the translatable content has already been translated.

Redelivery of translations may hide any manual updates made to translated content in Optimizely.
If you have any questions or concerns, contact your Smartling Solution Architect or another Smartling representative.

Enabled block/media root folder (For All Sites) for custom asset type.

Added support of content asset root folder for pages (For This Page) and (For This Block).

Fixed bug for case when EPiServer responds with null on content request.

Introduced Custom asset type. This asset type is built for all content types that conform to IContent, IVersionable and ILocalizable interfaces. For example, you can build a custom content type by building a class that inherits from StandardContentBase.

The plugin no longer performs any action when attempting to publish content that is already published.

The plugin responds with the last modified date for the content, to be used within the Smartling UI.

The plugin responds not.found on references request of missed content. This means that if a request is made to list references for a particular content ID and the plugin cannot find that content (i.e., it doesn't exist), it will return not.found instead of throwing an error.

The connector now updates URL segments by replacing special characters—such as ü with u.

The connector now checks a nested block's properties to determine if it is localizable.

Block/page/catalog/media references can be requested for specified locale.

Added filter by content type for project items.

Plugin hides missed locales for Media entries.

Name and Name in URL property are available for Medias.

Issue with filtering out Primary Draft content is fixed.

Enabled search provider for Media assets.

The asset search in Smartling now allows you to search for the content type "Media".

Added support of Media asset type.

Added support of multisite configuration.

Added support of Geta.Optimizely.GenericLinks link properties

Bug fix: The Episerver asset list in Smartling now always shows the latest Status (Episerver) for each asset.

Fixed enumeration of child content, using the provided source locale.

Added support of PropertyList property

Added support of link item property via JSON.

The release package is available to be downloaded here.

Added support of scheduled publishing.

Bug fix: The Episerver asset list in Smartling now always shows the latest Status (Episerver) for each asset.

Bug fix: Fixed enumeration of child content, using the provided source locale.

Added support of scheduled publishing.

Added support of a custom property built upon a String or LongString property.

Added support of filter by status.

Added support of Name property for page/block/content
​

Fixed support of SeoUri property of a commerce entry.

Added support for Content Area Item's Display As option.

Fixed translation of Form elements.

Added support of a custom property built upon a String or LongString property.

Fixed support of SeoUri property of a commerce entry

Added support for Content Area Item'sDisplay Asoption.

You can now filter by status

Added support of Name property for page/block/content
​

Context preview can be shown using base URL defined in preview HTTP request header.

Fixed translation of Form elements

Simple address and Name in URL properties are shown in Smartling dashboard with the same labels as they're shown in EPiServer UI.

Simple address and Name in URL properties are shown in Smartling dashboard with the same labels as they're shown in EPiServer UI.

Display name and code are shown for a catalog.

Display name and code are shown for a catalog.

Removed EPiServer Commerce dependency. The plugin supports catalog via reflection.

EPiServer plugin supported .NET5 Core

Removed EPiServer Commerce dependency. The plugin supports catalog via reflection.

Catalog related items can be ingested for translation

Fixed error on retrieving fields for manually created custom fields

Introduced fast pagination for sort and filter

Include references from non-localizable fields when asset's related items were requested for translation as well

Fixed issue related to search functionality in the case when Episerver's search providers are installed

Extended response of /dictionary/content-types/{con

tent-type-id}/fields endpoint.

Added contentTypeId information for nested block field.

Retrieve information about Episerver setup

Export original content to Smartling

Deliver translations back from Smartling