Masonry objects with slight overlap

[jborum]

I have two questions regarding this page:
http://staging.jeremyborum.com/the-latest-buzz/

​1) The layout is making errors at first and some posts overlap, presumably because it computes the masonry layout before the sizes are preloaded and known. If I resize the window even a tiny bit all the overlaps go away, so I think it’s just a question of stalling the layout a short moment until the necessary images or post sizes load fully. Could you tell me how to do that please?

​2) Is it possible to start loading new posts when the page is at 75% instead of fully at the bottom? It feels a bit jumpy at the moment because we must first reach the bottom, then wait for new posts to load, and then continue scrolling.

Many thanks.​

[ruenel]

Hello There,

Thanks for writing in! I have checked your site and I could not replicate the issue. This is what I see in the first load of the page: http://prntscr.com/iq6btb

Moreover, you may need to activate lazy loading by utilizing the grid preloader in your grid settings to give a lay way for the images to load up. For more information, please check this out: https://theme-one.com/docs/the-grid/#ajax_settings

By the way, please be advised that we have released X 6.0.4 and Cornerstone 3.0.4. It is now available in automatic updates. You can now update to this latest version. This latest release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/).

After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Hope this helps. Please let us know how it goes.

[jborum]

Please look at the link again and scroll down.
http://staging.jeremyborum.com/the-latest-buzz/

The top line of entries is straight, but in the first group of posts some lower ones leave too much white space above and then collide below. Here is an annotated screenshot of the errors as you should see them.

If you resize the window even a tiny amount the posts adjust their spacing issues, so they are clearly placed in the layout a little before their sizes are completely known.

It seems like ajax is not waiting quite long enough for the preload. How can we fix that?

And regarding my question #2 above, can we load the next group of posts when scrolling to 75% instead of 100% so the user doesn’t have to wait?

Thanks.

[christopher]

Hi there,

Unfortunately, it seems that there is a bug in The Grid plugin as I could also recreate the same issue with the Masonry layout with the version 2.6.0 of the plugin.

I will add this to our issue tracker, but please consider that The Grid is a 3rd party plugin which we included in our theme and we cannot release updates, we will inform the developers of the plugin about the bug and that will be their job to release an update.

By the way, there is no option in The Grid to be able to autoload the rest of the items when the user scrolls to a certain percentage of the viewport.

You might have a better chance checking the Essential Grids plugin:

Essential Grid | Themeco Docs

https://www.themepunch.com/faq/load-more-lazy-loading/

FYI, that plugin also does not have the percentage based load more feature.

Thank you.

[jborum]

Okay, thank you for the info.

For the record: Although you bundle The Grid with X, you don’t provide support for it. The Grid ALSO does not provide support for it because it was bundled. Both of you claim that the other one should provide the support, so nobody supports the extensions which come with the theme. It’s shitty. Nobody is standing by the product, and this seems to be true of all bundled items.

[christopher]

Hi there,

Actually, we are the ones that support the plugin. The information I gave you was an attempt to inform you the limitations we have. As I already mentioned we already added this as a bug report and our development team will inform The Grid guys about this.

We will surely follow up the case with the plugin developers. I just needed to inform you that we will not be the ones who actually fix the issue, we also report these kinds of stuff to the plugin developer.

Thank you for your understanding.