Formatting Considerations [#860830]

Here are a few formatting requests for the node entry form. They're all fairly minor, so I'm lumping them into one ticket...

1) Allow the description text that accompanies each field to wrap to the width of the field or have the option to eliminate it altogether. In case where the description is long, it pushes the next field in the form farther to the right, and makes the form a little harder to use.

2) Have an option that allows an admin to choose whether fields display on a single line, or wrap to fit the vertical space (for non-liquid layouts, for example, or just cases where the user wants to see the whole node at once.)

3) Change wording on "Save all Nodes" button to "Create all nodes" (for consistency with the individual "Create" buttons on each node.)

4) Narrow the width of text and textarea fields (easy enough for an admin to do in CSS, but it would be nice if this was available by default.)

Comments

Comment #1

ergophobe commented 22 February 2011 at 00:29

Building on #2, I'd like to see the admin able to set which field are displayed and the user just gets a multi-add form, with no options (except perhaps being able to add more nodes, but user doesn't choose which fields are displayed on the form).

Comment #2

aron novak

Hungarian

Hungary, Budapest

commented 3 March 2011 at 08:27

seehawk: Can you help me with providing some CSS? Then i can include it to the module.
ergophobe: this is a pretty good idea! I will try to include it in the next release. So the admin can be able to generate pre-configured multi add pages for the users.

Comment #3

ergophobe commented 7 March 2011 at 04:24

That would be great. It gives the ability for an admin to create a much simpler interface for less techy users. I can think of a couple of use cases right now!

Comment #4

gintass commented 29 November 2011 at 20:28

+1
I also don't want to burden users with selecting which fields to display, although it seems that there is a permission issue. For example my users don't usually have access to fields like "Revission information", "publishing options" etc. For now I'm hiding them from users via CSS.