Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author PerfectSolution

    (@perfectsolution)

    Hi Kristian,

    Thank you for your post.

    I have followed the callback example mentioned in WooCommerce’s official payment gateway docs which can be found on http://docs.woothemes.com/document/payment-gateway-api/

    I must admit that I am not entirely sure why you would always replace https with http. I suppose there is a good reason to this, but as of right now, I cannot give you the very specific reason.

    Since this is a big problem with your current setup, I suggest you modify classes/woocommerce-quickpay-order.php.

    Replace:

    public function get_callback_url() {
     return str_replace( 'https:', 'http:', add_query_arg( 'wc-api', 'WC_Quickpay', home_url( '/' ) ) );
    }

    With;

    public function get_callback_url() {
     return add_query_arg( 'wc-api', 'WC_Quickpay', home_url( '/' ) );
    }

    Please be aware that these changes will be lost in case of a plugin update.

    Thread Starter edlund

    (@edlund)

    I understand your concern, however I don’t understand why either.

    I have done something like that already, but I am not too keen on that solution since it is for a customer. And I really want her to be able to update the plugin.

    Would it be possible to add a filter to the callback url? If that would be an okay solution I am willing to submit it as a pull request. If that makes it easier for you.

    Plugin Author PerfectSolution

    (@perfectsolution)

    To your information this problem is solved in 3.0.7.

    Thread Starter edlund

    (@edlund)

    Thanks 🙂

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Callback problems when using HTTPS’ is closed to new replies.