[Support request] Plugin Conflict With Latest GP Premium

[Ash]

Hi

I’m having an issue with WooCommerce Load More Products products. I thought it was a Litespeed optimization but I tried disabling the plugin and it was still the same.

So I decided to disable plugins that have been recently updated. GP premium once disabled fixes the issue.

I have always used this plugin with the theme and never had an issue with it before.

[Leo]

Hi Ash,

Just viewed the linked page and the load more function seems to be working for me.

Is GP premium disabled on the page currently?

[Ash]

If you go on and scroll it will load the products, carry on scrolling and it shows the exact same below with page title, sort filter etc, then it messes up completely and starts showing products in a weird list.
Gp Premium is active, I can’t leave it inactive as I lose the custom header with search etc.

[Tom]

This should be fixed in 2.0.1 which was just released.

Let me know 🙂

[Ash]

Hi Tom,

I’m afriad that did not fix it unfortunately.

[Ash]

Seems infinite load for blog is causing the issue. Turned it off, until this is fixed.

I know like many we would like to see infinite load added for product archives, most plugins are clunky and bloated with crap.

[Tom]

2.0.1 should have fixed the issue – any chance you can turn infinite scroll back on so I can take a look?

[Ash]

No problem it is back on

[Tom]

The issue seems to be fixed on my end – can you try clearing the caching plugin and your browser cache to see if that makes a difference for you?

[Ash]

I think it was showing the cached page with it turned off, Cleared cache please check again. Its still doing it for me

[Tom]

Can you turn the caching off completely for now?

[Ash]

done

[Tom]

Ah ok, I think I see the issue.

For now, you can do this:

add_filter( 'option_generate_blog_settings', function( $settings ) {
    if ( function_exists( 'is_woocommerce' ) && is_woocommerce() ) {
        $settings['infinite_scroll'] = false;
    }

    return $settings;
} );

Will get this fixed in 2.0.2.

Thanks!

[Author]

Posts