This topic has 6 replies, 4 voices, and was last updated 3 months, 2 weeks ago ago by Andrew Mitchell
Hi,
We want to use this plugin: https://woocommerce.com/document/country-restrictions-woocommerce/
There is an option to restrict the add to cart button for certain counties.
But this function does not work with the xstore add to cart buttons.
A test product which should not be able to buy in the Netherlands: https://www.expandsupps.com/shop/new/test-product-niet-in-nederland-te-bestellen/
Is there a fix for this?
Thanks in advance!
Hello,
Thank you for reaching out to us with your request.
Please provide temporary wp-admin and FTP access. We will check what can be done to help you.
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.
For FTP access, we require the following details: FTP host, FTP username, FTP password, FTP port, and FTP encryption type. If you need assistance in creating these credentials, please reach out to your hosting provider who will guide you through the process.
Best Regards,
8Theme’s Team
Thanks for the reply!
Dear @Luc,
I hope this message finds you in good health and spirits.
We have thoroughly investigated the issue you reported and found that it exists only with our Single Product Builder that is currently installed on your web-site. Upon reviewing the code for your “Country Restrictions for WooCommerce” plugin, it has become apparent that a global compatibility update is necessary. Our builder does not utilize standard WooCommerce hooks due to the builder unique structure, which varies and cannot remain static across different cases. Unfortunately, one of these standard hooks is essential for loading your plugin on the Single Product page (details here: https://prnt.sc/KYntUCSoSo3o).
The “Cor_Front” class of plugin, does not support direct integration of custom functions in our theme due to the absence of an instance callback, causing the __construct() function to trigger immediately upon each call.
To resolve this, we recommend reaching out to the developers of the “Country Restrictions” plugin to discuss potential solutions that would ensure compatibility with our Single Product Builder. Our builder utilizes specific hooks tailored to various content display scenarios, such as ‘etheme_woocommerce_template_single_title’ for displaying the product title.
You can find a comprehensive list of our builder’s hooks here: https://www.8theme.com/documentation/xstore/additional-customisation/single-product-builder-hooks/
Please note, the following standard WooCommerce hooks are not incorporated in our builder for the reasons described above:
1. woocommerce_before_single_product_summary
2. woocommerce_single_product_summary
3. woocommerce_after_single_product_summary
4. woocommerce_share
To address this compatibility issue, you have several options:
1. Disable the Single Product Builder.
2. Contact the plugin’s authors to seek a viable solution. If one is found, we could consider integrating it globally.
3. Rewrite the ‘xstore/woocommerce/content-single-product-builder.php’ in your child theme and add the necessary actions for compatibility.
We regret any inconvenience this may cause and are here to assist with any further questions or concerns you might have.
Best regards,
Jack Richardson
The 8Theme Team
Thanks for the help! We’ve fixed the issue.
Dear luc,
We hope you’re reveling in the experience our theme brings! Your enthusiasm is what fuels our passion. Would you be so kind as to channel that energy into a 5-star rating on ThemeForest? Your feedback is the spark that lights our way!
Click here to spread the love: https://themeforest.net/downloads
Thank you for being an integral part of our journey!
Best Regards,
The 8Theme Team
Tagged: add to cart button, woocommerce themes, wordpress
The issue related to '‘Add to cart buttons not disabled with external plugin’' has been successfully resolved, and the topic is now closed for further responses