Closed (fixed)
Project:
Link
Version:
7.x-1.0-alpha3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Apr 2011 at 18:46 UTC
Updated:
24 Sep 2011 at 20:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
burki commentedThis seems to be a problem in the
link_field_processfunction. The settings array that is taken from form_state is not initialized.Proposal for a fix:
Comment #2
jcfiala commentedI'm not able to reproduce - I created a node type, added a link field and selected the 'no title' option - I'm seeing no title field on the form. Can you give me some more information about the field that could help me reproduce your problem?
Comment #3
rwohlebI'm getting this also. I am seeing it when I attach a link field to a profile2 content type. It appears it's due to how profile2 merges it's attached fields into profile forms. As a result, you can't guarantee a specific structure for $form_state['field'].
Based on the description of field_widget_instance() on api.d.o it looks like that's the proper way to get to field instance settings anyways. The change in #1 works for me.
Comment #4
jcfiala commentedHm. I'll have to agree, it does look like I should be using field_widget_instance. Thank you for pointing that out.
I've pushed the change into git.
Comment #6
Niklas Fiekas commentedSubscribe.
Related issue: #1252274: Instance settings aren't saved for link fields attached to the user entity type
Comment #7
meabbasi commentedSubscribing.
Comment #8
dqdPlease read project page:
here a snapshot of working 7.x-1.x-dev below