Adding a field

I'm sorry but I cannot understand your post, you're not being clear
Please provide a clear description of
- exact actions you are doing
- what you expect
- what happens instead

+ this looks more like a feature request to me, we'll turn that back into a bug if it appears there is one.

1) Pick the field set it up. When I set that field up. It populates the widget field for the new field section with the widget types for the existing field. There is no option to leave the widget field blank. Therefore when I try to add the existing field it gives me the error that the new field section is not filled out correctly.

Sorry, this still doesn't make any sense to me. English language issue, I think + you are still being vague.
Say where you click, what you choose and where, what *exact* error message you get.

edit : not a language problem, you're in the States. You need to make a minimal effort and post clear reports. That's the minimal job you can do if you want to get help.

If you have a field selected, you must also have a widget selected. If you de-select a field and go back to no field, the widget selection will also go back to none selected. That all works exactly as expected.

Why would you want to be able to have a field selected without a widget? You can't do anything with it anyway. You certainly can't save it that way.

Double check the very latest -dev code to see if you still have a problem there, I can share fields with no problem at all and everything behaves as it should.

Nothing like this is happening on an installation with just core CCK fields, I suspect you have some other module interfering somehow, either a contrib CCK field that isn't working right in the new UI or a non-CCK module that has javascript that is getting in the way. What other modules do you have enabled, including CCK contrib modules? What kind of field is the shared field that's creating problems? Do you have the very latest -dev version of all CCK modules?

I also have this same problem. I installed the newest CCK build today. When I built the fields for my first content type everything worked correctly. The problem occurs when you attempt to build fields for the second content type and you already have existing fields from first content type.

When you pick the "type of data to store" in the new field, the last box changes to "Select List" and gives you the field options as it should. However, the last box in the existing field portion also changes to "Select List" when it should remain as "Select widget" so that drupal doesnt think youre trying to add an existing field at the same time.

So changing the data type changes the widget box for both the new and existing fields. The last box for both the new field and old field are somehow linked.

Modules other than core that I have enabled: CCK, Views, Pathauto, FCKeditor, Image, and Date

I also tried disabling all modules except the "Core-required", and the Content and Text modules in CCK (turned all others in CCK off). The problem still occurs.

after installing cck-6.x-2.0-rc8 I can't add a new field to my existing content types:

this is a description of what I do/did:

1) admin > content management > content type > add content type
2) i fill out the fields necessary
name: test_cck
type: test_cck
save content type

3) after saving I get redirected to: mysite.com/admin/content/types
- click on 'Manage fields' of my newly created "test_cck" content type
- I get redirected to: mysite.com/admin/content/node-type/test-cck/fields

I fill out the necessary fields for the new field

New filed: new_field
field_: new_field
select a field type: text
form element: textfield
save
save field settings

so far so good...

!!! now this is the part when my troubles start

4) I go back to the list of my content types: mysite.com/admin/content/types
I select "add content type"

5) i fill out the fields necessary to create a new content type
name: test2_cck
type: test2_cck
save content type

6) now i'm back on the page that lists all my content types: mysite.com/admin/content/types

I select 'manage fields' of my newly created "test2_cck" content type

7) now... under "Add" ... I see three rows with blank fields:

New field
Existing field
New group

I'm not interested in using an existing field (e.g. new_field that I created under test_cck content type).
I want a brand new field.

8) i fill out the necessary field in the "New field" row:
label: test2_field
field_:test2_field
select a field type: text
form element: textfield

9) I click "save"

now I get the following message:

* Add existing field: you need to provide a label.
* Add existing field: you need to select a field.

(In the "Existing field" row... the fields "label" and "select an existing field" are highlighted in red)

I can't get rid of the message and I don't know how to add a brand new field.

I know this is not a conflict with other modules since I'm using a fresh install of drupal 6.4 in my local environment (xampp) and I only use the core modules now (no additional modules are installed).

I hope I was clear to describe my problem. (a screen shot provided)

Thank you in advanced for any help with this issue.

I can't replicate this problem at all. I can add new content types and add fields to them with no trouble at all.

I can't think of any reason why you would have this problem if you don't have any other modules enabled (which would have been my first question).

I'll leave this open in case anyone else is having this problem and can provide more ideas.

The only other thing I can think of is to try a different browser just in case it's some kind of javascript issue.

Dropped in the RC8 today.

Problems with adding a new field OR an existing field.

The issue is that when you select from the first select list under the heading "type" it dynamically effects both select lists for new AND existing fields.

BIG FAT BUG :)

I just noticed that I can add a new field but only in case I add an existing field as well.

I hope this info will be helpful. I've attached another screen shot of more or less the same thing.
But I swear, I'm not making this stuff up.

Thanks in advance for any feedback or help.

Definitely looks like a JS issue: Looks like the jquery selector that is supposed to select the relevant "widget" dropdown selector for either "add new field" or "add existing field" in fact selects both of them...

Something around :

this.targetSelect = $('.content-widget-type-select', $(this).parents('tr'));

in content.js (2 occurrences, one for each "add [new|existing] field" row)

