Multi-image field referenced to CMS template page

Design help CMS
1

On a CMS template page, is it possible to include multiple images from a multi-image field that is being referenced to the CMS in question, via a multi-reference field? For example, can the CMS template page from CMS collection “A” display all the images contained within the multi-image field in CMS collection “B”, that is referenced to CMS collection “A” via a multi-reference field?

If so, how do you construct this on the template page for CMS collection “A”?

If not, is there a finsweet tool that can accomplish this?

Here is my public share link: LINK
(how to access public share link)

1 Like
2

If-

  • A is whatever
  • B is
    • multi-image field
    • multi-ref field to A

Then on A’s collection page you;

  • Collection list bound to B
    • Filtered to where multi-ref field contains current A

Inside of that,

  • Collection list bound to B.multiimageField
    • Shows image

Then you’re dealing with a nested list, and you’ll be limited to 5 images.

If you want to show all 25 for each multi-image field, the easiest path is to use a nesting solution. There are several. FS CMS Nest is best known, but may be over-complex for your needs.

3

Thanks @memetican Can you elaborate on the statement above? I am not sure how to accomplish that.

4

What’s your readonly link?

5

https://preview.webflow.com/preview/cottagesouvenirs?utm_medium=preview_link&utm_source=designer&utm_content=cottagesouvenirs&preview=49ecbd468f038c28759074f7643bd0e0&pageId=673651d7037218ffde42da0f&itemId=6789af90741d1c0b6f644fd2&locale=en&workflow=preview

6

Hey Chris,

Decoding your original request;

  • A is Extant Homes :white_check_mark:
  • B is Published Designs :white_check_mark:
    • multi-image field(s) :white_check_mark:
      • Additional Design Sketches
      • Published Floor Plans
    • multi-ref field to A :x: ← I don’t see this?

Then on A’s collection page you;

  • Collection list bound to B :white_check_mark:
    • Filtered to where multi-ref field contains current A :x: ← can’t do without the ref connecting the collections

Inside of that,

  • Collection list bound to B.multiimageField :x:
    • Shows image

^ Don’t forget this part, it’s quite a different build and more complex. You’d need to familiarize yourself with the tools first or hire a pro.

Decide what exactly you’re wanting to build first and then you’ll know which direction to pursue.

7

Ok, I believe I have added the multireference connection to A from B, and then I also believe I have correctly filtered the initial collection list to be using the new connection with “contains” and “Current Extant Home”.

image
image241×185 3.48 KB

But now, when I attempt to place the nested collection list into the collection iten of the first collection list, I get the message that “Collection List wrapper elements cannot be nested into each other”. What am I doing wrong now?

8

https://preview.webflow.com/preview/cottagesouvenirs?utm_medium=preview_link&utm_source=designer&utm_content=cottagesouvenirs&preview=49ecbd468f038c28759074f7643bd0e0&pageId=673651d7037218ffde42da0f&itemId=679d8b50072642818482ee0a&locale=en&workflow=preview

9

The nested collection list goes inside of the item.
You’d then bind it to the multi-image field you want, and build out your gallery.

Remember it will only show 5 items of your 25, and you can only have one nested collection list per page.

image
image1920×991 169 KB

10

Michael,
Thanks so much, I got everything working as desired. I really appreciate all your help. If you reconnect to my site, you will see the final result.

I do have one last question regarding how this is all configured. Because of the bi-directional connections between the “Homes” collection and the “Designs” collection, this means that every time I add a home to the “Homes” collection, I need to specify the design within the “Homes” collection referenced field and then I also have to specify the home within the “Designs” collection referenced field. With thousands of homes soon to be added via import from CSV, this seems rather inefficient. Is there a better (more efficient) way to get the fields to associate with each other, like starting with the “Homes” collection, specifying the referenced “design” and therefore by doing that, the “home” automatically gets referenced appropriately within the “Design” collection?

11

Hey Chris, that’s awesome.

I did not see any A → B refs when I scanned through your previous setup at the start of our discussion. If that exists, you can reverse your setup. First collection list is bound to A’s multi-ref field, Inner collection list is bound the same way as current to the multi-image field you want.

It’s up to you where you want to maintain it, but I’d generally recommend you have only one, otherwise it’s a bit of a nightmare to admin.

Webflow’s CMS is based on a no-SQL document store, most likely MongoDB. Because it’s not relational, the database itself doesn’t have two-way relations the way you’re imagining.