Support » Plugin: Cactus Masonry Classic » Short code — and Plugin conflict — only first parameter working

  • I put short code [cactus-masonry post_orderby="rand"] and it works. Then I put anything else (and trust, I tried a lot of variations, from your website suggestions to how using the generator) it doesn’t go past the first parameter.

    For example [cactus-masonry post_orderby="rand" posts_per_page="3"]

    The cactus-masonry rand order is respected, but nothing after the first parameter.

    Any suggestions?


Viewing 5 replies - 1 through 5 (of 5 total)
  • Just noticed an error: Uncaught ReferenceError: elemsCM_GALLERY_44492 is not defined

    Going to check is Lazy Load plugin is conflicting…

    Update: yes, there are multiple errors using Lazy Load plugin.

    The issue is still a problem, where only the first parameter is respected, for example, rand order works, but keeps defaulting to like over 30 images, when I am trying to set it to 12: [cactus-masonry post_orderby="rand" posts_per_page="12"]

    So, no resolution there…

    BUT yes, Lazy Load plugin conflicts with this plugin.

    Basically, if I use Lazy Load plugin, then it destroys my layout, and you don’t see the % loading…

    So I disabled Lazy Load.

    Okay, here where is stands now.`

    Lazy Load removed, plugin working.

    Now, some parameters seem to work, its not about the first parameter vs another second parameter.

    For example, I have this right now: [cactus-masonry gallery_align="left" post_orderby="rand" posts_per_page="12" horizontal_spacing="0"]

    So all parameters seem to work GREAT except the post_per_page — this is still defaulting to like 30 per page.

    I am not certain what other parameters will or will not work, or are and are not working. I will keep experimenting.

    BUT if you have any suggestions please do tell 🙂

    By the way — EXCELLENT plugin! 🙂

    Okay, so all parameters seem to work, except the posts_per_page for me.

    Any suggestions?

    Thank you, and thanks for this amazing plugin.

    Plugin Author


    Hi JJNW,

    The posts_per_page parameter tells the infinite scroll how many posts to load per request. The infinite scroll will keep requesting posts (in lots defined by posts_per_page) until the posts loaded run beyond the end of the visible page by a certain amount.

    The parameter page_size may be what you are looking for. This tells the plugin how many posts it can load.

    I hope that helps

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Short code — and Plugin conflict — only first parameter working’ is closed to new replies.