It's possible this is just one of those, "I'm really tired so..." problems, but I just spent 15 minutes trying to figure out why userreference wasn't showing up as a widget type. Turns out it's dependent on optionwidges.module. Here's a patch to point this out to bleary-eyed people. :P

CommentFileSizeAuthor
#1 req_option.patch1.7 KBwebchick
user_option.patch796 byteswebchick

Comments

webchick’s picture

Title: userreference sould indicate it requires optionwidgets » user/node ref sould indicate they require optionwidgets
StatusFileSize
new1.7 KB

Actually, presumably this holds true for nodereference as well.

yched’s picture

Nodereference does _not_ require optionwidget.
And AFAIK, neither does userreference...

webchick’s picture

yched: An exercise. ;)

Enable the content module, the text module, and the userreference module, but NOT the optionwidgets module. Create a new content type. Attempt to add a field. "Text" will be the only widget available. This doesn't change until you enable the optionwidgets module.

webchick’s picture

Also, just confirmed this to be the case in nodereference module as well.

yched’s picture

I just did what you described and I can in fact create a [node|user]reference field with optionwidgets disabled. I really don't think there's a dependency here, and I don't see why there should be one.

I noticed something strange along the way, though : after enabling or disabling a field module, I have to empty my cache in order to have the field creation page show the correct available fields.
So I suggest maybe you try and disable optionwidgets, enable [node|user]reference, _empty your cache_ and see if you get the correct fields.

If so, I guess we have found a bug...

webchick’s picture

Title: user/node ref sould indicate they require optionwidgets » Cache should be cleared when enabling new fields
Status: Needs review » Active

@yched: Yep you're right! Clearing the cache makes the fields show up. Sorry for the misdirection; I thought I tried that as a troubleshooting step but obviously not. :)

Changing title and status appropriately.

dodorama’s picture

If so, I guess we have found a bug...

Hey! I've been the first one to found this bug :)

webchick’s picture

Status: Active » Closed (duplicate)

Oops. Apologies, didn't see it. :)

webchick’s picture

Status: Closed (duplicate) » Active

And also didn't see that you marked yours a dupe. ;)

Just call me web-"extra observant"-chick! ;)

yched’s picture

Status: Active » Closed (duplicate)

In fact, I guess the original report by dodazzi is probably clearer, and less crufted :-)

dodorama’s picture

I thought this one was clearer :)
Happy to know that sometimes my english works :)