Classification without multiple selection

Hi,

Here's what I do:

- Create a new classification "News types"
- Add this new classification to the News

This works. But multiple selection is enabled by default, and I need to disable it.
From News, I go to Settings, and:

- I go to News > Controls > NewsBackend > Views > NewsBackEndEdit > Sections > CustomFieldsSection > NewsTypes
- I uncheck the box "AllowMultipleSelection" and save
- I do the same with NewsBackInsert, NewsBackPreview, and NewsBackVersionPreview

Result: I get errors when editing news.
- If I try to save or publish a news, I get: Expecting state 'Element'.. Encountered 'Text'  with name '', namespace ''.
- If I try to preview a news, I get: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

This is with SF 4.1 SP3.

Hi Thomas,

We're aware of this problem and it will be fixed in 4.2

Regards,
Pavel
the Telerik team

I just updated to 4.2, and it still doesn't work. Bummer.

I still get the following error when trying to save a news:
Expecting state 'Element'.. Encountered 'Text'  with name '', namespace ''.

Hi Thomas,

Could you open a ticket and there provide your database and configuration files?

Kind regards,
Pavel
the Telerik team

Hi Pavel,

First, could you please confirm that the bug has indeed been fixed in 4.2? Because I couldn't find it in the change log.
The fact I get the exact same error makes me wonder whether anything has changed.

Thanks.

Hi,

Sorry to hijack this thread

I am also receiving this exact same error too but in a Custom Generic Module but again on a Hierarchical Taxonomy.  So please if you do find a solution to this problem could it be made public.

This is my definition that gives this problem:

Hi Sean,

You're not hijacking the thread, it's totally relevant. Thanks for sharing your experience.
I guess that shows it's not just an isolated issue with my configuration or database.

Hello Thomas,

Here is an update:

Initially we were indeed working on this, but we've found that the fixes done for this bug are causing regressions, so we had to revert the changes and leave the issue open for Sitefinity 4.2. In other words, we confirm that the issue still persist - the same Seam points out. 

We have two options - definitely fix it for SP1, or get someone from the dev. team to provide you with a workaround (this could take a day or two though). It's your call. If it is very urgent, we will push to provide you with a workaround. 

We apologize for all the troubles with this issue. 

Hi Georgi,

Thank you very much for clearing things up.

It's not very urgent, the client could just tell the users not to pick more than one classification item for now, and hopefully they'll behave. Then once the fix is released, change the configuration to disable multiple selection.

That said, I wonder how it'd behave if 2 items were selected, then multiple selection gets disabled afterward. Maybe just keep the first one selected when the item is resaved, or something, but make sure it doesn't trigger a blocking exception.

I created a module with a custom field designated as a classification type. I created a classification list of States. I only want the user to select one State. How can I do this in 5.1?
Thanks!

I created a module with a custom field designated as a classification type. I created a classification list of States. I only want the user to select one State. How can I do this in 5.1?
Thanks!

I'm getting the same issue on 5.0 and I have just the basic fields on a detail view in my Content Module.

Edit: I've just discovered that I've had conflicting model field names with content link field names.  I've resolved that issue but now am encountering another error: