Hey @mathistrndevinf
Thanks for doing that, I can see clearly that masonry is not working / being triggered.
While I don’t understand the issue fully I think I can highlight some potential issues:
- Normally, when using Masonry with WordPress, the default version of the Masonry script is loaded (that comes with WordPress) , this is the version our plugin is designed to use
- If we look at our website, inspect the source code, we can see the following line is used to load Masonry:
<script src='https://customlayouts.com/wp-includes/js/masonry.min.js?ver=4.2.2' id='masonry-js'></script>
We can see Masonry is loaded from our wp-includes directory, part of WordPress.
- I can see on your site though, that does not exist, instead, you have this:
<script src="https://unpkg.com/masonry-layout@4/dist/masonry.pkgd.js"></script>
Notice here, its not being loaded from your WordPress install, but instead, from unpkg.com
It looks like something in your setup is loading Masonry in a non-standard way, and this would be my best guess as to why Masonry is not loading correctly on your site.
What I would do to see where the issue is coming from:
- Change your theme (temporarily) to a default WordPress theme, and see if the issue persists
- If it does, then its likely a modification coming from another plugin, in which case you will need to disable your plugins one by one and keep checking (and refreshing the page) to see where the issue is coming from.
Once you know what is causing this change, then we might be able to figure out a solution (but not guaranteed, I’m afraid).
Let me know how you get on, and if that all makes sense.
Thanks
-
This reply was modified 1 year, 10 months ago by Code Amp.
-
This reply was modified 1 year, 10 months ago by Code Amp.