This topic has 9 replies, 3 voices, and was last updated 2 months, 3 weeks ago ago by Andrew Mitchell
Good afternoon, I am presenting various problems with the Xstore template.
xstore builders templates not loading well, not updating editions, problems with containers.
slowness of the page, I have already checked the plugins, database, it seems to be a problem with the template
Hello, Tiang,
Please record some videos and upload them to a file-sharing service, such as WeTransfer (https://wetransfer.com/). Once uploaded, kindly provide us with the URL link to the file.
Could you please provide temporary wp-admin access?
To grant WP-Admin access, please proceed to create a new user account with an administrator role through your WordPress Dashboard. Once the account is established, you may securely transmit the username and password to us via the Private Content section designated for this purpose.
Best Regards,
8Theme’s Team
I attach the wetransfers link with the videos.
One of the videos shows the errors, in the archive products, product single and footer templates.
The other video shows how these templates should look correctly.
Added to this, each product page takes at least 10 seconds to load for each product and I fear that it is a problem with the xstore theme.
Hello, Tiang,
Please get in touch with your hosting provider to fix the memory error -https://prnt.sc/qvWI60KGgjn7
Let us know once it will be fixed.
Best Regards,
8Theme’s Team
I already communicated the error problem with my hosting provider, and they have taken care of this,
But I still have problems editing the xstore builder templates for archive products, product single, and footer.
and slow issues on my site that I would like you to advise me if it is a problem with the template or if I should change it. Since my site is additionally experiencing slowness problems.
Hello, Tiang,
All your problems are caused by the mentioned memory error.
Your current memory value is 256 MB (you can see it in WooCommerce > Status) , and the text of error is: Allowed memory size of 805306368 bytes exhausted (tried to allocate 67108872 bytes) This means: 805306368 bytes + 67108872 bytes = 872415240 bytes = https://prnt.sc/stor_gAlHeRJ
It is important to note that the need for increased memory is not a requirement of the theme itself but a necessity due to the number of plugins installed on your site. Each plugin adds to the total memory requirement, hence the need to increase the memory limit as indicated in the error message.
We recommend adjusting your memory settings accordingly to ensure smooth and efficient performance of your website.
Best Regards,
8Theme’s Team
Could you tell me where it appears that the memory is 256 MB?
Since it appears to be 768 to me, attached image
At this moment the products archive and product single template has just been broken again and everything looks bad.
obviously it’s the theme
Hello, Tiang,
“Since it appears to be 768 to me” – ok, you are right, but it requires – 873mb https://prnt.sc/stor_gAlHeRJ “Allowed memory size of 805306368 bytes exhausted (tried to allocate 67108872 bytes) “.
“products archive and product single template has just been broken again” – yes, because someone disabled Elementor and XStore Core plugins on your site.
Please adjust the memory limit to 873MB at your earliest convenience. Once this adjustment is made, we will proceed with addressing and resolving the remaining issues.
Thank you for your attention to these matters. We look forward to your prompt action and are here to assist you with any further needs.
Best Regards,
8Theme’s Team
Dear Tiang,
As we continue our mission to exceed expectations, your insights become increasingly valuable. Could we, with all due respect, request your thoughtful feedback by giving our theme a deserved 5-star rating on ThemeForest?
Click here to share your valuable perspective: https://themeforest.net/downloads
Your time and trust are highly appreciated!
Best Regards,
The 8Theme Team
The issue related to '‘problems with xstore builders templates and slowness of the page’' has been successfully resolved, and the topic is now closed for further responses