And wondered if the latest release now includes this?
Major issues for us for the same reasons and so I hope that you folks have found a way of helping us not feel pain with oversizes options tables 🙂Theme version: 8.2
Thanks for using our theme.
Here you can find changelog – https://xstore.8theme.com/update-history/
Read about theme and plugins update – https://xstore.helpscoutdocs.com/article/63-theme-update https://xstore.helpscoutdocs.com/article/37-plugins-update
thanks for the reply. Please see attached a link to my WP Options Table and you’ll see lots of X Store/theme related autoloaded Data entries – Can you advise if these are all necessary and if not then what I can do about them?
I am assuming all ET entries are because of the theme?
Also other items needed for the theme such as the Kirki entry. I’ll list below the ones I am curious about whether we can do anything about them…
the above entries I think are related to the theme and your plugins – e.g. Kirki – so can you advise how we can make this better and better performing?
I’ve passed your question to our dev team. Waiting for comment from their side. We have a lot of requests these days, so it may take some time. Sorry for this delay.
Hi Guys – any response to this? I have a huge Autoload Data size and many of the DB rows are from the theme – it would be really helpful if your DEVS can take a look at whether or not these rows need to be autoloaded.
et_studio_data – it was excluded from autoloading.
theme_mods_hg-child – these are settings of some hg-child theme that you use or used
smile_modal_styles, brainstrom_bundled_products, smile_style_analytics – it’s not related to our theme. We don’t have such things in our theme. Probably it comes from the third-party plugin.
kirki_downloaded_font_files – it loads the fonts that you chose in theme settings. We can’t remove that from autoload.
et_multiple_headers_old – we’ll remove that field in the next theme version
theme_mods_xstore – these are settings of XStore theme. We can’t remove that from autoload.
et_multiple_headers – you need that if you created multiple headers, to load them quickly on your pages. We can’t remove that from autoload.
et_multiple_single_product – you need that if you created multiple single product templates, to load them quickly. We can’t remove that from autoload.
thanks for the reply – that is super helpful.
I guess this answers a lot then in terms of reliance of 3rd party plugins e.g. Kirki – as you can see it is Autoloading a fair bit and swallows up a lot of the allotted advise 0.8MB limit on autoloaded data on WPEngine who are said to be one fo the best WP hosts. So if your required plugins affect that a lot then this answers why some people suffer poor performance?
I’m surprised the Child Theme is so large a size – as well as some of your other essential required DB table Rows – I wonder if this can be improved upon as at the moment I have removed lots from my site and turned off Autoload data where I can but the theme itself is swallowing up a lot of my autoloaded data 🙁
Do you use a lot of different fonts on your site? Kirki is the options framework that we use but we are not developers of that and do not manage that moment with the fonts autoloading. You may ask the plugin developer about this moment here https://wordpress.org/support/plugin/kirki/
Lots of fonts? Not really – but we are about to remove fonts and upoad to Elementor instead so no need to call from Google.
I see the Kirki autoload data is font related – do you use that in the theme? I wonder if I can disable autoload on this as I intend to use the fonts uploaded to Elementor for use on the site – not sure if Kirki needs to be autoloaded that’s all..
Overall in XStore there are lots of rows that autoload – is there a way to make this more optimal/streamlined? Just a tohught
Any update please? I reached out to Kirki but nothing and over 5 days
Take our apologies for the delay in answering.
We can’t disable autoload of the Kirki fonts via child theme just for you. At the same time, we can’t disable fons autoloading for all the users because many use global fonts, not Elementor fronts, and they need that.
You must be logged in to reply to this topic.Log in/Sign up
One standard license is valid only for 1 project. Running multiple projects on a single license is a copyright violation.