Pagination conflict with PostX plugin use of wp_enqueue_scripts

  • Resolved Sherwin

    (@sherwinarnott)


    10 months, 2 weeks ago

    Hey folks, I’ve been getting some broken ajax pagination when I use Litespeed with Post Grid Gutenberg Blocks and WordPress Blog Plugin – PostX plugin. I like to have the pagination on post grids. But with the caching, the pagination will eventually break. Sometimes it takes a day or so.

    I have sent you a Toolbox report: #TNROZMEO

    I asked the PostX folks about it, and they did a little digging and said the following.

    Upon thorough investigation, we’ve determined that the problem lies in the utilization of the “wp_enqueue_scripts” hooks for pagination. Unfortunately, LiteSpeed is inhibiting the execution of this hook, causing logged-out users to encounter pagination errors… To find a comprehensive solution, it’s essential to contact LiteSpeed and inquire about the reason for blocking the “wp_enqueue_scripts” hooks.

    PostX tech support

    As a short term solution I had added wp_enqueue_scripts to CACHE > PURGE > PURGE ALL HOOKS, but then I realized this was causing the page cache to be rebuilt every time anyway. So I’ve removed this.

    Here’s what the pagination can look like on the URL I’ve provided for you.

    Does this all make sense? Have I missed something? Let me know know what you think.

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

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support qtwrk

    (@qtwrk)

    please try disable JS minify and CSS minify , purge all , see how it goes

    Thread Starter Sherwin

    (@sherwinarnott)

    Thank you, I’m running a couple of experiments now and will report back!

    Thread Starter Sherwin

    (@sherwinarnott)

    I disabled JS and CSS minify, and purged all, and then waited a day. Unfortunately, the pagination has failed. I ran this experiment on two sites. But this is the page and site you have the most data on: https://www.eitrainingcompany.com/articles/.

    Here are two screenshots of the broken pagination in case they’re helpful.

    (1)

    (2)

    • This reply was modified 10 months, 1 week ago by Sherwin.
    Plugin Support qtwrk

    (@qtwrk)

    okay, this sounds like a nonce issue not js issue

    please try enable ESI, see how it goes after a day

    Thread Starter Sherwin

    (@sherwinarnott)

    Okay, I have enabled ESI and purged the cache. I will report back asap.

    Thread Starter Sherwin

    (@sherwinarnott)

    Enabling ESI has not solved the bug.

    • This reply was modified 10 months, 1 week ago by Sherwin.
    Thread Starter Sherwin

    (@sherwinarnott)

    Something that I find very interesting about this bug is that it doesn’t occur right away. For some number of hours, the cache gets built and the pagination continues to work. But by the next day, the pagination breaks.

    Plugin Support qtwrk

    (@qtwrk)

    please contact the plugin support, and ask them what’s the nonce name on action “ultp_pagination”

    Thread Starter Sherwin

    (@sherwinarnott)

    On it!

    Thread Starter Sherwin

    (@sherwinarnott)

    Hey folks, the developers didn’t get back to me regarding the nonce name on action “ultp_pagination”, however, they did ship an update and the pagination appears to be working now. Let me know if you still want the nonce name! Otherwise, thank you for your help with this, I will mark this thread resolved.

    Thread Starter Sherwin

    (@sherwinarnott)

    There are two updates on this file. One, is that the pagination bug persists. The second is that the developers of PostX did get back to me about the nonce name on action “ultp_pagination”. They say it’s wpnonce. Let me know your thoughts.

    Plugin Support qtwrk

    (@qtwrk)

    hmmm? maybe you can ask them to point out the related code for that part

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Pagination conflict with PostX plugin use of wp_enqueue_scripts’ is closed to new replies.

Tags