cheesegrits
Support Gopher
I'm not 100% sure what you mean, but it rendered the same way as it does now in the test site.
BR,
martin
Rob and I are just confused about how this ever worked.
I know its technically possible to set a group up this way, but as far as we know, it would never have worked "right", as it would require "nesting" of groups.
You have a repeat join group, which has a one-to-one to another join group. So in theory that should render a separate copy of the one-to-one for each instance of the repeat, as they could all point to a different row. But in practise, it won't. It'll just render a single copy of that one-to-one joined group. And even in 3.0 (I just looked at the code) the submission procressing wouldn't have handled it "properly", and as far as I can tell, each instance of the repeated join would have wound up being saved with the same one-to-one join FK, i.e. pointing to just that one instance of the one-to-one group.
-- hugh