martin

You don't need to use the $key. foreach($p->product_images as $image) { $productImages[] = $image; } How were you adding them to the WireArray in the first place?

When you create the fieldset, it creates two fields. One is (fieldsetname) and one is (fieldsetname)_END. You put both of those in the template.

Schema changes should be extremely rare, but hard-coding the relationships still doesn't sit well with me. I suppose I'll have to go with prefixes on fields to decide their group.

The one problem I have now is that, although I can find out which fields are in each fieldset from the template, I don't have any direct link between the fields and the granule checkbox. Can I access the "show if" value in my PHP template?

I only have one template and will never need more. The app has a very specific requirement to fill. But yes, it's not perfect.

Yes, I thought as much. My backup plan was just to do it in the template for the parent page, selecting all children and find out details about their template and fieldgroups. This is an interesting option... and within 20 minutes I have it working like this. PW continues to impress! I've even managed to use the fieldsets in my PHP template to visually group and perform logic on those granules. Still needs some more testing but I think it'll work. Thank you

I'm wondering if there's a clean way I can implement a granular templates system for a web application I want to build. By granular templates, I mean that you can apply more than one template to a page, and all fields from all applied templates will be made available. I want something similar to this: House (page) implements Basic-House, Garage, Garden (templates) or Vehicle (page) implements Basic-Car, Diesel-Engine, Turbo-Engine, Four-Wheel-Drive (templates) The simple (already available) option is to use the page's children as the "granules", but it means having 2-4 children per item just to implement extra fields. I would rather some sort of inline solution. Thanks in advance for any suggestions.