• I am having major ongoing issues with this plugin. I have multiple support tickets open but the support I am getting is inconsistent – I often get responses from BC support who are not familiar with this plugin. I then ask clarifying questions and a few days later will get a response from another person. This has gone on for months. I am reaching out here in the hopes that someone like @topher1kenobe can look into my issues and we can get a dialogue going, because talking to a different person every few days is never going to solve these problems. I cannot continue to have a site that’s broken, while waiting a few days every time I send a response, only to have it answered by someone who is not familiar with the software.

    Here is a very general overview of my issues:
    I am continuing to get messages almost daily from WP saying that the site has had a technical issue. Sometimes “There has been a critical error on your website. Learn more about debugging in WordPress.” appears on the front end of the site. This appears to be related to API credentials, but my client is the store owner, because he needs to have access to the financial data; this means that I, as the site developer, do not have access to the API credentials because I’m not the store owner. I also reported back in March that checkout doesn’t work in Safari, IE11, and occasionally Chrome. This issue has sat unresolved since then.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Topher

    (@topher1kenobe)

    Hey Jesse (if I may call you that), could you email me at [email protected]? I’d like to ask for some info that shouldn’t go in the forums.

    That error is a 500 server error, and if it’s tied to the API, and only happens occasionally, I’m going to strongly suggest that it’s from an under powered server. We’d want to do some more testing before just acting on that however.

    I wrote back about the IE11 and Safari issue (which is different from the Chrome issues) on the other ticket, but I’ll do it here also for visibility. The problem is getting engineering attention, but it’s not a high priority given the low usage rates of IE11. That said, it’s been fixes a couple times, and may actually be working now in IE11.

    Safari is a bit trickier since the problem isn’t old tech, but rather new tech that is constantly moving.

    I appreciate your patience, and I’m sorry it’s been a struggle.

    Thread Starter jesseamber

    (@jesseamber)

    Many thanks, Topher. I just sent you an email.

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

The topic ‘Outstanding support issues, inconsistent support reps’ is closed to new replies.