• Resolved esd3104

    (@esd3104)


    I am trying the block checkout option and am seeing the same issue I reported here about not being able to edit the “Place Order” text on the checkout button.

    Obviously the way to edit the text on the button is different as it is just an edit of the “Place Order” text on the checkout page blocks edit. But regardless of the text entered to replace Place Order, with GDP enabled, is ignored and the button stubbornly remains “Place Order”. Disabling GDP and replacing with any other payment method (check for example) allows the altered text to be shown and replaces “Place Order” as expected.

    I have tried the solution provided for shortcode checkout in my prior support request, and it doesn’t work (as I expected) – blocks work differently.

    My stage site should clearly show the issue. Selecting check payment you see my custom text of “Register Make Payment”. If you select GDP then it changes to Place Order. So something with GDP is overwriting the text of the “place order” button and ignoring the custom text/changes on the checkout block page.

    GDP 1.7.2
    WC 8.6.1
    WP 6.4.3
    WC Blocks 11.8.0
    PHP 7.4.33

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Support Kari-SkyVerge

    (@kariskyverge)

    Thank you for reaching out about GoDaddy Payments. I’m happy to help!

    Our support engineers have told me they are aware of this being an issue in the Checkout Blocks, and are looking into it as we speak.

    This issue will be resolved shortly by our engineers and will be released in an update soon to the plugin and the framework that connects to it. They have been working on the resolution for the Checkout Blocks version of this issue for a few days, so I expect that update will come out in the next week or so.

    Would you please let me know if that is helpful information, and what further questions you have?

    All the best,
    Kari

    Thread Starter esd3104

    (@esd3104)

    Thanks. I will sit back and wait for a fix. No other questions at this time.

    Plugin Support Kari-SkyVerge

    (@kariskyverge)

    Hey there,

    Thank you for letting us know you have no further questions. Please do watch for the update to be pushed out soon, and then once you give the updated version a try, would you please let us know if you have any further issues with the button text?

    Have a nice day!

    Kind regards,
    Kari

    Thread Starter esd3104

    (@esd3104)

    I have updated to 1.7.3 and the “Place Order” button text still remains “Place Order” when GDP is the selected payment method – it continues to ignore changed wording for the button by editing the checkout block.

    Add something to cart from here: https://stage.allbritishcarshow.com/registration/ and then go to checkout. I have left check payment option on so you can see the difference in button wording. I’m not running any cache on my stage site and I have used the browser empty cache and hard reload option and still only see “Place Order”,

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    Thanks for reaching back out and sending me a url to test. When I went to the URL you sent, and then added a T-Shirt to the cart, then went to the checkout page, I’m seeing “Register Make Payment” button. This is what I’m seeing: https://share.zight.com/DOuJKLxy

    Is this what you are seeing on your end?

    All the best,
    Amber ??

    Thread Starter esd3104

    (@esd3104)

    @amberskyverge yes. Check Payment is the default and shows my custom button text.

    If you go back to that checkout page and select GDP as the payment method you’ll see the button text change back to the default “Place Order” text, overwriting my custom text. This is with v1.7.3 installed which is supposed to fix this but apparently doesn’t, at least for me.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    Thank you for letting me know where you were seeing the button not showing your custom text. May I ask what you are using to update the button custom text?

    All the best,

    Amber ??

    Thread Starter esd3104

    (@esd3104)

    It just uses the block editor. With the WC Blocks checkout you don’t seem to need hooks/functions you can just edit the button text right in the block editor of the checkout page.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    My apologies on my delayed reply, we have been quite busy the last few days.

    The filter above is a WooCommerce filter, and it filters the button text argument passed to the checkout template.

    Whereas our payment gateway has its own filter for the button text, which is:?apply_filters( 'wc_payment_gateway_' . $this->get_id() . '_order_button_text', $text, $this );? which for GoDaddy Payments it would be?wc_payment_gateway_poynt_credit_card_order_button_text.

    So while it?might?be possible to read in the site editor changed value and pass that through from the backend to the frontend for registering the block checkout gateway with the site editor text value… It’s not something we have in place at the moment.

    To change this, I believe that the code snippet you were using before was:

     function sv_custom_button_text_place_order( $button_text ) {
        return ‘Make Payment’; // new text goes here
    }
    add_filter( ‘woocommerce_order_button_text’, ‘sv_custom_button_text_place_order’ );

    That should be:

    function sv_custom_button_text_place_order( $button_text ) {
          return ‘Make Payment’; // new text goes here
      }
      add_filter( ‘wc_payment_gateway_poynt_credit_card_order_button_text’, ‘sv_custom_button_text_place_order’ );

    Could you try this and let me know how it goes?

    Thanks.

    Amber ??

    Thread Starter esd3104

    (@esd3104)

    The code snippet I was using is/was:

    add_filter( 'woocommerce_order_button_text', 'abcsweb_custom_button_text' );
     
    function abcsweb_custom_button_text( $button_text ) {
       return 'Register and Pay'; // new text is here 
    }

    Using the code/function you provided my site gets a fatala error and won’t load.

    I did try this also (using your poynt button item) but it also caused a fatal error.

    add_filter( 'wc_payment_gateway_poynt_credit_card_order_button_text', 'abcsweb_custom_button_text' );
     
    function abcsweb_custom_button_text( $button_text ) {
       return 'Register and Pay'; // new text is here 
    }
    

    Before I realized that the button text could be edited in the block editor I was looking at this. I don’t think these filters and functions work the same way with the block check, but who knows, this isn’t my day job. ??

    I have disabled my code snippet (it wasn’t working anyway – the text shown for “Cheque payment” was coming from the block editor and not this code snippet anyway) to avoid any possible conflicts but the results don’t change. The block checkout text is “Register Make Payment” vs. the code snippet trying to have “Register and Pay” – so this confirmed the snippet wasn’t working.

    Plugin Support amberskyverge

    (@amberskyverge)

    Hey there,

    Thank you for trying that. I have tested this on my local site, and I was not receiving a fatal error and the code snippet did work properly. I’d love to dive deeper into this issue on why this is happening with your website, in hopes to find why you’re receiving a fatal error and to get this code snippet up and working for you. The best way to do this would be to have you fill out our help form, that way I can get more information to better assist you.

    Would you mind going to https://www.skyverge.com/contact/ and filling out the form to move forward?

    Thanks ??

    All the best,

    Thread Starter esd3104

    (@esd3104)

    I have submitted my contact info using the form and the “I’m getting in touch for something else” option as none of the others seemed to provide appropriate options.

    Thread Starter esd3104

    (@esd3104)

    For anyone else needing this solution the code snippet problem was caused by single quote translation issues. By replacing all single quote marks with my keyboard it worked as expected.

    function sv_custom_button_text_place_order( $button_text ) {
          return 'Make Payment'; // new text goes here
      }
      add_filter( 'wc_payment_gateway_poynt_credit_card_order_button_text', 'sv_custom_button_text_place_order' );
    Plugin Support jlareauxskyverge

    (@jlareauxskyverge)

    Hey there,

    It has been a long time since we heard from you, so I’m going to mark this topic as resolved.

    If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

    Thanks,
    Jesse L ??

    Plugin Support Kristy

    (@kristybrg)

    Hey esd3104 ??

    Apologies for our team not addressing your last two replies in this thread! We communicated with you over email when we received your request there, and I see that’s now also marked as “solved”. So, I wanted to make sure to follow-up and close the loop here as well. ??

    Thanks so much for sharing that fatal error you received when implementing the code snippet was due to needing to convert smart quotes to straight quotes. So glad to hear that’s resolved and we appreciate you sharing the solution here for the benefit of the community!

    Additionally, I wanted to mention an alternative (preferred) way to the contact form when you need to open a support request related to your GoDaddy Payments account. GoDaddy Payments has a Get Help link available in the WordPress admin when you navigate to WooCommerce > Settings > Payments > GoDaddy Payments. You can reach out to us there for help anytime if you have questions about your account or need to share private information related to the issue you’re experiencing. ??

    I’ll keep this thread marked as “resolved”. Have a wonderful day!

    Best,
    Kristy | SkyVerge Support

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Block Checkout – “Place Order” Button Text Problem’ is closed to new replies.