Field dependency on field within repeater based on field outside of repeater?

[999design]

Hello

I've just hit a scenario where I have a particular field (within a repeater) that I'd like to set up a field dependency for, so that it shows only if an option from a page reference field (that sits outside of the repeater) is selected.

Simply using the fieldname=value approach doesn't seem to work. I'm assuming that this is because the field in question is inside a repeater and can't access information from the fields that sit outside of it?

I tried using the following without luck. To be honest I was just guessing at this point.

• page.fieldname=value
• forpage.fieldname=value

There's other ways that I can set up my template, but I was just curious if there was missing a trick somewhere?

[MarkE]

$page->getForPage()->fieldname ?

[999design]

@MarkE Thanks

I think that would work within a frontend template but I don't think I can write it like that in the "Show if" dependency field settings. It seems a little bit more limited.

[MarkE]

37 minutes ago, 999design said:

@MarkE Thanks

I think that would work within a frontend template but I don't think I can write it like that in the "Show if" dependency field settings. It seems a little bit more limited.

There may be some ideas here 

 

[adrian]

@999design - I just found myself wanting this exact functionality. The easiest way for now seems to be Robin's https://processwire.com/modules/custom-inputfield-dependencies/. The custom PHP option does the trick with something like this:

$p = $page->getForPage();
if($p->field_name == 'value') return true;  
return false;

The caveat is that the conditions provided by this module are only applied on page load, not instantly via JS like the PW core feature. But definitely better than nothing for now.

[adrian]

I am thinking that this might actually be an easy fix in the PW core.

I just did a quick edit, replacing this line: https://github.com/processwire/processwire/blob/cc43f8e67600fc3ad73ea3ac095d67f166c5ca96/wire/templates-admin/scripts/inputfields.js#L1483 with:

var field = match[1];
if(field.indexOf('forpage.') == 0) {
	field = field.replace('forpage.', '').replace(/\_repeater\d+/g, '');
}

This lets me use: 

forpage.fieldname=value 

as described by @999design in the OP.

@ryan - can you see any problems with this approach? Maybe I've overlooked something?

Note that this approach currently won't work with AJAX loaded repeater items.

[adrian]

PR for the above change submitted: https://github.com/processwire/processwire/pull/255 although I expect Ryan might have a more complete solution, but at least that will hopefully get this issue on his radar.

[adrian]

This functionality is now available in 3.0.236 and now seems to work with AJAX loaded repeaters as well.

[elabx]

Hi! I've made an experiment to support nested repeaters updating a little bit the previous update. Not sure how common this is, but I have a lot of scenarios where I have at least one extra level of repeaters, and I'd benefit from this dependency update to change the fields of nested repeaters.

https://github.com/elabx/processwire/pull/1/commits/bdf7e4fc21961712abf7ee3e1e6910de32683725

Not sure if you are in the possibility of testing this @adrian? Thanks!