An error is occurring for one of the fields during our import of a csv file. We are using Umbraco 4.7.1.1.
The error is:
Error while importing data for property 'manager', datasource record UserID= '71275', Error: could not find file
This is a strange error as we don't have uTagsy installed and there are no properties that use uTagsy (or have tags ) in the docType.
Some further investigation has revealed that the property 'manager' is a DataType that is using the Umbraco usercontrol wrapper. The Data Editor GUID for the usercontrol wrapper is d15e1281-e456-4b24-aa86-1dda3e4299d5.
The UTagsyFieldProvider is using the same Data Editor GUID for the PropertyEditorAlias. I suspect that the uTagsy DataType is also using the usercontrol wrapper.
So, it looks like the manager property is being identifed as a uTagsy DataType during the import. Even without this error, I think we are going to need to create our own FieldProvider to import this value correctly. Is there a way to force the usage of our own FieldProvider?
You are absolutely right. I think this bug was introduced since the change to FieldProviders. I will fix this now and it will be in 2.5.1. If you want the patch now send me an email please [email protected] and I'll send you the installer.
Could not find file utagsy.config
An error is occurring for one of the fields during our import of a csv file. We are using Umbraco 4.7.1.1.
The error is:
Error while importing data for property 'manager', datasource record UserID= '71275', Error: could not find file
This is a strange error as we don't have uTagsy installed and there are no properties that use uTagsy (or have tags ) in the docType.
Some further investigation has revealed that the property 'manager' is a DataType that is using the Umbraco usercontrol wrapper. The Data Editor GUID for the usercontrol wrapper is d15e1281-e456-4b24-aa86-1dda3e4299d5.
The UTagsyFieldProvider is using the same Data Editor GUID for the PropertyEditorAlias. I suspect that the uTagsy DataType is also using the usercontrol wrapper.
So, it looks like the manager property is being identifed as a uTagsy DataType during the import. Even without this error, I think we are going to need to create our own FieldProvider to import this value correctly. Is there a way to force the usage of our own FieldProvider?
Thanks
Dallas
HI Dallas,
You are absolutely right. I think this bug was introduced since the change to FieldProviders. I will fix this now and it will be in 2.5.1. If you want the patch now send me an email please [email protected] and I'll send you the installer.
Best regards,
Richard Soeteman Soeteman Software
Quality Umbraco packages | http://www.soetemansoftware.nl
is working on a reply...