hernan2022

I apologize for the error; my extension version is 2.0.1

At least in that version, the error occurs where all posts containing the “#” character cannot be shared, resulting in a fatal error in the console

Well, I suppose it’s understandable that I’m not receiving support for the extension since I don’t have an active license. By the way, I think this must be happening to everyone

I’ll keep trying with CSS or JS; there must be an easy way to prevent that context menu from appearing

I understand, I’ll run more tests. it sounds tricky

Thank you very much for the information. It would be great if you could look into this further, especially since you mention in the YouTube video that it “facilitates navigation, particularly in mobile view.”

I understand it’s a delicate matter in terms of performance, but if it’s achieved reasonably well, the user experience will be greatly improved

In any case, thank you very much for the response and the information. I’ll run more tests before making a final decision

Thinking about it, this could be tricky, since we might trigger a lot of server queries

I think the most responsible fix would be something like this:

jQuery(function ($) {

  var busy = false; // evita múltiples ejecuciones por scroll

  function autoLoad() {
    if (busy) return;

    var $btn = $('.load-more:visible').last();
    if (!$btn.length || $btn.data('autoloaded')) return;

    var triggerPoint = $btn.offset().top - 800;
    var viewBottom  = $(window).scrollTop() + $(window).height();

    if (viewBottom > triggerPoint) {
      busy = true;                // bloquea reentrada
      $btn.data('autoloaded', 1); // marca este botón
      $btn.find('a').trigger('click');
    }
  }

  // Escuchamos scroll en cualquier lado (window + contenedores móviles)
  $(window).on('scroll', autoLoad);
  $('.yz-wall-content, .yz-content, .bp-single-activity, body').on('scroll', autoLoad);

  // Cuando BuddyPress carga más contenido, liberamos el lock
  $(document).ajaxComplete(function () {
    busy = false;
  });

});

I believe this solves the problem more safely. In any case, I would greatly appreciate it if you could confirm receipt of this feedback.

Updated Youzify 3.6.1

It’s an old bug or issue. That Open Graph gets inserted across the entire site

Thanks for the reply

I was able to fix it; for some reason, setting TTL to 0 wasn’t enough, but I was able to get it working with the litespeed_control_set_nocache hook

add_action( 'template_redirect', 'lscache_nocache_404', 0 );
function lscache_nocache_404() {
	if ( is_404() ) {
		do_action( 'litespeed_control_set_nocache', '404' );
	}
}

Although this is a sign that the CartPops plugin might not be very modern and I should change it

But for now, I’m fine with this

Thanks, best regards, Merry Christmas!

That’s right! It works!

Replacing with litespeed_buffer_before data-src for data-src-disabled (just to disable it) applies the plugin’s lazy loading. I just need to fine-tune the code a bit more to correctly select what I need, and I’ll be done

Thank you so much for the support!

I think Google shows something interesting. The images it highlights are the large 600×600 images, meaning they’re the “main slider” of the product, the big version of the product images.

PageSpeed Insights

Maybe I could do something by taking the DOOM images out and putting them in. But it sounds complicated if they don’t fit into the lazy loading process from the start