Support » Plugin: WooCommerce SecureSubmit Gateway » Several problems updating to 2.0.1

  • Resolved lousaint

    (@lousaint)


    Hi,

    I ran into a few problems with the latest update (2.0.1):

    1. We offer more than one payment gateway, but the new iframe place order button that replaces the WooCommerce button doesn’t work with these, of course. Could you make it so that the button gets swapped back if another gateway is selected?
    2. If the customer has a saved card, the saved card/new card selector no longer seems to work–specifically, nothing happens when I click “Pay with a new credit card.” (It looks like the event handler for this was removed.)
    3. After clicking place order, one of the input fields that gets added by the response handler is visible. It looks like a bug on line 85ff., where you’re resetting the values for expYr instead of setting them for bin (so when bin is added later, it’s not hidden).
    4. I’m getting two PHP warnings for undefined variables. Looks like these variables were removed elsewhere, but these two locations just got missed:

    PHP Warning: Undefined variable $secureEcommerce in /wp-content/plugins/woocommerce-securesubmit-gateway/classes/wc-gateway-securesubmit/class-payment.php on line 109
    PHP Warning: Undefined variable $authenticated in /wp-content/plugins/woocommerce-securesubmit-gateway/classes/wc-gateway-securesubmit/class-payment.php on line 236

    5. Could you update the version number when you enqueue your js and css files for cache-busting purposes? (Simplest would be to just pass the plugin version instead of ‘1.0’ when you call wp_enqueue_script.) I ran into problems at first because my browser had cached an older version of the javascript file. I suspect customers will run into this, too.

    Nice to have:
    It would be nice if we had some basic styling options for the place order button (e.g., background color, hover color) to make it blend better with our theme. Maybe these would be plugin settings that then get passed as arguments to your server when you fetch the button.

    Thanks.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author SecureSubmit

    (@markhagan)

    @lousaint , thank you for reaching out. Bullets 2 and 3 were actually addressed with the release this morning (2.0.2). Our development team will review and follow up on the other topics you’ve raised. In the meantime, please reach out to our development team directly at developers@heartland.us if you need any immediate assistance.

    Thread Starter lousaint

    (@lousaint)

    Great! Thank you for the quick response.

    Plugin Author SecureSubmit

    (@markhagan)

    Happy to help! Also, I misread your #1 earlier – it also should be resolved with the recent release. Just FYI

    +1 to @lousaint
    “Nice to have:
    It would be nice if we had some basic styling options for the place order button (e.g., background color, hover color) to make it blend better with our theme. Maybe these would be plugin settings that then get passed as arguments to your server when you fetch the button.”

    Agreed. My store’s theme is pretty far removed from the button’s default styling, so the button “as is” sticks out like a sore thumb at a critical point in the checkout flow.

    Plugin Author SecureSubmit

    (@markhagan)

    @lephilissimo @lousaint Following up regarding the order button styling and general behavior – the updates in the version we released this morning (2.1.0) revert back to using WooCommerce’s order button instead of one created by our plugin. This should address the styling issues you noted. Please update if/when convenient and let us know if there is anything else we can help with.

    @markhagan Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.