Beta 6 - building recent posts loop on home page

[scotbaston]

Hi Guys,

I’ve got another one that doesn’t seem to work for me. Its probably something simple that I am doing wrong but for the life of me it doesn’t seem obvious

in the back end it shows the following 3 post recent post looped column

in the front end it shows garbage

If I don’t add a looper provider, nothing shows at all. I have tried adding various conditions in various places or none at all and still it shows rubbish on the front end.

each post should link through to a post (which it does correctly), show the featured image, title and excerpt (which it doesn’t)

Any help would be appreciated

Scot

[Maratopia_Digital]

Hey,

I’m having very similar issues here. Looks all good on the back end then on the front end shows absolutely nothing. Tried multiple conditions but also doesn’t work.

Any help would be greatly appreciated.

Cheers,
Jonathan

[alexander]

Hey @scotbaston and @Maratopia_Digital,

We’ve definitely got a bug where elements are not outputting in the content builder when using loopers… It’s got something to do with the content builder (and Global Blocks) relying on a shortcode based structure so we’re losing access to some information. Will confirm here when it’s worked out. Sorry about the confusion on this one.

[alexander]

Fixed some issues with the looper providers today. Should be consistently/predictably working in all builders with the next patch.

[Maratopia_Digital]

Hey @alexander,

Thanks so much for sorting this out, this is now working on my end on Beta 7.

Also, I just wanted to ask. I’ve used one of your post looper templates and on the row’s setting you use just an em value to specify the column’s structure, how does that work?

I think I have an idea of what it’s doing but just wanted to hear from the experts.

[alexander]

Sure! It means something like “try to afford each column in this row 28em of space”. The Column sizing of the Row element is powered by flex-basis. It takes string separated dimensions, and applies those to each Column in order. 28em will give every column flex-basis: 28em regardless of how many you have. If you added a space and did something like 20em 8em your first column would be 20em and your second 8em. When we run out of dimensions, it repeats again for remaining columns.

Hopefully that makes sense, but what’s really important is the motivation behind this technique. Imagine adding a 4 column row inside of a skinny sidebar area. That would be very squished. At a page level, we can solve this by changing the number of columns per breakpoint - but breakpoints only apply to the entire device width, and don’t translate at all to our sidebar. Flex Basis is the solution because the content will just grow to fit comfortably. Depending on the width of the container, wherever you drop Posts it will try to fill as much space as possible but never output more than one column if the space isn’t accommodating.