• Resolved Felix Mahama

    (@mdordaa)


    Ok, I'm now at my wits' end. No matter what I do I can't get Litespeed esi blocks to show up on my websites. Of course, once caching or esi is turned off all the blocks show up as expected.

    esi blocks I've tested: WordPress comments form (both on WooCommerce single product page and WordPress regular post), shortcodes of Product Slider Pro for WooCommerce by ShapedPlugin and Shortcodes by Code Snippets by Code Snippets Pro. However, admin bar shows up correctly.
    Example shortcodes I tried
    [esi woo_product_slider id="xxxxx"]
    [esi woo_product_slider id="xxxxx" ttl="3"]
    [esi woo_product_slider id="xxxxx" ttl="300"]
    [esi woo_product_slider id="xxxxx" cache="public" ttl="300"]
    [esi woo_product_slider id="xxxxx" cache="private" ttl="300"]
    Result: all of them showed the same problem.

    Websites tested: 1 Multisite install, 4 single WordPress installs
    Result: Only one of the single WordPress installs worked. All 5 subsites of the multisite install are showing the problem.

    Themes: The multisite install and 3 of the single installs are running on twenty twenty-three and its child themes while one of the single installs is running on twenty twenty-five theme.
    Result: Only one of the single installs running on twenty twenty-three theme is working.
    I exported the Litespeed cache settings from the working site to the site running the twenty twenty-five theme (a test site) but it still didn't work.

    Plugin conflict: I disabled all plugins of the main site of the multisite leaving only Litespeed cache but it still did not work.
    Comparing plugins of the multisite install with the single site install that worked, only askimet anti-spam and wp super cache (both disabled) are on the working site but not on the multisite. However, the same plugins are on the test site that is also not working.
    On the test site there are only 3 plugins: askimet anti-spam, wp super cache (both disabled) and litespeed cache. So Litespeed cache is the only active plugin there, but it is not working.

    Users: The problem exists for both logged-in users (including admin) and guests.

    Hosting Servers: I have changed hosting since I started testing this problem. The problem occurs on both hosts. Both hosts use Litespeed enterprise servers.

    Quic.Cloud: All the sites are connected to Quic.Cloud.

    Others: I also tried with caching of admin bar and comment form on and off alternatively.
    With and without object caching didn't help.

    On the linked page, there's supposed to be a recently viewed products block below the product list.

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

