Forum Replies Created

Viewing 15 replies - 16 through 30 (of 12,050 total)
  • Looks like that’s coming from CoolPay:
    https://ww.wp.xz.cn/plugins/woo-coolpay/

    Do you have this plugin? Its not been updated for 6 years and has several issues, not just that one, because things have changed in that time. To confirm, temporarily deactivate CoolPay. Do you still have the messages?

    Editing its code to bring it up to date will need plugin writing skills or a developer. I think you’ll need to look for an alternative plugin.

    My experience on the site has got worse since last time. I can add the sample product to the cart, and it shows in the header cart dropdown. However, there are no links to the cart page or to the checkout page, so I can’t check those.

    The grecaptcha error is showing in the console for the product page. As said, I don’t have elementor but reading round it seems google recaptcha is integrated into elementor. I think you’ll need to take the grecaptcha error issue to Elementor support. ww.wp.xz.cn forums can only effectively support themes and plugins available from ww.wp.xz.cn.

    The problem may not be that but the issue does error before the payment errors.

    My best guess is that the settings for WP_Square_Payment integration are not quite right and this is leading to the problem in your first post.

    The first error is at the line: wp.i18n.setLocaleData It says that wp is not defined. This error is described here:
    https://ww.wp.xz.cn/support/topic/conflict-with-i18n-min-js-in-core/
    Its telling us that the script that defines the javascript variable wp is not loaded until after wp is used.

    I don’t have elementor as its premium, but is there any way in elementor settings that allows javascript loading to be defered? if so, set loading to be not deferred.

    The WP_Square_Payment error is the same sort of thing. Variables are being used before the script which defines them has been loaded.

    Have you tried the general debug procedure? Deactivate all plugins except WooCommerce and the payment plugin and switch to the default theme. Keep the site as simple as possible. Does it work now? It should do. Reactivate plugins one-by-one and check to identify which plugin is not playing nicely.

    I’m still seeing the same set of errors.

    I’m seeing several console errors. The first is due to the product being unavailable in my locality. (I am in the UK and I see you are in Canada,) The second is coming from grecapture – it seems to not be setup properly. The next two are coming from the WP_Square_Payment form handler. Its possible that early errors are causing the later ones, and that if the early ones are fixed, the later ones may no longer appear.

    I can’t change my locality.

    Consider double checking the grecapture set up. If the setup looks good, try disabling it until the rest is working.

    Consider revisiting all aspects of the WP_Square_Payment integration.

    I’m sorry I can’t be nore specific.

    Is the difference in who can see the field either logged in users or not logged in users? Please post the link to your site.

    I changed my site language to Italian and these two strings were translated correctly, so this does not look like a WooCommerce issue. To confirm, change your theme for a moment to Storefront and check.

    It looks like you are using the Flatsome theme. This is a premium theme and I don’t have access to it. I think Flatsome has its own templates which override the default WooCommerce templates. Consider asking Flatsome support about this.

    Loco Translate is not the tool for this problem because it would make a custom translation which you would need to keep up-to-date yourself. The Say What? plugin is better for translating the odd string until the Flatsome Italian translation is updated. However, without a copy of Flatsome, I can’t advise the correct settings for these strings in Say What? Flatsome support should be able to help.

    Try this custom css:

    .woocommerce .quantity .qty {
    width: 4.5em !important;
    }

    Something you have called the astra-addon is setting the text colour to white and the opacity to 0. Can you manage without the astra-addon?

    If not, you can try this css:

    .woocommerce-SavedPaymentMethods-saveNew label {
    opacity: 1 !important;
    }
    body .woocommerce-additional-fields label {
    color: #333 !important;
    }

    So if Loco Translate is used, my understanding is that that would make a custom translation file. If the file is kept in the default location, it will be overwritten the next time Mollie translations are changed. If the file is kept in the custom location, it needs to be updated by the webmaster if Mollie strings are changed. Either could be a burden. The Say What? plugin is suitable for the translation of a small number of strings and may be a better way until the Mollie Dutch file is updated by Mollie’s Dutch translators.

    That string is not in the WooCommerce plugin, so its coming from your payment processor plugin. It looks like you are using Mollie for WooCommerce? That’s a premium plugin which I don’t have so I can’t look at it to be sure. Download the plugin to your hard drive and do a text search to find out if the string does come from there. If so, contact support at woocommerce.com. Premium plugins are not normally supported in this forum.

    Thread Starter Peter Lawrenson

    (@lorro)

    If you look in wp-config.php for the line $table_prefix = ‘something’, it will tell you what the table prefix is for your site. If its the default ‘wp_’, then no, my suggestion won’t make any difference to you.

    If your table prefix is something else, then it may make a difference but the code is too complex for me to say. You’ll need to wait for the plugin author to issue an update.

    If you are feeling lucky, replace wp_ in line 68 with your table prefix, deactivate and reactivate treepress to run the change. Take a backup first.

    The first may be coming from:
    Design > Customizer > WooCommerce > Kasse
    Put your own text in the last field.

        WooCommerce correctly translates the button text to German with a default setup. Try going to the list of pages, Checkout page. In the block editor, look at the Place Order button. Its likely that the default text has been changed to Buy Now. If so, just edit the text to your words.

        Yes, looks like a theme issue. Meanwhile, try this custom css to get it working:

        .products a {
        display: inline-block;
        }

        I don’t think this would be possible using css.

        It could be done with a php snippet. The code would intercept the rates array and reorder it before returning. The code to do this is more than one would normally expect via a forum answer. Debugging may require access to your system.

        add_filter( 'woocommerce_package_rates', 'custom_shipping_rates', 100, 2 );
        function custom_shipping_rates( $rates, $package ) {
        // reorder the $rates array
        return $rates;
        }
      Viewing 15 replies - 16 through 30 (of 12,050 total)