Silva

Unknown metadata fields break import

Bug #120173 reported by Eric Casteleijn
2
Affects Status Importance Assigned to Milestone
Silva
Fix Released
Low
Eric Casteleijn
Silva 2.0.6

Bug Description

When importing silva xml that uses metadata fields/sets that aren't defined on the importing server, it should silently ignore those, and not error as it does now.

Eric Casteleijn (thisfred)
Changed in silva:
assignee: nobody → thisfred
status: Unconfirmed → Confirmed
Revision history for this message
Andy Altepeter (aaltepet) wrote :

The metadata system also shouldn't complain with an error when a metadata field value no longer exists (think ListField).

Revision history for this message
Eric Casteleijn (thisfred) wrote :

Good point, I'll try to take this along...

Revision history for this message
Eric Casteleijn (thisfred) wrote :

Two points:

- Unknown metadata sets already generate a warning, not an error, so my bug report is incorrect.

- the problem with field values is that validation happens on a whole metadata set at once. If I remove the rasing of the error, the whole set will be dropped for a piece of a content when one field fails validation... :(

Revision history for this message
Eric Casteleijn (thisfred) wrote :

A fix is checked in and this should be working. (Fields are imported separately, if one fails, it generates a warning not an error.)

Changed in silva:
status: Confirmed → Fix Committed
Andy Altepeter (aaltepet)
Changed in silva:
importance: Undecided → Low
milestone: none → 2.0.6
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.