Upgrade to U6.2.1 throws "More than one converter for property type xxx" error on all CheckBoxTree datatypes
I just upgraded a site to Umbraco 6.2.1, and I'm seeing a "More than one converter for property type xxxx" error occurring on all data types that use uComponents: CheckBoxTree.
To be honest I'm a bit surprised that no one else had noticed this sooner, our v6.0.0 has been out in the wild since last October - either no one is using it, or wanted to complain about it. (Jeez ya think someone would test this stuff eh?) ;-)
copy all relevant *.dlls from src into target umbraco installation
make sure that you are properly using the new data type conversion.
A side-effect of this change from textstringarray to checkboxtree property value convertor is that when you call GetProperty you are no longer getting a String, but a IEnumerable
Upgrade to U6.2.1 throws "More than one converter for property type xxx" error on all CheckBoxTree datatypes
I just upgraded a site to Umbraco 6.2.1, and I'm seeing a "More than one converter for property type xxxx" error occurring on all data types that use uComponents: CheckBoxTree.
Any ideas?
Cheers,
Mike
Hi Mike,
There was a typo on the
PropertyEditorValueConverter
for TextstringArray. (My bad)There is a source-code fix available, but we haven't rolled it into a release yet. https://github.com/uComponents/uComponents/pull/21
Current options are to either apply the source-code fix manually, or delete the
uComponents.PropertyEditors.ValueConverters.dll
from the /bin folder.Cheers,
- Lee
Ah, OK, makes sense - thanks v much for the quick response too :)
I'll remove the dll for now - cheers.
Mike
Sorry for the headache.
To be honest I'm a bit surprised that no one else had noticed this sooner, our v6.0.0 has been out in the wild since last October - either no one is using it, or wanted to complain about it. (Jeez ya think someone would test this stuff eh?) ;-)
Testing? Pshhhh....
So the official response is "who cares about 6.2.x noone is using that anyway, build it yourself" Is that correct?
I have not found any indication that the above fix was ever released.
For future Google sleuths:
A side-effect of this change from textstringarray to checkboxtree property value convertor is that when you call GetProperty you are no longer getting a String, but a IEnumerable
GetProperty<>
Regards, Daryl
is working on a reply...