Not seeing all the the components to create a new conditional rule

I am having the same issue. I've created a really long web form (80+ elements) and I am no longer able to see the questions after the 70th or so item.

I'm having the same issue using Webform Conditional 6.x-1.0-rc2 with Webform 6.x-3.14. The list cuts off after the first 50 form components.

Figured it out... Breaking up the nested fieldsets into pages seemed to resolve this problem.

Boosting the signal on this one, since the previous revision of the Issue Summary might have given the false impression that the issue was resolved.

I'm only seeing the first few fields on the second page of a multi step form. Just seeing the first 4 fields on the second page. Subsequent pages exhibit similar behaviour, some fields are available some aren't. These are all select fields all set up in the same way, so not sure what the problem is.

Same Issue. I only see the first four or so items after a page break. However fields in each subsequent page break shows all fields in all previous pages but again only the first four or in it's own. All options appear when adding a new field but not after you edit it.

Attached are examples from the last field in each page break. You can see it randomly cuts off the available options.

I had the same issue, still have it but i think i found a clue about this.
Checking the code found that the module loads the right components to display in the drop down, but then they never get added, this is the line that does it (line 23 of webform_conditional.module):

$form['conditional']['extra']['conditional_component']['#options'] = $form['conditional']['extra']['conditional_component']['#options'] + $triggerComponents;

$triggerComponents is correctly loaded with the components but they are not being added to ['#options'].
In my case, I have several page breaks, all with the same text for the next button, and this is what makes the assignation fail as the text is used as the key for the array of the page, so trying to add it to the ['#options'] fails without notice.
Changing the assignation I got to see the right components, but with the addition of a number before the page break component in the drop down, I'm still not sure if it actually works like this, here is the code:

$form['conditional']['extra']['conditional_component']['#options'][] = $triggerComponents;

Hope this helps to figure this out, its a great module.

Edit: Try to check that all your page break have different text to see if that shows the missing components, it did for me without code changes, but all the "Next" buttons may get different text, "Next1", "Next." or so.

Can someone export a webform that is having this problem using node export ? You can either attached output as text file to this issue or contact me via my contact form. This will make testing much faster.
Thanks

Yeah, here is an export of my webform. Thanks

Hmmm has anyone made any progress on this? I only have one page break, and it looks like the list of available components to build a conditional rule on the second page ceases at an arbitrary point. I will be happy to provide an export of my form if that would help.

Don't know if this sheds any light, but I am trying to build a conditional off a conditional.

So:

• If you select A on page 1
• Option Z appears on page 2
• If you select Z on page 2
• Option Zx appears on the same page. Option Zx is mandatory.

The problem being that when I attempt to make option Zx's visibility conditional on Option Z, Option Z does not appear in my list of components to build the rule. There are a bunch of other components to choose from, but like I said, the list of options seems to end arbitrarily.

Are you aware that Webform Conditional is limited to Select type componants at the moment ?
This means that the dropdown will show you all "contionnable" components before most recent pagebreak PLUS all select components on same page as the component you are editing.
Well at leadt that's what is written on 7.x version : "Currently fields and fieldset can be dependent on Select components."

@David Stosik: I wasn't aware of that, but in my case at least I don't think that's the issue. After the first 50 components, even select components were not showing up in the dropdown.

@David Stosik, yes, that's how I understand the module to work. However, I am trying to conditionally show a field that is based off a select component on the same page, but the select component is not appearing in the components list. Attached image may clarify my problem.

This is probably having b/c of this issue in Webform #1403586: Conditional Rules component list is incorrect when using components that don't support conditional where extra components are put into this selectbox.

The patch I submitted was for D7 but it applies to D6 also.

Repasting original summary