Viewing 10 replies - 1 through 10 (of 10 total)
  • I am receiving the same error. The plugin needs to be redesigned for compatibility with the most recent version of WooCommerce. They have changed the way requests are handled. So unfortunately there is nothing that can be done besides have someone manually fix it or wait for the dev of the plugin to fix the problem since this is not an official CardConnect plugin.

    Personally I am going to rollback my version of WC to see if I can get the error to go away for the time being.

    @matthew – do you get that error while in Sandbox or Production mode? Have you confirmed that your CardConnect MID is entered accurately? Are you using Subscriptions 2.0? We’ve been doing some testing to duplicate the problem and are not able to replicate using the latest WC version.

    I am using the Sandbox mode at the moment. I am afraid to test the production mode just yet.

    I copied the credentials straight from the CardConnect email that I was forwarded by the merchant processor.

    I am not using any Subscriptions plugin either…

    Here is more information, not all of these plugins are enabled. I currently have the caching plugin among many others I am not currently using disabled for the time being until I see fit to use them in the production of the site.

    ### WordPress Environment ###

    Home URL: https://www.tantravape.com
    Site URL: https://www.tantravape.com
    WC Version: 2.4.10
    Log Directory Writable: βœ” /home/tvhostmgr/public_html/wp-content/uploads/wc-logs/
    WP Version: 4.3.1
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    Language: en_US

    ### Server Environment ###

    Server Info: Apache/2.4.16
    PHP Version: 5.4.45
    PHP Post Max Size: 48 MB
    PHP Time Limit: 120
    PHP Max Input Vars: 1000
    SUHOSIN Installed: –
    MySQL Version: 5.5.42
    Max Upload Size: 32 MB
    Default Timezone is UTC: βœ”
    fsockopen/cURL: βœ”
    SoapClient: βœ”
    DOMDocument: βœ”
    GZip: βœ”
    Remote Post: βœ”
    Remote Get: βœ”

    ### Database ###

    WC Database Version: 2.4.10
    :
    woocommerce_api_keys: βœ”
    woocommerce_attribute_taxonomies: βœ”
    woocommerce_termmeta: βœ”
    woocommerce_downloadable_product_permissions: βœ”
    woocommerce_order_items: βœ”
    woocommerce_order_itemmeta: βœ”
    woocommerce_tax_rates: βœ”
    woocommerce_tax_rate_locations: βœ”

    ### Active Plugins (34) ###

    Adults Only AVS for WP: by AGSoft – 1.7.1
    CardConnect Payment Gateway: by SOF Inc – 1.0.3
    Contact Form 7: by Takayuki Miyoshi – 4.3.1
    Debug Bar: by wordpressdotorg – 0.8.2
    Duplicate Post: by Enrico Battocchi – 2.6
    Envato WordPress Toolkit: by Envato – 1.7.3
    EWWW Image Optimizer: by Shane Bishop – 2.5.4
    Force Regenerate Thumbnails: by Pedro Elsner – 2.0.5
    iThemes Security Pro: by iThemes – 2.0.0
    Limit Login Attempts: by Johan Eenfeldt – 1.7.1
    Slider Revolution: by ThemePunch – 5.1.1
    W3 Total Cache: by Frederick Townes – 0.9.4.1
    WooCommerce Checkout Manager: by Ephrain Marchan – 3.6.8
    WooCommerce Customer Relationship Manager: by Actuality Extensions – 2.6.13
    WooCommerce Customizer: by SkyVerge – 2.1.1
    WooCommerce Free Gift Coupons: by Kathy Darling – 1.0.8
    WooCommerce My Account Widget: by Bart Pluijms – 0.5.0
    WooCommerce Order Status Change Notifier: by WooThemes – 1.0.1
    WooCommerce Order Status Control: by WooThemes / SkyVerge – 1.4.0
    WooCommerce Order Status Manager: by WooThemes / SkyVerge – 1.2.2
    WooCommerce Points and Rewards: by WooThemes – 1.5.4 – 1.5.5 is available
    WooCommerce Product FAQs: by Josh Levinson – 3.0.2
    WooCommerce Product Reviews Pro: by WooThemes / SkyVerge – 1.2.2 – 1.3.1 is available
    WooCommerce Shipment Tracking: by WooThemes – 1.4.1
    WooCommerce USPS Shipping: by WooThemes – 4.2.12
    WooCommerce Social Login: by WooThemes / SkyVerge – 1.6.0
    WooCommerce: by WooThemes – 2.4.10
    iDevAffiliate WooCommerce Integration: by iDevDirect.com LLC – 1.0
    WooThemes Helper: by WooThemes – 1.5.9
    Yoast SEO: by Team Yoast – 3.0.4
    WP-CORS: by Tim Stephenson – 0.2.1
    WP Force SSL: by Kostas Vrouvas – 1.2.1
    YITH Essential Kit for WooCommerce #1: by YIThemes – 1.1.7
    Zopim Widget: by Zopim – 1.4.1

    ### Settings ###

    Force SSL: βœ”
    Currency: USD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 2

    ### API ###

    API Enabled: βœ”
    API Version: 3.0.0

    ### WC Pages ###

    Shop Base: #8 – /shop/
    Cart: #9 – /cart/
    Checkout: #10 – /checkout/
    My Account: #11 – /my-account/

    ### Taxonomies ###

    Product Types: external (external)
    grouped (grouped)
    simple (simple)
    variable (variable)

    ### Theme ###

    Name: Betheme
    Version: 10.6
    Author URL: http://muffingroup.com
    Child Theme: βœ• – If you’re modifying WooCommerce or a parent theme you didn’t build personally we recommend using a child theme. See: How to create a child theme
    WooCommerce Support: βœ”

    @matthew – thanks for the additional info! We’ll post here when we figure out the issue. So far, we’ve only been able to reproduce the problem when we have an incorrect MID in the settings, but we’re still doing further troubleshooting.

    @matthew – Please confirm with your hosting provider that the following ports are open: 6443, 8443. If the host will only open those ports for a specific IP address, you’ll need to get those IP’s from CardConnect.

    I spoke with CardConnect directly and they told me that my version of WooCommerce is not yet supported. They only support 1.x not 2.x

    Or at least this was their excuse. They then tried to set me up on Authorize.net and I got a separate error. They used the excuse that this was because it was testing mode and that sometimes testing mode doesn’t work and that I should switch it to Live mode to test it, which in my mind defeats the purpose.

    Should I still open these ports for use with Authorize.net?

    I believe that both problems relate to the API keys being invalid or some kind of setting being wrong in the backend of CardConnect or Authorize.net as I was in such a hurry to get it working…

    However, I setup stripe payment gateway in under 5 minutes. It is the easiest I’ve ever used. So straightforward without all of the BS you see with the others.

    Your version of Woo Commerce is supported. They might have been referring to their plugin not yet supporting Woo Subscriptions 2.0, but from what you posted, it doesn’t look like you are using that plugin. My guess is that all you need to do to get CardConnect working correctly is confirm with your host that the ports are open.

    If you decide to go with Auth.net or Stripe, you don’t need to ask your host to open those ports.

    Well stripe worked perfectly fine. I’ve never had any issues out of it and it was my personal first choice but they were inclined on using CardConnect.

    Authorize.net did not work right out of the gate either. There was way too much configuration on the backend for me to figure out in just a few minutes without any prior experience or guides. They handed me the account unactivated with no Server keys or e-commerce configuration. I tried to enable everything necessary, I had them double check it and it still didn’t work.

    All of my MIDs and keys were confirmed by CardConnect to be correct.

    Unfortunately they are using GoDaddy as their host provider I will request that they open up the ports and try it again.

    Resolving post as resolved due to inactivity. If you have any further questions/concerns please reach out to our support team at CardPointeSupport@cardconnect.com.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘SyntaxError: Unexpected token C’ is closed to new replies.