Issue with Pagination and Query Loop in Gutenverse Post Block

  • I hope this message finds you well.

    I’m reaching out to report an issue I’ve encountered with the Gutenverse plugin on our WordPress website. We are experiencing problems with the pagination and Query Loop functionality.

    Bug Details:

    1. Pagination Not Working: On the following page, diamonddm.com/knowledge-base, the pagination buttons do not navigate to another page, regardless of which type of pagination is selected. It seems that the Query Loop is not functioning as expected (Figure 1 attached).
    2. Gutenverse Query Loop Block Not Rendering: Any block from Gutenverse that uses the Query Loop functionality is not rendering properly in the Gutenberg Site Editor interface. The block appears to be broken or unresponsive.

    Environment:

    • WordPress version: 6.6.2
    • Gutenverse version: 2.0.8
    • PHP version: 8.3.12

    We would appreciate your assistance in resolving this issue. Could you please advise if this is a known bug or if there are any steps we can take to troubleshoot?

    As Gutenverse is a valuable part of our site, we’re eager to see this issue fixed or to learn if there’s an issue on our side. Please let us know if you need any further details.

    Thank you for providing this great plugin, and I appreciate your help in resolving this issue.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support gowinda

    (@gowinda)

    Hi,

    This issue is new to us and we will try to investigate further. But one thing we knew is that the request was forbidden as it showed 403 error. was there any protected post in your post list?

    View post on imgur.com

    If you haven’t already, try going to your WordPress admin panel, navigate to Settings > General, and change both the WordPress URL and Site URL to use HTTPS.

    Additionally, if you create a new post block with pagination, we’d like to know if you encounter the same issue.

    Regarding your question about the query block, this behavior is intentional within our plugin. When you open the editor to view templates, WordPress loads every template in the editor view and runs the query loop simultaneously, which may occasionally cause an unresponsive error. We use a placeholder for the interface, but once you open the template to edit, it should function normally.

    If you have any more questions, please let us know, and we’ll do our best to respond as soon as possible.

    Hi Gowinda,

    Thank you for the quick response and the helpful insights.

    Regarding the Pagination Issue:

    1. We have verified that no content restriction rules are set, and the pagination problem persists even after deactivating all plugins. There are no custom code snippets controlling content restrictions.
    2. Additionally, we have tested this issue across five different websites, all exhibiting the same behavior.
    3. We confirmed that both the [WordPress URL] and [Site URL] are set to HTTPS, and we have replaced all instances of HTTP with HTTPS using the [Better Search Replace] tool. Despite checking all your suggestions, the pagination issue continues to occur.
    4. If needed, I can provide login access for you to investigate further.

    We agree that the 403 Forbidden error is a valuable clue, and we are investigating it from our end as well while awaiting your response.

    Regarding the Query Loop Rendering Issue: In the Gutenberg Site Editor interface, the CSS for the Post Block does not render, although it displays correctly on the frontend. The editor only shows an error placeholder, not the CSS-rendered content. Could you suggest any solutions for this?

    Thank you again for your assistance. Please let us know if you require any further information.

    Plugin Support gowinda

    (@gowinda)

    Hi,

    We haven’t found any additional clues about the pagination issue yet, but we checked your site, and it seems the problem may already be resolved?

    Regarding the Query Loop rendering issue, it might be a bug. Could you please share some more information with us?

    • Please send us a screenshot of the error placeholder. We would like to understand how it looks.
    • Check for any error messages that might be appearing. To do this, use your browser’s developer tools. You can usually open these by pressing the F12 key on your keyboard. If that doesn’t work, you can search for how to open developer tools in your specific browser.
Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.