Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
field_ui.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Sep 2009 at 13:32 UTC
Updated:
29 Jul 2014 at 18:27 UTC
Jump to comment: Most recent file
Comments
Comment #1
aspilicious commentedStill an issue?
How can I reproduce?
I read this thing 3 times, and i still don't understand...
Comment #2
bradweikel commentedAdding usability tag, but I can't find a repro path for this because I can't find a field type without settings. Maybe a non-issue now?
Comment #3
yoroy commentedOriginal report is very hard to understand (I couldn't).
Comment #4
Everett Zufelt commentedWhen adding a field to a entity using the UI (e.g. content type -> manage fields) you:
1. Add the field and click save
2. Are taken to the settings page for the field
3. Are taken to the settings page for the field instance.
Some fields (likely none in Core) have field instance settings, but no field settings. So, in step 2 you are basically taken to a field settings page w/ no controls other than Save. Can't think of a contrib field where this happens, but I am certain I have seen this (perhaps link.module is where I saw it).
Comment #5
Everett Zufelt commentedJust confirmed that link.module does not implement hook_field_settings_form(), as it declares no field settings, only field instance settings.
Bypassing the field settings form for fields that don't implement hook_field_settings_form() seems like a good idea, but does provide inconsistent behavior when adding new fields.
Comment #6
JvE commentedWhen drupal core is installed with the "minimal" profile the Long text fields also have no settings.
Attached patch makes a few changes to the form:

Comment #8
JvE commentedAdded extra newline at end of file to see if it applies better that way.
Comment #9
valthebaldWhat's the point showing the form with only option to click 'Save'? Can we just skip this step and proceed to the instance settings form?
Comment #10
swentel commentedLet's tackle this at #552604: Adding new fields leads to a confusing "Field settings" form