Silva

formulator validate assumes non-unicode

Bug #101699 reported by Andy Altepeter on 2006-06-01

Affects		Status	Importance	Assigned to	Milestone
	Silva	Fix Released	Medium	Unassigned	Silva 1.6

Bug Description

When modifying/setting a metadata set from custom code (e.g. a pythonscript),
the paradigm:

  md = context.service_metadata.getMetadata(obj_ver)
  silvaextra = md.get('silva-extra',acquire=0)
  silvaextra.data['publicationtime1'] = date1
  silvaextra.data['publicationtime2'] = date2
  md.setValues('silva-extra',silvaextra)

does not work. (at least) Formulator.Validator.StringValidator.validate assumes
input values are byte-encoded. Using the above paradigm the values are unicode.

Fields that support forced unicode to verify the value is not already unicode
before encoding.

Tags:

Revision history for this message

Andy Altepeter (aaltepet) wrote on 2007-10-03:

The latest formulators released with Silva now check whether input is unicode or not. This is resolved.

Changed in silva:
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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