• nukurt

    (@kurtnuimage)


    We seem to be missing the log file completely, there’s nothing titled “wc-stripe” on the Woocommerce > Status > Logs page.

    Even though on the API Settings page, we have the setting “Debug Log” checked. Why doesn’t this file exist? There’s been a few instances recently where it would be useful to review the log but it doesn’t exist.

    Perhaps for a seperate support thread but we had a duplicate payment issue, the first order went in as “unpaid order cancelled” but seems to have actually charged the customer. The second order went through as normal. But because of this it meant the customer was charged twice. The first payment had to be refunded directly through Stripe as a Transaction ID seemingly didn’t exist on the order.

    Again i would have used the logs to review this but there aren’t any available.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    Why doesn’t this file exist?

    There could be any number of reasons why the log file doesn’t exist, none of which would be caused by a Stripe plugin issue. The first thing to check is that the proper file and directory permissions have been setup for your WordPress installation.

    Typically if log files aren’t being created it’s because the file permissions aren’t correct and so the web server can’t write to the log file.

    You can always check the stripe.com > developers > logs to get a better picture of the requests that are being made for a particular payment.

    Charged twice issues almost alway come down to a 3rd party plugin issue or custom code that triggers an error during the checkout process during the WooCommerce payment_complete process. If WooCommerce feeds the plugin a new order ID, then it will naturally treat that new order ID as a unique payment and process it.

    Kind Regards

    Thread Starter nukurt

    (@kurtnuimage)

    The file & directory permissions are set correctly. Every other log file within /uploads/ is being created & updated correctly, it’s just the one generated by your plugin which doesn’t.

    I will look into whether anything could be interfering with the payment_complete process, there’s nothing in our custom code, but perhaps there’s a plugin causing some problems.

    Plugin Author Payment Plugins

    (@mrclayton)

    it’s just the one generated by your plugin which doesn’t

    Our plugin uses the WooCommerce provided log functions so there isn’t anything unique about how it works compared to other logs.

    By looking at the stripe.com > developers > logs and the webhook logs you can see pretty much everything that the Stripe plugin log would have.

    Kind Regards

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