Known issues in Konstrukt, the back office UI builder for Umbraco.
Konstrukt tries it's best to mimic the content pipeline as closely as possible whilst sticking to public and supported APIs. This is in order to be able to use the full data type suite for editing properties. Unfortunately there are some features in the Umbraco Core that are locked away in internal methods and so does mean some features may not be fully supported. Bellow are a list of known issues to date.
Whilst we have support for persisting the tags value, we don't currently have the ability to write these tags to the
cmsTagsDB table. Unfortunately this is all handled via a
tagsRepositorywhich is internal and so we currently can't save to it like core does.
When using a Multi Node Tree Picker with an XPath filter, only filters starting with the
$rootplaceholder will be valid as all other placeholders expect the property editor to be placed on a content node, with that node being used as context.
Macros in Rich Text Editors don't appear to work properly due to the preview mechanism. They will save and may run on the front end, but you'll get an error notification in the back office as it tries to render a preview.