Is using type: group in plugins no longer working?

Support
1

Has type: group become obsolete in plugins?

I tried using it in a plugin, but it doesn’t work. The input field behaves like a text field instead of the expected select.

Has type: group been deprecated?

  quectel_online_customer_general_customer_group_id:
    default: ""
    type: group
    client: true
2

I think it has to be type: group_list

3

Yes, I looked into it, and basically everyone uses type: group_list.

However, my requirement is to select only one. If I use type: group_list, I have to add a custom validation to prevent multiple selections. While this works, it feels very awkward.

Why was type: group removed? Just like with type: category, there are scenarios where only a single selection is needed. It shouldn’t be a blanket rule.

Unless type: group_list can support the case of selecting just one.

4

I’m not sure it was removed, it looks more like it was never really implemented maybe? It does seem odd.

Think this might be worth opening a Contribute > Feature request for to be honest.

5

Actually @gerhard you have any more context? I see there is a note about a TODO regarding the documentation

6

I’m not sure. As the TODO notes, while working on the importer script, I noticed that the type group seems to be stored as a text, not an ID. I guess it was never implemented as a select. In the beginning of Discourse we mostly had text fields for site settings. This might still be a remnant of it.

7

Yes, it’s in the form of a text box now. Looks like it was never implemented. :rofl:

8

Indeed not implemented so group_list was the correct answer, until