petedan
Forum Replies Created
-
Forum: Plugins
In reply to: [Redis Object Cache] 2.1.1 breaks the site and rolling back didn’t fix itDid you delete the object-cache.php drop-in?
Forum: Plugins
In reply to: [WooCommerce] Asking to Complete Setup after each updateOh crap, not again! Too nervous to update again since the last update (5.7) was a complete fiasco!
Forum: Plugins
In reply to: [Cloudflare] version 4.4.0 not tested on wp 5.7It messed up my WordPress Multisite, critical errors, couldn’t access any sub-sites. Un-installed Cloudflare plugin, all good.
Forum: Plugins
In reply to: [Variation Swatches for WooCommerce] Classes Being Output On All PagesI know a few CSS class is not a big issue, but my OCD was going wild ??
Thank you for your attention.
Forum: Plugins
In reply to: [Variation Swatches for WooCommerce] Classes Being Output On All PagesWhy has this topic been marked as resolved?
Forum: Plugins
In reply to: [Variation Swatches for WooCommerce] Classes Being Output On All PagesIf “Load Scripts” is set for only single product and product archive pages, why have the body classes still load on every page?
Thanks.
And as I asked you, does the twentytwenty theme also have the same infinite scroll feature?
No it doesn’t does it? Because I just checked, and the infinite scroll is a feature that is part of the OceanWP Extra plugin, so how do you suggest I test it with a different theme?
And I also mentioned, I’ve changed over to Nginx fastCGI cache, not WP-Rocket, so why would I reach out to WP-Rocket?
- This reply was modified 4 years, 1 month ago by petedan.
I’m talking specifically about OceanWP theme infinite scroll feature. Does twentytwenty theme also have the same infinite scroll feature for shop page?
Cool reply Elementor team!
Meanwhile, I have Elementor set to use my theme colours, but it’s still outputting all this nonsense:
.elementor-kit-77844 {
–e-global-color-primary: #6EC1E4;
–e-global-color-secondary: #54595F;
–e-global-color-text: #7A7A7A;
–e-global-color-accent: #61CE70;
–e-global-typography-primary-font-family: “Roboto”;
–e-global-typography-primary-font-weight: 600;
–e-global-typography-secondary-font-family: “Roboto Slab”;
–e-global-typography-secondary-font-weight: 400;
–e-global-typography-text-font-family: “Roboto”;
–e-global-typography-text-font-weight: 400;
–e-global-typography-accent-font-family: “Roboto”;
–e-global-typography-accent-font-weight: 500;
}It’s a theme and cache issue, not specific to WP-Rocket. I have since switched to Nginx fastCGI cache, and the issue persists.
I just tested it without WP-Rocket, but with Nginx fastCGI caching, and the problem is the same. So it’s a problem when I use the OceanWP theme infinite scroll feature, and caching.
Will post on OceanWP theme support too.
Any update on this feature? Was it just a polite, “I will consider it”, or do you think you may seriously add this very helpful feature?
Or is there some temporary code I can do myself for a temporary solution?
Thanks.
OK, so WP-Rocket is saving the page 2, 3, 4, etc, for infinite scroll, but not the currency?
I see in WP-Rocket they have built-in compatibility with Aelia Currency Switcher, no idea what I’m looking at here, but is this something that could be done for your plugin?
Thank you ??
I’m still tinkering with this on localhost, so sorry, no live link just yet.
I have disabled infinite scroll for now, just using pagination, and the issue has gone, so it’s definitely to do with OceanWP theme infinite scroll feature.
Also, as I mentioned already, if I load the page with infinite scroll and without WP-Rocket cache, no issues either. So is it the infinite scroll and caching together that’s the problem?
Sorry, I meant to say, the first 12 products will show the new chosen currency, but the infinite scroll loaded more products will still show the previous currency.
My currency storage settings were already set to “sessions”.
I am using WP-Rocket cache, and I have set, “I am using cache plugin on my site”. But if I load the page without WP-Rocket cache, the currency shows correctly. So could this be a WP-Rocket cache issue?