• Resolved CrazySerb

    (@crazyserb)


    This issue has been reported on your GitHub:

    and is currently confirmed in both 4.7.0 and 4.8.0 release (4.6.0 release still works fine, somehow).

    I’m wondering how fast do you get to these issues at all?

    I’m seeing some issues from months, even years ago, labeled “high priority” on there and never getting any traction, never being fixed, etc…

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi!

    Thanks for reaching out!

    We try to get to issues as quickly as we can, but we don’t always have a timeline we can share in regards to progress. Some issues that may seem simple to fix on the surface can often require significant changes to fix in the code, which can take time.

    If you could link to the specific report you mentioned I’d be happy to share further insights if any exist for that issue.

    Thread Starter CrazySerb

    (@crazyserb)

    @crazywickedawesome oh, sorry, I thought I included the link in the original post.

    Here it is:

    https://github.com/woocommerce/woocommerce-gateway-stripe/issues/1458

    Plugin Support Stuart Duff – a11n

    (@stuartduff)

    Automattic Happiness Engineer

    Hi @crazyserb,

    Thanks for referenceing the issue link.

    Whilst we cannot offer any ETA on issue investigation and resolution times, with Github you can subscribe to receive email notifications which will keep you updated with any recent comments and indicate any new progress on the issue.

    Image Link: https://cloudup.com/cRqSYGiWN52

    I hope this helps.

    Thread Starter CrazySerb

    (@crazyserb)

    @stuartduff I am aware of that, and I’m already subscribed to the issue.

    What I was asking instead was how fast or often are these issues looked at on GitHub and how fast do you actually tackle them?

    This one specifically has been reported almost 2 weeks ago and no response yet from anyone on your team, for example, and it’s a feature that worked just fine in previous versions but got messed up/broken somehow in 4.7.0 and on, so it shouldn’t even be that hard to undo the coding that broke it, I’m sure (as you don’t need to invent or reinvent anything new there).

    Hi @crazyserb !

    To clarify, the issue you linked to was initially opened by a member of our team and we are aware of this problem. As I mentioned before, sometimes issues that seem like they may be a quick or easy fix, can require quite a bit of work to sort out. Rest assured we’ll update that GitHub report as soon as we have a fix in place.

    Since this is already being monitored on GitHub I’m marking this thread as resolved for now.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Cannot update Credit Card from My Account’ is closed to new replies.