Currently, subdomain just injects itself into the node add forms quite randomly. This request is to make it the positioning of the field configurable by users. Just like they can choose where to display the title field, the body field, or any other field that goes on a node add form, they should be able to control the positioning of the subdomain field.

Comments

rwohleb’s picture

rwohleb
he/him
Primary language English
commented

The subdomain form should only appear on the node type form, and not the node form. Maybe there is a bug and it's showing on the wrong form.

mrfelton’s picture

mrfelton commented

When you create a node of type Group, there is a field on this form (the node form) that allows you to specify the subdomain that will be assigned to the group. I don't think this is a bug.

It's entitled "Choose a subdomain".

rwohleb’s picture

rwohleb
he/him
Primary language English
commented
Title: Make subdomain field exposed to manage content type form » Make subdomain a pseudo field on group node forms

I see what's going on. Your original title mentioned the content type form so I assumed you were doing subdomains by content type. You didn't mention you were doing domains by organic group. This is definitely something I can look in to.