Closed (fixed)
Project:
Relation Select
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
13 Jun 2012 at 14:55 UTC
Updated:
25 Aug 2012 at 22:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
gilles_c commentedIn relation_select.module, function relation_select_field_widget_multiple_form.
There is condition to prevent to show the add-more button if there is no field. If I remove it, the button appear but I need to push the add button 2 times, the first relation don't work, but the second is ok.
Comment #2
steveoliver commentedErrance,
I also encountered the issue where Relation Select fields were not showing up on the node edit page when no relation was previously set (when the field previously WAS showing up), along with the following error thrown:
I've been doing a bunch of work with the fields and with patching the relation_select module, so I figured I messed something up.
I removed and added my Relation Select fields back, and they began to appear as expected--with or without relations selected in the field.
Alternatively, or first, you could try submitting the edit page for that Relation Select field, make sure you have a relation and view selected -- they may have changed/been removed in your development.
Comment #3
steveoliver commentedThe behavior I'm still encountering is:
if relation select field settings: Number of values = Unlimited, no field appear.
else if relation select field settings Number of values = 1, one field appears.
else if relation select field settings Number of values = any other number (n), n-1 fields appear.
In other words: Unlimited = none; 1 = 1; N = N-1 fields.
Errance,
Can you confirm any similar behavior with field settings?
Comment #4
gilles_c commentedYou're right.
The field appears if I select a number.
It's same as you say : Unlimited = none; 1 = 1; N = N-1 fields.
Comment #5
gilles_c commentedI made an update today with the last dev version & nothing change :(
I hope to find some time to have a look to this bug but this month it's hard.
Comment #6
gilles_c commentedOk, I think I find the problem. When the number of value is unlimited, the max is 0. We need to set it to 1, so we always have a field.
I try to make a patch.
Comment #7
steveoliver commentedThanks, Errance.
I haven't dug into it yet, but I don't think this patch approaches the problem. It seems to hack at the effects. I'll be giving Relation Select issues some more time next week. In the meantime, maybe see how the $max var is being used. Have you stepped through this code with a debugger?
Comment #8
jpstrikesback commentedAlso seeing this cardinality issue, trying to relate terms to each other (the return of synonyms, yaaaay)
Comment #9
steveoliver commentedFixed in 3ccc29e. Thanks, Errance.
Comment #10
jpstrikesback commentedWorking now. Thanks for your work here, this is great!
Comment #11
steveoliver commentedYou're welcome. This is a cool module.