Hello Rose,

Apologize for late reply.

Yep that helped and works. However seems only pictures displayed are only where is one photo and seems if there is album it don’t show despite check box at option “Show everything except album and video posts” is not checked.

Any trick for that?

Thank you,
Tomas

One more thing I found out:

our original X-Store Child Theme had this function in functions.php:

//Remove Query Strings From Static Resources 
function smartwp_remove_query_strings_from_static_resources( $src ) {
  if( strpos( $src, '?v=' ) ){
    $src = remove_query_arg( 'v', $src );
  }
  if( strpos( $src, '?ver=' ) ){
    $src = remove_query_arg( 'ver', $src );
  }
  return $src;
}
add_filter( 'script_loader_src', 'smartwp_remove_query_strings_from_static_resources', 999 );
add_filter( 'style_loader_src', 'smartwp_remove_query_strings_from_static_resources', 999 );

// Add mailchimp integration
add_action('wp_head', function() {
	?>
	<script id="mcjs">!function(c,h,i,m,p){m=c.createElement(h),p=c.getElementsByTagName(h)[0],m.async=1,m.src=i,p.parentNode.insertBefore(m,p)}(document,"script","https://chimpstatic.com/mcjs-connected/js/users/ba7e51eafdcb61b2943699529/cbf3f511c5104a42d1d457e3e.js");</script>
	<?php
});

Which also causes the same issue.

When removed from functions.php, and your Remove Query Strings From Theme Static Resources is turned on, the same issue.

Basically, your theme or jscomposer doesn’t like query strings removed for some reason.

This is the error we see, does this mean anything to you?

Uncaught TypeError: Cannot read properties of undefined (reading 'currentTheme')
    at window.vc_rowBehaviour.window.vc_rowBehaviour (js_composer_front.min.js:10:9014)
    at window.vc_js.window.vc_js (js_composer_front.min.js:10:659)
    at HTMLDocument.<anonymous> (js_composer_front.min.js:10:20071)
    at e (jquery.min.js:2:30038)
    at t (jquery.min.js:2:30340)

Only happens when the XStore Child theme is activated (even a fresh new one I downloaded from your Downloads section, no modifications).

Seems that JsComposer (WPBakery builder) doesn’t know how to read your Child Theme?

I can confirm that the WPML issue was separate – WPML 4.5.11 version has issues with WP 6.1, but now we have updated WPML to 4.5.12, confirmed to work with WP 6.1 and content still doesn’t show.

Even when we deactivate all WPML plugins, content doesn’t show.

At 1am CET on the 7th of November, we have updated these:
– WordPress to 6.1
– X Store theme + X core plugin to their latest versions
– plugins:
GDPR Cookie Compliance
MC4WP: Mailchimp for WordPress
Really Simple SSL
W3 Total Cache
WooCommerce
WP Maintenance Mode & Coming Soon

Neither of these plugins should interfere with WPBakery page builder displaying content, so it still seems like an X-Store issue.

done 😉

Thanks Olga,

Not sure why they were removed but after you put values back it looks much better 🙂 thank you.

Tomas

Thanks Olga, so far i know there is http cache which cache .js on hosting site but that should cache only for 10 minutes.

I reached out to them now to see if there is some other server cache which can influence this.

I tried also remove instagram API on web and add it back again, but did not helped either.

I will let you know once i have answer from webhosting provider.

Hello,

We use only w3 total cache. We used CDN in past but it is disabled and not longer used.

Did you just disabled our total cache now?

Apologize for late reply, login details in private area.

Thanks Rose, i will try and if no luck will open a new topic.

Cheers,
Tomas

Hi Rose,

Sorry for late reply, its working fine, thank you very much.

Cheers,
Tomas

Hello,

Please see private area for details.

I see this fontawesome-webfont.woff2 within preload in for theme, so i assume theme utilize it, I am just not sure if I need it. In GTmetrix it sometime take up to 1 second to load, what seems to be quite a lot for me, considering its only 75kb. I seen that other people were looking to this and had same question on this forum, but haven’t seen an answer how it ends.

Also seen recommendation to load this fontawesome from cloudflare servers – replace it in with https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.3/css/all.min.css

Is that something what would work?

Cheers,
Tomas

Hello Rose,

Hope you doing good. Check or change ? 🙂 Should i change code originally provided to this new one?

Thank you,
Tomas

Hello Rose,

thanks for answer. was a bit expecting it. But tell me please, how come that until last update it worked just fine? Please don’t take me wrong, I fully understand that you can’t support custom modifications on child theme. But on other side, there were no changes on child theme for almost year and it start cause issues after last theme update, so it indicate for me that something has been change in parent theme what affected child theme as well? On production we still ran older version and there is no issues. You had to do some changes in last update, is there some detail release notes what has been touched?

Or do we have to pay each time you change something to developer to check all custom code in child theme despite nothing has been changed there? I thought that child theme is for this purpose to keep custom modification and not to cause issues.

For header menu I see there is message “These options will be deprecated in 41 days. We recommend you to use Header Builder.” does it mean that after those 41 days there will be some update and I need to build menu from scratch as you mention or will existing setup somehow automatically moved?

Thanks,
Tomas

Hello Olga,

My apologize, didn’t seen that my provider enabled this. I have disabled it now so you should be able to login.

Cheers,
Tomas