• Review: Issues with Billwerk Update from 1.7.3 to 1.7.5

    Updating from version 1.7.3 to 1.7.5 of Billwerk has caused significant problems for us. We discovered that none of our orders from the last two weeks were captured. Typically, we simply change the order status to “completed,” and Billwerk automatically records the amount.

    We had to revert to version 1.7.3 and confirmed that changing the status from “processing” to “completed” worked correctly again. Due to the inadequate dashboard at admin.billwerk.plus, which lacks an export function, we had to develop an API method to extract all authorized payments. We then had to compare each order with our internal ERP system to check if the order was completed, and finally, we had to manually change the order status in WooCommerce from “processing” to “completed.”. Wasted hours on this, due to their latest update.

    It’s unclear if Billwerk employs inexperienced programmers or if there are other issues, but it’s evident that they do not adequately test their plugin before releasing new versions. This situation is highly disappointing.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Unicco,

    We have recently taken over the support and development tasks for the Billwerk WooCommerce plugins. There have been many bugs to fix in the first weeks of our work on the modules and we sincerely apologize for the change that has caused this one to emerge or to start affecting your usage. I am making it a priority to correct this particular issue about the captures.

    [redacted by moderator]

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    @rschris

    I’ve deleted your offer to login to your user’s site. I’m am 100% sure you mean well but please never ask for credentials on these forums.

    Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER.

    If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty.

    Please be aware that repeatedly asking for credentials will result in us escalating this to the plugins team.

    It’s never necessary to do that. Here’s why.

    There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far.

    • Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
    • Ask the user to create and post a link to their phpinfo(); output.
    • Ask the user to install the Health Check plugin and get the data that way.
    • Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
    • Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again.
    • Ask the user for the step-by-step on how they can reproduce the problem.

    You get the idea.

    Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums.

    Versions 1.7.7 released today solves issues related to auto-capture.

    If you are willing and able to collaborate with us to ensure that the issue you experienced has been solved then please contact us through the address at the bottom of the official Billwerk+ webpage linked as “By Billwerk+” on the page of the plugin. Then the staff will be able to escalate the case to us. Sorry for the inconvenience.

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