Import of nonexisting skin gives a formulator SelectionValidator error.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Silva |
Fix Released
|
Medium
|
Eric Casteleijn |
Bug Description
If you're using silva layout, you can set the skin in the metadata user interface for publications. This is the metadata set silva-layout, metadata element 'skin'. The skin selection shows a list of skins that are installed that you can use. If you select an installed skin, then export that publication as XML,
and then import this into another Silva which doesn't have that skin installed,
you see the following exception:
Module Products.
Module Products.
Module Products.
Module Products.
Module Products.
ValidationError: unknown_selection
This is because the skin with the selected name is not recognized by the other Silva and the formulator SelectionValidator trips over it.
We should modify the importing system to give a better error message so it is clearer to the user what's going on. Alternatively we can set the skin to a default skin that *is* installed and send a warning message to the log.
Changed in silva: | |
assignee: | thisfred → aaltepet |
Changed in silva: | |
status: | Fix Committed → Fix Released |
I think the second option – set the skin to a default skin that *is* installed and send a warning message to the log – is much better. I can't imagine that someone would abort an import if a skin wasn't installed, so we shouldn't do that either.