Pro 6.0 b4: strange behaviour with first element of a looper

Beta
#1

I’m experiencing some strange behaviour with the first element of a looper.
In this instance, I have a looper provider on a grid grabbing a custom post type, with the cells doing the consuming, and when I set the count to a number higher than 15, the first child element of the first cell loses it’s content:

This is occurring in the builder only, and it shows up correctly on the front end.

Here is what the content should be:

image
image2246×400 127 KB

And here you can see it is totally empty when the number of items being provided is higher than 15:

image
image2244×234 97.3 KB

It’s a really odd one, as I have tried a few other things and none are coming up with this issue.
E.g. if I bring in a different custom post type to this same provider, the issue does not arise. Also, changing the ordering of this provider has no effect, so it’s not to do with a specific post breaking it.

Not sure if it’s one that will be very replicable, but maybe!

I added a secure note with login details incase that helps. The specific page is the About page and the Team Grid consumer and layout.

1 Like
#2

Looking into this further, it appears to be something to do with the condition evaluation. That first child-element of the x-cell is a featured image displayer with a sub-div for if there is a featured image set, and an icon if there is not.

image
image586×802 13.7 KB

That Profile Picture div shows up empty for the first item in the loop regardless of whether it is the first child of the cell.

Seems like when there is over a certain threshold of items in the loop, it is no longer calculating the featured image condition correctly for that first item, and neither the No picture or the Picture element is showing up.

Additionally, I found another instance of it happening (building out a news grid on this same page) where this time the threshold was far lower, at just 2

And this time it is referring to the builtin post post type from Wordpress, rather than a custom post type

1 Like
#3

Thanks for testing. This issue is being looked at.

1 Like