Oscar Gare

Hi,
Thanks for following up!
Regarding your questions, I can’t answer PRO support questions here due to the ww.wp.xz.cn community guidelines. Could you please reach out to us directly through our official website? You can submit a pre-sale inquiry via our support page:
https://www.pricebasedcountry.com/support/

Thank you.

Hi there,

Thank you for reaching out and using our plugin.

Please note that compatibility with “Variable Subscription” products (from the WooCommerce Subscriptions extension) is a feature exclusive to the Pro version of Price Based on Country. The free version hosted here on ww.wp.xz.cn only supports the default WooCommerce product types (Simple, Variable, External, etc.).

You can check the full feature comparison here:
https://www.pricebasedcountry.com/docs/getting-started/free-vs-pro/

If you are using the Pro version, commercial products cannot be supported in this forum due to ww.wp.xz.cn community guidelines. In that case, please open a support ticket through our official website:
https://www.pricebasedcountry.com/support/

Hi!
Yes, it’s possible. You can leave the price to be calculated using the exchange rate, or set a fixed price manually for each pricing zone. Please review:
https://www.pricebasedcountry.com/docs/getting-started/managing-country-product-pricing/

Hi there,

This query retrieves the products for which the scheduled sale price starts or ends. It runs every day on the woocommerce_scheduled_sales hook. The query is affecting you runs to get the products that have the “scheduled sale price date” set to “manual” for the pricing zones.

How many products and how many pricing zones do you have? 37 million rows are a lot of rows.

If you don’t have products that have the “scheduled sale price date” set to “manual” for the pricing zones, you can turn off this daily task with the following code snippet:

remove_action( 'woocommerce_scheduled_sales', [ 'WCPBC_Product_Meta_Data', 'scheduled_sales' ], 11 );

Hi,
It’s a conflict with the variation swatch feature you use. Try to add the following code snippet to force the “swatches” JavaScript to refresh the value it stored after the “Ajax geolocation” runs:

add_action( 'wp_footer', function() {
    ?>
    <script type="text/javascript">
        (function($) {
            $(document.body).on('wc_price_based_country_after_ajax_geolocation', function() {
                var $v_form = $('form.variations_form');

                if ($v_form.length > 0) {
                    // Eliminamos el atributo que mencionas
                    $v_form[0].removeAttribute('data-variation-price');
                    
                }
            });
        })(jQuery);
    </script>
    <?php
}, 99 );

You can use the Code Snippets plugin to add the code.

Important: Clear the cache after adding the code snippet.

Hi @adampmc

If you pass the wcpbc-manual-country=US parameter in the URL, the plugin sets the customer’s country to US and initializes the WooCommerce session. Since the WooCommerce session is set to the US country, when the AJAX request runs, the plugin reads the correct pricing zone and updates the price accordingly. There are no issues with the wcpbc-manual-country parameter when AJAX price loading is active.
I found the same problem you reported in two cases:

• The cache plugin returns a cached page, and the request does not reach the server. So the plugin code does not run, and the session is not set.
• Users who run a code snippet that changes the country based on other conditions, breaking the wcpbc-manual-country parameter functionality.

I happy to help you to solve the problem if you share the page with the problem and your WooCommerce sytem report.

Hi @thecandleboutique
I am very sorry for the issues caused by the recent update. We released a patch (version 4.2.1) less than two hours after the launch of version 4.2.0 to minimize the impact and protect as many users as possible.

Regarding the missing data, it is likely that the backup you restored did not include the plugin’s configuration and data. To resolve this, you can restore a backup from yesterday (or a date when you are certain the data was intact). Immediately after restoring the backup, update the plugin directly to version 4.2.1.

Please let me know if you need further assistance.

Hi,
Thanks for the feedback! version 4.2.1 fixed the error.