Posted by leeksoup on Mon, May 29, 2023 - 11:06pm

Is there a way to rearrange the fields in the node add / edit form for a content type without changing the display of the full node?

For example, I have a content type of "review" for ... reviews. It has a LOT of fields, but the essential ones are very few. Is there a way to position those fields at the top of the form for users entering reviews, but not change the ordering (and grouping) of the fields when displaying the content for site visitors?

It may be something simple I'm overlooking, or maybe there is no such thing. I don't know. Thanks.

Accepted answer

@leeksoup you can drag the fields on the „Manage fields“ page to custom positions, and save the form. The new order is what content editors will see when they add or edit a content item, but the full display for visitors shouldn’t be affected by it.

Only exception: When you create the content type and add some fields, at first their order will be the same at both places. But when you change the field order later, it should only be applied to / for the place you are changing, without affecting other places.

Maybe I misunderstand what you‘re trying to achieve? I’m currently on a vacation, so can’t explain better at the moment, sorry!

Most helpful answers

Yes, to arrange the fields of

Yes, to arrange the fields of the add / edit form of your content type, go to the "Manage fields" tab of your content type, e.g. admin/structure/types/manage/post/fields. The fields of the content display are arranged on "Manage displays", e.g. admin/structure/types/manage/post/display (usually Default, or Full content).

PS: You said your content type has many fields. If you install the Field Group module, you can organize the fields of the add / edit form in groups, e.g. in collapsible fieldsets or in tabs.

Comments

Olafski's picture

Tue, May 30, 2023 - 2:18am by Olafski

Yes, to arrange the fields of the add / edit form of your content type, go to the "Manage fields" tab of your content type, e.g. admin/structure/types/manage/post/fields. The fields of the content display are arranged on "Manage displays", e.g. admin/structure/types/manage/post/display (usually Default, or Full content).

PS: You said your content type has many fields. If you install the Field Group module, you can organize the fields of the add / edit form in groups, e.g. in collapsible fieldsets or in tabs.

Sat, Jul 29, 2023 - 9:39am by leeksoup

@Olafski - thank you. I somehow overlooked your reply until now.

I knew about that page, but thought if I move things around there, it also affects the normal display. But I think you are saying I could change the default display mode to suit content creators / editors and then change the Full content mode to what site visitors should see. Brilliant!

Oh yes, I already have some Field groups set up for just that. :)

Sat, Jul 29, 2023 - 9:59am by leeksoup

@Olafski - I just tried this, and the add/edit form uses the settings I have in the Full content display mode, not the default mode. So I am back to the original issue:

Is there a way to rearrange the fields in the node add / edit form for a content type without changing the display of the full node?

Olafski's picture

Sun, Jul 30, 2023 - 12:35pm by Olafski

@leeksoup you can drag the fields on the „Manage fields“ page to custom positions, and save the form. The new order is what content editors will see when they add or edit a content item, but the full display for visitors shouldn’t be affected by it.

Only exception: When you create the content type and add some fields, at first their order will be the same at both places. But when you change the field order later, it should only be applied to / for the place you are changing, without affecting other places.

Maybe I misunderstand what you‘re trying to achieve? I’m currently on a vacation, so can’t explain better at the moment, sorry!

Mon, Jul 31, 2023 - 9:24am by leeksoup

@Olafski - I think I misunderstood your first reply and was looking at "manage displays" tab instead of "manage fields." I get it now, and yes, it does fix my issue.

Thank you very much!