DC 5.2.0 10 Known issues

DAM-4127

Tree muli-language bug - Solr

In 5.2.0 and 5.2.1 an issue existed where trees were affected if you had multiple languages. As of 5.2.2 (and 5.3.0) this issue has been fixed. Still, there can be a disparity between assets in one language, and assets in another language in MM. Therefore, an update from 5.2.0/1, also necessitates that your Solr core is repopulated.

None.

Can only be solved by SQL

DAM-4146

Solr/Searchproxy update instabilities

We are seeing that the searchproxies and Solr indexes fail to update correctly under certain circumstances. This typically happens under high load and/or on replace/crops of assets

Repopulate searches

DAM-4147

Deleted assets are not removed on repopulate searchcache

If you delete an asset and the event is somehow lost, the asset remain in the search proxy and can be found in MM5. Repopulating the search cache does not resolve this issue

Stop Solr and delete the data folder in the core of Solr. Restart solr and repopulate search cache

DAM-4152

Digizuite core does not work in load balanced environments

This is caused by a fix for events going missing against sitecore, which we would rather keep working.

The DC can still technically be set up in a load balanced configuration, however the “event2job” and “cronsevice” sub applications under automationworkflows should only be enabled on one server.

DAM-4187

ItemHandler.InsertDefaultValue: ComboValue is always matched by "textvalue"

When using “InsertDefaultValue” with combo or tree type metafields a match is done. The issue is that the match is done against “textvalue” aka “displayvalue” even if “optionvalue” is requested. The issue will be seen when there is a difference between “textvalue” and “optionvalue”. Example: workflows setting MM “Asset status”. Consequence: access rights on the tree or combonode in question will revert to the metafields access rights (or parent treenode in case of treenodes with a parent). As the default match for treenodes is “textvalue” the issue will only be seen if the InsertDefaultValue eventdata is configured explicitly to use “optionvalue”.

Use “textvalue” matching by inserting the <MatchByTextValue/> tag in eventdata.

DAM-4192

Exported variable for a workflow is broken when upgrading

We run some migrations during startup to change some workflows, in case we changed the definition of a step. This process will break if the workflow uses any exported variables (Which is most workflows).

The workflows will have to be corrected manually. We will be releasing 5.2.6 with a fix, the avoid it happening again. However if you already have upgraded to 5.2.2-5.2.5, then you need to correct the workflows manually, as they will already have been broken.