Closed (duplicate)
Project:
References
Version:
7.x-2.x-dev
Component:
Code: user_reference
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 May 2011 at 15:55 UTC
Updated:
11 Dec 2011 at 20:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
cpelham commentedjust installed 7.x-2.x dev and got this error
Comment #2
quicksketchThere is no 7.x-2.x dev. I'm assuming you mean 7.x-1.x dev? Right now dev is identical to 1.9 so there won't be any difference in behavior between dev and the current stable version.
Comment #3
wmelon commentedI also get this error. Drupal 7, with references 7.x-2.x-dev (2011-May-03) and node reference URL widget 7.x-1.10
Comment #4
gfxguru commentedsame here
Comment #5
andrebonfanti commentedsubscribe (after upgrade)
Comment #6
yched commentedI'm not sure this is the cause of this very bug, but I see that nodereference_url_build_link() uses calls _node_reference_potential_references(), which signature was just changed by #945004: [release blocker] Missing views-mode for picking userreference and nodereference :-/.
Sorry about that, I wasn't aware that some external code was relying on the function.
I'll be rolling a beta release for references shortly, it should then be "easier" to fix nodereference_url accordingly point to an official references tag.
Comment #7
boobaaSame issue here, even with user references (internal ref. #949):
Notice: Undefined index: args in _user_reference_view_settings_validate() (line 167 of …/references/user_reference/user_reference.module).Comment #8
yched commentedSee #1149600-2: Undefined index error
Comment #9
yched commentedI took my remark in #6 off to #1150004: _node_reference_potential_references() signature changed in node_ref.module
Comment #10
Stefan Haas commentedsubscribe
Comment #11
icefeet commentedsubscribe, same issue, even after removing URL Ref Widget
Comment #12
inversed commentedsubscribe
Comment #13
davidsanger commentedsubscribe
Comment #14
TripX commentedLine 161 error happens here too on first creation of a reference field
Comment #15
Adam S commentedsubscribing
Comment #16
dafederI believe this is miscategorized. I am getting this and do not have Nodereference URL widget installed.
Comment #17
dafederBelieve this is a duplicate of #1149600: Undefined index error
Comment #18
Todd Young commentedMe too - using USER reference as stated in #7 above:
Notice: Undefined index: args in _user_reference_view_settings_validate() (line 169 of /XXX/YYY/ZZZ/sites/all/modules/references/user_reference/user_reference.module).
Comment #19
Liaz commentedsame here
Comment #20
TripX commentedlatest dev fixed the problem at my side... have you updated, liaz, adam,..?
Comment #21
puya commentedDo you mean the latest dev of the References module? I don't see any dev releases on the url node ref.
Comment #22
mrmeech commentedSame error here too using node reference...
Comment #23
drugget commentedSubscribing.
Same error when using Drupal 7.2 + 'Node reference' (warning appears after field creation).
Comment #24
rosemeria commentedSubscribing.
Same error when using Drupal 7.2 + 'Node reference' (warning appears after field creation).
Comment #25
CrashNet commentedsub
Comment #26
apermuy commentedSame error using Drupal 7.2 + Node reference 7.x-2.0-beta3 ...
Comment #27
dafederFolks, please try latest dev release of References, so far no evidence that this is anything other than #1149600: Undefined index error.
Comment #28
rfayI guess I don't think it's a dup.
This occurred for me when creating a node reference field, and I didn't add a view or an argument.
Here's a patch (for node reference only) that seems to deal with that case.
Comment #29
Adam S commentedI updated to the most recent References release and this error disappeared.
Comment #30
dafederrfay: looks like the exact same issue to me, and your patch is very similar to mine, which got rejected in favor of a better solution by @yched. Are you using the latest dev?
Also, still no evidence that this has anything to do with the nodereference_url module.
Comment #31
jon betts commentedI updated to the most recent References release and this error disappeared for me as well.
Comment #32
backwardgraphics commentedIn reference to comment #7 and #18 user_reference should be fixed with this patch. This is my first patch so my apologies if this doesn't apply right.
Comment #33
carn1x commentedsubscribe (using node_reference-7.x-2.0-beta3)
Comment #34
jrdixey commentedSame error, but node_reference rather than user_reference. We are also using node_reference-7.x-2.0-beta3.
Comment #35
gumanist commentedIt is fixed in dev
Comment #36
stephenrobinson commentedI get this when saving a node reference when building content types
Comment #37
Polyspiral commentedYep the Dev worked for me
Comment #38
hip commentedSubscribe.
Me too (#36): I get this when saving a node reference when building content types
after a fresh install
Comment #39
alonk27 commentedSubscribe.
Comment #40
mkaramizrakli commented+1 (fresh install with the latest version)
Comment #41
m.sant commentedSame here with a fresh install and 7.x-2.0-beta3
Comment #42
runeasgar commentedMoving my comment to another ticket, since it seems to be another issue with WOSD + content type edits when node ref is used.
Comment #43
zeta1600 commentedsubscribing...
Comment #44
adamjuran commentedsub
Comment #45
Jean Gionet commentedsub
Comment #46
mtiftSubscribing
Comment #47
aidanlis commentedSubscribe
Comment #48
jdufaur commentedSubscribe
Comment #49
Anonymous (not verified) commentedsubscribe
Comment #50
leoklein commentedsubscribe
Comment #51
stopshinal commentedsubscribe
Comment #52
bvanmeurs commentedSubscribe. Please fix.
Comment #53
Rhodungeon commentedSubscribe
Comment #54
Courtney.B commentedSubscribing.
Comment #55
mike27 commentedSubscribing
Comment #56
mrpauldriver commentedsub
question? Is Corresponding node references module causing this?
Comment #57
drjonez commentedsub
Comment #58
ppc.coder commentedI got this error with the 7.x-2.0-beta3 release. Tried the 7.x-2.x-dev and no error.
Comment #59
jakew commentedI'm getting this in 7.x-2.0-beta3, except on line 169.
Comment #60
redhoodie commentedSubscribe
Comment #61
rick hood commentedConfirming same for me: "I got this error with the 7.x-2.0-beta3 release. Tried the 7.x-2.x-dev and no error."
Comment #62
dTr303 commentedConfirming same for me: "I got this error with the 7.x-2.0-beta3 release. Tried the 7.x-2.x-dev and no error."
I had the same issue installing the dev version instead of the beta version solves the problem
Comment #63
modulist commentedConfirming same for me: "I got this error with the 7.x-2.0-beta3 release. Tried the 7.x-2.x-dev and no error."
Comment #64
gumanist commentedThis patch is for those ones who don't want to use dev version but wish have this issue fixed. As it mentioned above dev version haven't this issue.
Comment #65
hip commentedsubs
Comment #66
mausolos commentedHappens with me, too, and on two completely different D7 sites. Has anyone noticed if this only happens when the content type you are referencing happens to not have any nodes, yet?
Comment #67
samw commentedYes, it's the same for me that the error message disappears once a node of that content type has been created.