I'm not currently where I can test or debug this, but I know for sure that I was not seeing this on my setup, and Karen doesn't either.

Could you guys specify which browser / OS you're using ?

Same problem. The form expects you to add both an existing field AND a new field and won't allow you to add an existing field without also filling in new field info as well.

This is a huge bug.

I'm using Ubuntu Hardy Heron/Firefox.

Just tested in IE7. Same issue- refuses to accept only one entry- expects to have both a new field and an existing field or returns an error.

I'm using vista home premium...

I've tested the issue in the following browsers:

Firefox 3.0.3
Safari 3.1.2 (525.21)
Explorer: 7.0.6001

The problem persists in all of them.

Thanks very much for your help.

Same problem
XP + IE7

Impossible to create a field, this requires to also add an existing field
The widget selection for the form element of the 2 (new+ existing) fields combines both offering for the different data types that need to be selected.
For example, selecting a node reference for the new and a text element for the other gives the same -inconsistent - merged choice:
Select list, Check boxes, Single On/Off checkbox, text field, Text area

Looks like a cat walked on a developer's keyboard

Same problem :(

I cannot replicate the problem using IE XP with either FF3 or IE7, both work just fine for me.

I haven't got a clue what to try, and since I can't replicate the problem, I can't test any possible fixes. And I don't know enough javascript to have any idea what to try anyway.

Yched, if you have any ideas that people experiencing this could test, I guess that's the only way to figure this out.

Same problem here. I just installed the latest CCK and View today.
When I hit save, it won't allow me add a new field to an existing content type. instead it requires me do something on existing field which doesn't make any sense.
I am using vista basic+firefox, but I believe it's irrelevant to the problem.
Thanks for sharing...

this is a serious issue with RC8 - I had to roll back to RC7 and now the issue is gone.

Strange, I have just upgraded to RC8, and withouth any errors I can:
- add just a new field to an existing content type;
- add an existing field to an existing content type.
(using Ubuntu, FF 3.03)

People experiencing this could try the following
- make sure you use Firefox with firebug
- edit content.js as specified below:

  // 'Field type' select updates its 'Widget' select.
  $('#content-field-overview .content-field-type-select', context).each(function() {
  this.targetSelect = $('.content-widget-type-select', $(this).parents('tr'));
  // *** add the following line: ***
  console.log('new field - target:', this.targetSelect); 

  // (...)

  // 'Existing field' select updates its 'Widget' select and 'Label' textfield.
  $('#content-field-overview .content-field-select', context).each(function() {
  this.targetSelect = $('.content-widget-type-select', $(this).parents('tr'));
  // *** add the following line: ***
  console.log('existing field - target:', this.targetSelect); 

  // (...)

Then, reload the 'admin field' page (CTRL-F5, to be sure to grab the updated JS file), check the Firebug console, and report the results here. The normal behavior would be :
new field - target: (a reference to the widget selector for the 'add new field' row)
existing field - target: (a reference to the widget selector for the 'add existing field' row)

People seeing the bug will probably get different results, which I'd be interested to know...

[edit : fixed the code as mentioned by claudiu.cristea in #29]

same problem. trying to add an existing field results in the errors in pink, because it also tries to add a new field.

tried the above code in #25, it worked, however, all the widget form elements come up (text, image, amazon, emfield....) regardless of what's in the field (add or select) box.

using firefox 3

The point of the code in #25 is not to fix the problem but to debug it. Yched is asking someone to use firebug along with that code and report back what the firebug messages say.

Same behavior... but is gone after trying #25... Seems that Ctrl+F5 fixed the issue... :) The old content.js was in the browser cache.

Is not gone... Sorry for the false info... In fact, the was not fired up because the code provided at #25 has a small syntax error. A quote (') was misses in the second console.log().

I tried #25 and I got in firebug:

new field - target: Object length=5
existing field - target: Object length=5

See first attachment.

Click on Object length=5 it take me to the DOM tab. See 2nd attachment.

New infos... With the same platform (OS/browser - Win/Firefox 3.0.3) I tested CCK 6.x-2.0-rc8 on other site. There is working well. Weird, no?

For this reason I think that this is NOT a cross-browser issue. Results from firebug on a "RC8 working site"

new field - target: Object length=1
existing field - target: Object length=1

See screenshot #1

And to the DOM tab we have only a '0' object as in attachment #2....

@claudiu.cristea : thanks for the info.
I'd like to take a look at your 'broken' site, if it's online somewhere.
Can you create an account with 'administer content' and 'administer site configuration' permissions and send me the url and credentials through my contact form ?

Note : same request for anyone seeing this bug on a site accessible online, in case claudiu.cristea's site is only local. Just be sure to modify content.js as specified in #25 so that I can have some debug information.

@yched, what is the reason for the difference between:

$('#content-field-overview .content-field-type-select', context).each(function() {

and

$('#content-field-overview .content-field-select', context).each(function() {

I see you have different class names for the field selectors but use the same class name for the widget selectors, could that be the problem?

More thinking out loud: What will happen if we have a site where some field or widget types are missing due to upgrade problems? Or if the field or widget lists are incomplete because of caching of outdated values?

I'd be interested to know if the people reporting problems have missing field info in their databases. You can scan the tables content_node_field and content_node_field_instance. If you see any items there that are missing module names or are not marked as active, but you are editing a content type that uses those fields, that could be a factor.

Also, be sure to clear cache_content() to be sure the field and widget type lists are updated.

And try using the Manage fields screen on different content types, including content types that don't have any fields, to see if that has any affect.

Same behaviour trying to add a field to any content type, even then no existing custom fields are there.

As soon as I select the type of data, the "Select a widget" empty combo lists of both New and Existing form zones fill up with all available widgets, defaulting to the first item "Select list "

This definitely has something to do with the rc8 release, everything was fine before

I'm having the same problem as claudiu.cristea on FF3/Mac and Safari/Mac with the same result with the debug code

new field - target: Object length=3
existing field - target: Object length=3

I'm only working locally and about to head out the door so I can't set up a public site right now. Maybe later tonight.

This definitely has something to do with the rc8 release, everything was fine before

Er, yes, the rc8 release is when this new UI was added. Earlier releases had the old 'Manage Fields' screen. This issue is all about getting the new UI to work correctly in all situations.

yched & KarenS,

I've sent you both private messages with info on a live site with a user name and password.

I'm having the same issue everything is talking about. Hope this helps!

Karen,

I have tried all three of your suggestions in #33 and they had no affect on the issue.

Please let me know if there is anything else I can try to help the process along.

I have this problem too.

When I select the "Type of Data to Store" the "Form Element to Edit This Field" changes for both the "New Field" that I am trying to create and the "Existing Field" that I do not touch, care about, and seems to be causing the error, "* Add existing field: you need to provide a label.
* Add existing field: you need to select a field."

Hi everyone,
I encountered the identical issue as described above. I noticed that when I selected an item from the "Type of data to store" list, it modified both of the widgets lists for both the New and Existing field lines. Clearly, the event should only be modifying the widget list in its current line.

It also appears to be a theme-related issue. I encountered the issue using the "Pushbutton" theme. I know Garland is pretty safe for the admin section, so I switched it to Garland... and the issue went away! To troubleshoot, I tested the themes that come out of the box with Drupal 6.4 and this bug also appears to affect Marvin, Chameleon, and Bluemarine. It does not affect Minnelli and Garland.

I spend about 20 minutes looking into what theme-related element might be causing the problem, but I have to admit, I am not a guru with Drupal themes. Perhaps someone else can pick up the ball from here. :-) Hopefully my contribution at least gives people a decent workaround (use Garland or Minnelli) and it gives the module developer a sure-fire way to reproduce (use Pushbutton, Marvin, Chameleon, or Bluemarine).

Brian

@Brian294 : thanks for the followup. This is probably a crucial point, but I'm not too sure what this means yet. Investigating on the sample site provided by dheffron.

To all people seeing this bug : switch to garland as an admin theme as a temporary workaround
(admin/settings/admin)

Bingo!

I was using the simplistic Chameleon as the administrative theme.
Using the site theme Garland instead solved the problem

OK, found it. Problem is with table-based layouts. $(this).parents('tr')) also returns the top-level rows from the layout, and breaks the logic.

This should be fixed by the following changes in content.js (I'm on holiday and writing this from a cybercafe in Portugal :-p, which makes it uneasy for me to roll a proper patch)

- this.targetSelect = $('.content-widget-type-select', $(this).parents('tr'));
+ this.targetSelect = $('.content-widget-type-select', $(this).parents('tr').eq(0));

(...)

- this.targetSelect = $('.content-widget-type-select', $(this).parents('tr'));
- this.targetTextfield = $('.content-label-textfield', $(this).parents('tr'));
+ this.targetSelect = $('.content-widget-type-select', $(this).parents('tr').eq(0));
+ this.targetTextfield = $('.content-label-textfield', $(this).parents('tr').eq(0));

This could probably be refactored / optimized a little, but we can see this later.

Side note : I'd welcome if someone could test the above fix in different browsers (FF, IE, Safari, Chrome...). As usual, be sure to refresh browser caches (usually CTRL-F5) after updating content.js

Moving from BlueMarine to Garland as admin theme also made the issue go away. - John

I switched to Bluemarine and could replicate the problem. I then made this change, used CTL-F5, and it fixed it in Windows XP/FF3. Also tested Windows XP/IE7 and could recreate the bug without the fix and the change fixed it.

I'm leaving this marked CNR so others can confirm that this is working, but it looks good to me.

Great detective work! It never occured to me to try a different theme.

Here the change is as a patch. If we get a couple confirmations that it's working, I'll commit it.

The patch solved the problem for me.

Thanks for all your hard work!

Confirming that the patch in #47 fixed the problem in the Wabi theme too. :-) FF3/Mac

OK, fix committed to -dev. I'll roll a new rc9 with this change shortly.

Thanks to everyone for getting this resolved!

and thanks to ctmiller for insisting in posts #0 to #8 :-)