Skip to main content
added 244 characters in body
Source Link

We had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

[Update] Upon further inspection, I now realize what we had wrong in the first place. We confused the field control (Image) for the field type (ImageField) and tried to register the namespace for the field control in fieldType.

Hope this helps.

Cheers, Christopher

We had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

Hope this helps.

Cheers, Christopher

We had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

[Update] Upon further inspection, I now realize what we had wrong in the first place. We confused the field control (Image) for the field type (ImageField) and tried to register the namespace for the field control in fieldType.

Hope this helps.

Cheers, Christopher

edited body
Source Link

weWe had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

Hope this helps.

Cheers, Christopher

we had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

Hope this helps.

Cheers, Christopher

We had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

Hope this helps.

Cheers, Christopher

Source Link

we had a very similar scenario with a custom image field inheriting from Sitecore Image field. Tried all of the above, without any success whatsoever getting the references added to link database.

The way we solved it was to use the namespace for the field we inherit from when registering the field type within <fieldTypes>:

<fieldType name="Our Custom Image" type="Sitecore.Data.Fields.ImageField,Sitecore.Kernel" />

All of our custom overrides and UI changes for our custom image still function when working within content and experience editor, so I'm guessing that the field registration in node fieldTypes relates only to link database.

Hope this helps.

Cheers, Christopher