Forum Replies Created

Viewing 15 replies - 1 through 15 (of 41 total)
  • Thread Starter Bruno Cantuaria

    (@cantuaria)

    Awesome. Thank you!

    Great great plugin!

    I’m also expecting the WP CLI option, but meanwhile I’ve developed a quick script to be run at command line which willl do the trick.

    I’ve only tested it with WASABI, but if you understand PHP (please don’t try use it if you don’t) you may replace the variables and make it work with other servers.

    I’ve sent it to git: https://gist.github.com/brunocantuaria/c21e3e4e180fef272dddc30430faa3e2 , have used it on 2 different servers and it worked great.

    Any update on this topic? I may try to help as well.

    I also had this issue. Basically, the plugin won’t show the “Full Image Size” when selecting a crop size, instead it would just displayed the already cropped version to crop even more, and after cropping, the image would be deformed.

    I also fixed the issue reverting to version 1.8.0, it’s working without issues

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Thanks, that was clarifying. I guess I tracked and deactivated every place where the full page cache was triggered. I’ve also disabled the crawler, I guess that for a news website with thousands of posts, it doesn’t make sense, it also helped reducing server usage.

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Additional note:

    Here’s an entry from the Purge Log:

    04/26/24 15:41:35.969 [**masked** 1 Kgp] 💓 ------POST HTTP/1.1 (HTTPS) /wp-json/wp/v2/posts/601385
    04/26/24 15:41:35.969 [**masked** 1 Kgp] Query String: _locale=user
    04/26/24 15:41:35.969 [**masked** 1 Kgp] HTTP_REFERER: https://www.**masked**/wp-admin/post.php?post=601385&action=edit
    04/26/24 15:41:35.969 [**masked** 1 Kgp] User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
    04/26/24 15:41:35.969 [**masked** 1 Kgp] Accept: application/json, */*;q=0.1
    04/26/24 15:41:35.969 [**masked** 1 Kgp] Accept Encoding: gzip, br
    04/26/24 15:41:35.969 [**masked** 1 Kgp] Cookie _lscache_vary: admin_bar:1;guest_mode:1;logged-in:1;role:50
    04/26/24 15:41:35.969 [**masked** 1 Kgp] X-LSCACHE: true
    04/26/24 15:41:35.969 [**masked** 1 Kgp] X-LiteSpeed-Purge: public,stale,482_Po.601385,482_URL./**masked**/,482_Po.601376,482_Po.601391,482_T.1,482_T.41016,482_FD,482_A.103,482_F,482_H,482_REST,482_URL./,482_URL./noticias/ => LiteSpeed\LSC->send_headers()@620 => WP_Hook->apply_filters(,ARRAY)@324 => WP_Hook->do_action(ARRAY)@348 =>
    /home/admin/domains/**masked**/public_html/wp-includes/load.php@517

    Let me know if I’m reading it correctly:

    A POST request to /wp-json/ from the post.php admin page, issued a Cache Purge. But what was purged? I assume this was triggered when saving post, correct?

    Anyway, I want full control of cache purging, because this is a site with big audience and multiple authors updating a lot of stuff every minute, and I’m seeing full cache being purged at least twice per hour.

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Thanks, I’ll monitor the log.

    Meanwhile, can you check if updating a profile will clear All the cache? It seems so.

    Is there a way to disable ALL cache purge? I want to programatically chose what and when to clear.

    @hailite updated to version 6.2-b3 and it fixed.

    Note that, this seems to be related with Cron jobs, after updating I had to manually stop the php script which was running the cron job, then the log stopped increasing.

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Thanks guys. This was very helpful. I’ll investigate further and tweak things and will udpate here for future reference.

    We use this same setup for other websites (some with even more audience) but didn’t had a complain yet.

    I’ll mark this as solved by now.

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Thanks for the feedback. I’ll play with the Brotli and Gzip for both Cloudflare and local to see if the issue still happens.

    @supervisior could you describe more about this encoding error when Cloudflare have a version of the cache and Litespeed have another? Maybe we can find something to mitigate it. Currently we use Cloudflare Cache because it’s simply overpowered and drastically reduces our server load. We’ve built internal API integration with Cloudflare to clear content whenever we clear LiteSpeed cache, even in special cases.

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Ok, here’s what I’ve found

    • No related error on dev tools when it happens.
    • lsesi parameter is presented in both requests
    • No error on LS log, in fact, the log when ESI outputs and when it doesn’t outputs, is the same. Here’s the diff between them (the version at 10:09 – at left panel – is the faulty one): https://www.diffchecker.com/O0jYFe5X/

    What else can I check?

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    What should I look on the logs, doesn’t seems to contains anything relevant? There are entries about ESI:

    [ESI] 💕 [BLock_ID] esi [wrapper] esi-shortcode [Control] public,no-vary

    I see no errors when the ESI is not executed though

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    I’ll try that and wait for it to occur again. Meanwhile, could it be related with Cloudflare?

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    Ok, found the bug.

    I’ve checked if the footer was triggering, and it was as intended, then I saw that on a related function (send_headers_force)

    * For compatibility with those plugins have ‘Bad’ logic that forced all buffer output even it is NOT their buffer

    I had this piece of code on the wp_footer action:

    ob_start();
    custom_post_ad($target);
    $ads = ob_get_clean();
    ob_end_flush();

    After removing it, it worked. Do you know why this happened? Is that way of getting the buffer wrong? Or the plugin isn’t compatible with buffer retrieval at the footer action?

    Thread Starter Bruno Cantuaria

    (@cantuaria)

    No luck. From what I see, wp_footer is being called correctly, by the page source code I can see scripts which are tied to it appearing.

    I’ll investigate further tomorrow.

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