We are transitioning over to a new forum platform. Please post new issues there. Existing threads will be dealt with here unless you choose to move them over. Visit the new forum
Separating perch field groups in a runway collection template out into separate...
Is this possible? I find that when I have to make a small text change to a collection item with a lot images (i.e. a gallery), Perch can be very slow to update on save, presumably because it's gotta check through all the images (& all the various sizes required for responsive images).
It'd be great if we could separate the images (or the new field groups) onto a separate (sub)edit page to speed up text only updates. I realise this might be possible by creating multiple collections then using associations to link them up but it doesn't seem like the most intuitive approach from a user perspective, and seems considerably more complex on the coding / dev side.
Perhaps something like a 'separate' attribute on the Perch field group which could create a link to a sub-edit page for that group, i.e. ...
<perch:group label="Gallery images" separate> ... </perch:group>
Are there any other approaches to improving this?
Want to reply to this thread?Login with Perch