The use of the Icon Block with the Query Loop

  • Resolved delrod

    (@delrod)


    10 months, 2 weeks ago

    Hi,

    I noticed that inserting an icon in the Query Loop, unfortunately, disables its function of infinite pagination (called Force page reload function). This function helps visitors to navigate the pages of the query loop without needing to refresh the whole website page.

    When I remove the icon from the query loop, the infinite pagination again works.

    Under the option of Force page reload in the query loop it says: (Browsing between pages won’t require a full page reload unless non-compatible blocks are detected).

    Thanks for your time reading!!

    With kind regards,

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Nick Diego

    (@ndiego)

    This for reporting @delrod. I looked into this and apparently that functionality is currently only available for Core blocks. As soon as a block from a plugin placed in the Query block, the functionality is disabled. You can see the code here.

    My guess is that this is temporary. The functionality is driven by the Interactivity API, which is very new and currently only available in Core. In WordPress 6.5, the API will be opened up for general use, and I expect this limitation of plugin blocks to be removed.

    Best,
    Nick

    Thread Starter delrod

    (@delrod)

    Thank you for the detailed answer!

    I’m wanting to do the same, creating a custom block to use inside core/post-template and have more control over post content output, but I would like to keep the non-reload pagination feature.

    Is it possible in 6.5? There’s anything that I have to do in order to my block to be compatible with it? I would appreciate if anyone has any link covering this topic. (Sorry for not opening a new ticket, it just felt very aligned with this one)

    Plugin Author Nick Diego

    (@ndiego)

    It looks like support for non-Core blocks in the Query Loop with the non-reload pagination feature was enabled in WordPress 6.5.2, specifically in #60006. I just tested it and it works, so I will enable this functionality in the next release (planned for early next week).

    For anyone else that stumbled upon this ticket, you just need to add the following to your blocks "supports" property in block.json

    "interactivity": {
    "clientNavigation": true
}

    Best,
    Nick

    • This reply was modified 5 months, 1 week ago by Nick Diego.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.