cloudres
Forum Replies Created
-
Forum: Plugins
In reply to: [Yoast SEO] Yoast sitemap error synchronizing slug with WPMLWPML support suggested a fix that I paste here:
Please try the following workaround:
– Go to wp-content/plugins/wp-seo-multilingual/classes/class-wpml-wpseo-xml-sitemaps-filter.php
Add the following code just above line 151 (the default case):
case 'product': if ( class_exists( 'woocommerce') ) { $this->sitepress->switch_lang( $lang_code ); $current_lang_shop_id = apply_filters('wpml_object_id', wc_get_page_id( 'shop' ), 'page', true, $lang_code); $url = get_permalink( $current_lang_shop_id ); $lastmod = get_the_modified_time( 'c', $current_lang_shop_id ); $this->sitepress->switch_lang(); break; }
Does it works for you?
Forum: Plugins
In reply to: [Yoast SEO] Yoast sitemap error synchronizing slug with WPMLHi @maybellyne,
it’s a company web site and I would like avoid to publish it here, please. Could we get on touch by E-Mail about this?
About your question, I was meaning that sometimes the URL is correct, not incorrect. Sometimes it is. I don’t know what cause it. I’m trying to discover it.
Just to be very clear, when the sitemap works correctly I see there:
/it/negozio/
/en/shop/
/it/negozio/categoria-prodotto/prodotto/
/en/shop/product-category/product/When something is not working as well, the sitemap lists:
/it/negozio/
/en/negozio/
/it/negozio/categoria-prodotto/prodotto/
/en/shop/product-category/product/So when something it’s not working well, the problem seems related only to the translation of the shop main page and only when the sitemap shows this page. The URLs of the products in fact are not influenced by this as you can see on my example. “Shop” is “shop” there. “Shop” is not “shop” only on the main page of the shop, but is “negozio” (first language slug).
I’d like send you the sitemap to show you what I mean exactly.
Thanks.
Forum: Plugins
In reply to: [LiteSpeed Cache] Cache by roles@qtwrk thanks!
Forum: Plugins
In reply to: [LiteSpeed Cache] Always Fresh Crawl on Quic.CloudForum: Plugins
In reply to: [Facebook for WooCommerce] Issues with variable productsHi @conschneider,
I contacted directly your support via WooCommerce.com because the situation was very twisted.
Thanks the same.
Forum: Plugins
In reply to: [LiteSpeed Cache] Cache by rolesForum: Plugins
In reply to: [Facebook for WooCommerce] Issues with variable productsHi @nathvi,
I enabled the debug. I’m going to wait for some hours to give you a feedback about what’s happening there.
Thanks!
Forum: Plugins
In reply to: [Yoast SEO] Update from 15.7 to 17.8Forum: Plugins
In reply to: [LiteSpeed Cache] 503 during login and recaptcha with Quic.CloudI opened a ticket there. Thanks!
Forum: Plugins
In reply to: [LiteSpeed Cache] 503 during login and recaptcha with Quic.CloudThe sign up form doesn’t work with Safari. Clicking on “Register now” after filling everything doesn’t work.
Forum: Plugins
In reply to: [LiteSpeed Cache] 503 during login and recaptcha with Quic.CloudExactly. We temporarily fixed it adding the IP of our office on the Whitelist, but it’s a problem for who works in mobility. Please help asap @qtwrk ??
Forum: Plugins
In reply to: [LiteSpeed Cache] Questions related CCSS and JSOk, we are going to test it a little bit. Thanks @qtwrk ??
Forum: Plugins
In reply to: [LiteSpeed Cache] Questions related CCSS and JSIt worked. Can I ask you why @qtwrk? ??
Forum: Plugins
In reply to: [LiteSpeed Cache] Questions related CCSS and JSHere it our report number: WKTIPMYW
It could be caused by the fact that we introduced this snippet inside the function.php?
if (strpos($_SERVER['REQUEST_URI'], "LSCWP_NONCE") === false){ ob_start( function($buffer){ @header('X-LiteSpeed-Purge: nothing'); return $buffer; } ); }
Thanks @qtwrk!
Forum: Plugins
In reply to: [LiteSpeed Cache] Questions related CCSS and JSThe CCSS creation now is complete, because there isn’t nothing more on the list. But
<style id="litespeed-ccss">
is not present on the HTML file. Maybe it could be necessary to clean the cache completely to see it at work?Now the web site it’s working well, so in the case that something will be broken what do you suggest? Is there a chance to leave CSS async, but without the critical on? It is just a supposition right now, but I’d like to play in advance.
Thanks @qtwrk!