Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter miremonger

    (@miremonger)

    Fixed…we believe…

    As the developer has taken a long time to respond to it. We believe we have fixed the issue.

    1. First make sure the resultC and resultY html files are in your worldpay gateway on their site, not yours. You can find the files within the plugin directory /payment-pages/required/ – upload those and test.

    2. Check your functions.php in the theme for any ?> code if you find some, remove it (this includes the ?> at the end of the file as it is this closing php tag that is breaking the response and thus causing the white screen of death after being redirected back from WorldPay.
    Note: if you have a function in your functions.php that uses html, hence why you may of closed the ?> tag, rebuild it so it uses echo or print instead.

    I will update this thread if it happens again.

    Thread Starter miremonger

    (@miremonger)

    Update to help diagnose the issue:

    I have put on WP_Debug within the wp-config file and got this message when the transaction was complete and the relay was coming back from worldpay to the website.


    Notice: status was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_API->handle_api_requests, do_action('woocommerce_api_mds_worldpay_gateway'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MDS_Worldpay_Gateway->worldpay_response_handler, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/sites/chocolatecraft.co.uk/public_html/wp-includes/functions.php on line 4147 Notice: billing_email was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_API->handle_api_requests, do_action('woocommerce_api_mds_worldpay_gateway'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MDS_Worldpay_Gateway->worldpay_response_handler, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action('woocommerce_order_status_processing'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, FP_RAC_Abandon_Order_Management->fp_rac_check_order_status, FP_RAC_Abandon_Order_Management::fp_rac_check_cart_list_manual_recovery, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/sites/chocolatecraft.co.uk/public_html/wp-includes/functions.php on line 4147 Notice: user_id was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_API->handle_api_requests, do_action('woocommerce_api_mds_worldpay_gateway'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MDS_Worldpay_Gateway->worldpay_response_handler, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action('woocommerce_order_status_processing'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, FP_RAC_Abandon_Order_Management->fp_rac_check_order_status, FP_RAC_Abandon_Order_Management::fp_rac_check_cart_list_manual_recovery, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/sites/chocolatecraft.co.uk/public_html/wp-includes/functions.php on line 4147

    I then created a staging environment using the WP staging plugin and it was successful in transferring back to the website and to the order received page after test purchase.
    I am unable to replicate the above message on the staging environment for some reason. However I was getting this wp debug notification:


    Notice: payment_method was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), wp, WP->main, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MDS_Worldpay_Gateway->set_wc_notice, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/sites/chocolatecraft.co.uk/public_html/staging/wp-includes/functions.php on line 4147

    Any ideas or suggestions on what I can try to fix this issue? Chocolate Craft is using a custom built from scratch type theme.

    Thanks for the support 🙂

    Thread Starter miremonger

    (@miremonger)

    Thanks for your advice with this.

    I have created the theme from scratch and have added the standard wordpress includes within the functions.php.

    The reason why I am bringing this thread up again is that it is appearing to happen to another site of ours.

    Is there any specific code within the functions.php or theme that I need to create in order for the plugin to redirect correctly?

    Many thanks for your help 🙂

    Thread Starter miremonger

    (@miremonger)

    *bump*

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