Viewing 15 replies - 1 through 15 (of 22 total)
  • Thread Starter Felix Mahama

    (@mdordaa)

    This is a follow-up update with additional information.

    Report Number: YXRBZVJV – This is the report number of the multisite main site which is NOT working: https://www.topbuygh.shop. I’m also adding the test link here too for convenience: https://www.topbuygh.shop/product-category/electronics-electricals/. After the main product list on this page, there should be a recently viewed product block.

    Report Number: ZANOXVED – This is the report number of the single site that is working: https://www.thecitizenalert.com/blog-posts/scams/emergence-of-scam-award-schemes-in-ghanas-tertiary-education-space/

    Report Number: ECBJVDLT – This is the report number of the single test site that is NOT working: https://test.topbuygh.shop/?p=1

    Plugin Support qtwrk

    (@qtwrk)

    [woo_product_slider id="xxxxx"]

    I assume this will work ?

    Thread Starter Felix Mahama

    (@mdordaa)

    Yes, iit will work.

    Plugin Support qtwrk

    (@qtwrk)

    function buffer_output_after( $content ) {
    if (strpos($_SERVER['REQUEST_URI'], "test") !== false){
    error_log( print_r($content, true), 3, WP_CONTENT_DIR . '/litespeed/debug/dump_after.log' );
    }
    return $content;
    }
    add_filter( 'litespeed_buffer_after', 'buffer_output_after', 0);

    please try this :

    add above code to theme functions.php

    purge all

    open the page as guest user , with ?test attach to the URI , like https://your_domain.com/something/?test

    then open /wp-content/litespeed/debug/dump_after.log , copy paste and share via https://pastebin.ubuntu.com/

    Thread Starter Felix Mahama

    (@mdordaa)

    Plugin Support qtwrk

    (@qtwrk)

    okay , now please remove or comment out the above code

    go to LiteSpeed Cache -> toolbox -> debug setting

    set dbeug log to ON

    debug level to advanced

    debug include URI:

    test
    lsesi

    then go to toolbox -> log view , clean up existing log if any

    now open the page that contains this shortocde as https://your_domain.com/something/?test

    once page is loaded , go to log view again and share me the log

    Thread Starter Felix Mahama

    (@mdordaa)

    There’s a funny story here. It’s no longer logging. When I followed your instructions, there were debug log entries which I cleared. Even now, there’s still a log file from yesterday on the server with entries. At first it was logging only object cache events, but after I turned that off and then back on, it stopped logging those too. Here’s the url I tested: https://www.topbuygh.shop/product-category/electronics-electricals/?test. Just to confirm, there are no log entries in the ls cache interface and the current log files on the server are empty as well.

    I have tried with and without the settings changes you asked me to make. I’ve tested with ?test, ?lsesi and without any, as admin and as guest. I’ve tried both basic and advanced debug levels.

    Here’s the current report number from the main site: JPFCFJNN

    Plugin Support qtwrk

    (@qtwrk)

    from report it looks like you set debug log to OFF , please check ?

    Thread Starter Felix Mahama

    (@mdordaa)

    Here’s a screen shot of the settings

    And here’s a new report: AVMPFUQQ

    Now it’s generating object cache entries again. Just the following 2 lines being repeated:

    05/22/25 20:43:45 – OC – Init Redis connection to /xxxx/xxxx/tmp/redis.sock:0
    05/22/25 20:43:45 – OC – Connected

    I’ll keep digging into this.

    Plugin Support qtwrk

    (@qtwrk)

    please follow this guide , to clean up plugin’s database records, then re-configure the debug setting

    Thread Starter Felix Mahama

    (@mdordaa)

    That didn’t help.

    If this helps: I have tested this on the single site installs and found no problem. On the multisite where the problem occurs (the settings are not saving), the problem is with only the network settings. I have tested all the subsites and their settings are saving correctly.

    Thread Starter Felix Mahama

    (@mdordaa)

    After uninstalling the plugin, deleting all options from the db and reinstalling, nothing changed, so I had to change the settings directly in the db to get the logs. Here you go.

    Plugin Support qtwrk

    (@qtwrk)

    is it actually displayed lsesi=esi & # 0 3 8 ; _control , instead of & ?

    this looks like something altered the URI which breaks ESI request.

    • This reply was modified 1 year ago by qtwrk.
    Thread Starter Felix Mahama

    (@mdordaa)

    I’m afraid I don’t understand the question.

    I’ve been doing some more digging on my own but have come up empty so far. I would like us to change the site we’re troubleshooting to a test site. This is a single WordPress install. This test site has only 3 plugins: Litespeed cache, wp super cache and askimet anti-spam. Only litespeed cache is active. Hopefully we can find the solution faster from here. The htaccess file contains only the default WordPress and litespeed cache (automatically generated) codes.

    Here’s a report from that site: WCFFWUUD

    Here’s a debug log dump.

    URL tested. This time around, we’re testing a basic WordPress post with comments allowed for all visitors.

    Note 1: I replaced “test” with “twist” for the query parameter, because there is already “test” in the url. Let me know if this is wrong. Irrespective, the debug log entries are generated even when I don’t add “?twist” or “?lsesi” to the url. But the log I posted above was generated with “?twist” in the url.

    Note 2: Remember from my original post that this issue of esi blocks not showing up is happening on many sites, both single installs and multisite.

    Plugin Support qtwrk

    (@qtwrk)

    this is the ESI URI form up on my test site , check the red-letter explanation

    and this on your log

    that’s why I asked , if it actually shows this & # 0 3 8 ; in the debug log ?

    because if so , that means something on your site that changed the request URI and breaks ESI request due to this

Viewing 15 replies - 1 through 15 (of 22 total)

The topic ‘esi blocks not showing’ is closed to new replies.